Web2.0-user experience-based Network Services

What is Web 2.0?

There is a website called What's Web 2.0. However, there is no answer. He is just a Community discussing the business, technology, and research of Web2.0.

The Web descriptions in Wikipedia are also vague. KESO said: "Web 2.0 is just a concept abstracted from phenomena. Everyone does not know this concept, so everyone has different understandings of Web2.0. He believes that some old technologies are integrated to defraud VC. Zhou tianshu believes that "Web 2.0 is based on the human-centered Internet ". As Dr. Jian mentioned, Web 2.0 is an industry term. Most people think that Web 2.0 = RSS + blog + SNS + (any new network term )....

Isn't that confusing? Is it true that all new things are attributed to Web 2.0, and the changes in the Internet have been gradual. Has it actually changed? Blog and RSS have been around us for more than a year. Why should we give him Web 2.0 now?

My point is:Web 2.0 refers to all user experience-oriented network services.This sentence has two key points: User Experience and network services.

Network services are not technical web services, but all applications that provide personalized services on the Internet. If there is no good service, there will be no users at all. With users, we also need to consider whether the service is willing to be used, and the service comes from the demand.

Focusing on user experience is the main reason why Web 2.0 is often mentioned. This is not only because users can participate, but also because Internet services are more user-friendly and personalized. The simplified Google interface and search sorting, the function release of Flickr, and the right-click submission of Del. icio. us all demonstrate the importance of user experience.

What network services do we need?

In fact, Zheng has mentioned in Learning Web 2.0 (II ).

Microcontent: microcontent. Any data produced by a user is classified as micro-content, such as a blog, comments, images, favorite bookmarks, favorite music lists, and what you want to do, places to go, new friends, etc. These micro-content is filled with our life, work, and learning, its quantity, importance, and our dependence on it, it is no less than the Orthodox articles, papers, and books that are well-founded and well-styled.

The re-discovery and utilization of micro-content is a natural derivative of equality, democracy, and freedom created by the Internet. It is also a result of Internet-related technologies that cut information management costs.

Every day, we produce a large number of micro-content and consume the same amount of micro-content. For Web 2.0, how to help users manage, maintain, store, share, and transfer micro content becomes the key.

For example, with the Windows operating system, why do we still need WinZip and ACDSee. Now, the portal provides us with services far from enough. Now we need a lot of things, depending on whether you are doing the best. There are many examples:

Because you want to add webpages and images to your favorites, you have Del. icio. us, furl, Flickr, and 365key.

Because everyone enjoys reading books, Douban and readshow are available.

Because you need to read RSS resources, Bloglines, Rojo, feedburner

......

In the future, network services must be generated from these microservices.

Technology is root and user experience-oriented

When it comes to Web2.0, most people will mention that Web2.0 is user participation. In fact, user participation exists in the past, now, and in the future, not the main feature of Web2.0. In addition, read the fourth lesson in "seven lessons of Google's success", "taking the user experience as an example:

Google's Sparta-style website is launched with a streamlined "menu", which is free of charge and does not encourage you to stay away from advertisements. The purpose of the design is to get you to the Information link as soon as possible and leave as soon as possible.

Who doesn't want users to visit your website more? It's best to divide each article into 10 pages. "Hurry up and leave me", which was previously incomprehensible to the website. Now Google relies on word-of-mouth traffic, which is larger than other websites. While Yahoo is desperately transforming itself into a portal, Google strives for perfection in search technology and user experience.

In my opinion, some new and old technologies proposed by Web 2.0 are designed to improve user experience. Note these technologies one by one.

RSS-- This is a subset of the XML format. Some fixed tags are agreed to be recognized by the reader. It facilitates data exchange.
Benefits:1) users can subscribe to RSS for targeted information
2) developers can use RSS as the data source interface
Limitations:1) currently, the formats of 1.0 and 2.0 vary greatly, and some readers are incompatible.
2) RSS fixed labels are sometimes not enough, such as transmitting images.
Suggestion:Use as many places as possible without affecting website performance
User Experience:As long as you know the information source, you can obtain the information in a targeted manner, and the information is more smooth, saving the portal transit process.

Trackback-- Two scenarios are available: receive trackback and send trackback. Receiving trackback means that the messages sent by the recipient are saved and displayed. It is relatively complicated to send trackback. You need to analyze the links in the body, capture pages one by one, and analyze whether the received trackback contains the RDF mark. If yes, extract the trackback address and send a message to the trackback address.
Benefits:Trackback forms a loop for the quote to notify the referenced person, so that the topic can be traced easily.
Limitations:1) trackback achieves resource consumption, and many blog systems have blocked it.
2) trackback spam is a headache
Suggestion:Generally, it is best to provide trackback receiving operations on the final page to bring trackback out of the blog circle.
User Experience:Knowing who is referencing can lead to more discussions and discover like-minded people.

Tag-- Technically speaking, it is multi-classification, and the function is designed to make it easier for users to attribution of documents.
Benefits:1) easier classification and better user experience
2) with Tag ownership, it is more convenient to search for and federated searches.
Limitations:1) More semantic elements such as tag synonyms need to be studied.
2) Tag spam is also a headache
3) in China, there are not many people using multiple tags, which is a problem
Suggestion:You only need to use tags when classifying information. The harder it is to find and use tags, the better. Comparing videos and videos is the most difficult to find. In this case, the best effect is to use tags. In addition, Rojo labels for each item a bit too much. Is this really necessary?
User Experience:It is easier and more convenient to add a category, and more convenient and accurate to search.

Web Services-- This is the main technology for Realizing Data Exchange on heterogeneous platforms. Data Transmission also adopts XML format.
Benefits:Heterogeneous platforms can seamlessly exchange data
Limitations:Web services can only be developed by programmers
Suggestion:Zhou tianshu believes that "the core of Web 2.0 is Web Service". I have different opinions. unless there is a technical partner's requirement, it is of little significance to implement the Web Services interface. This does not mean that Web services are not good, but in China, programmers seldom use the web services of other websites to write additional applications. This situation is hard to change in a short time. Think about the reason why the Open Source in foreign countries cannot be found at the Chinese site.
User Experience:Users do not feel it. developers need to develop related applications to make them effective.

Web Standard (CSS + XHTML)-- The word "web standards" was promoted in China last year with the book "website reconstruction: Design Using web standards". In general, there is no technical content, it mainly puts forward higher requirements for art design engineers and changes some of the original web design habits.
Benefits:1) smaller pages and faster loading
2) The page is more standard and reduces interaction with the program
Limitations:The main learning cost is that there is no good visual compiler yet.
Suggestion:Use as many as possible
User Experience:The page loading speed is faster, making it easier for users to access

URL rewriting-- URL rewriting is actually a special HTTP handler. This handler is used to filter each URL request and redirect the URL as needed.
Benefits:Make the URL shorter and easier to remember
Limitations:In IIS, Handler generally processes a suffix file. If it is a wildcard character, handler actually processes many requests that do not need to be processed, resulting in waste.
Suggestion:Use as much as possible. For IIS implementation, refer to URL rewriting in ASP. NET.
User Experience:Users can easily remember the URL for the next visit.

Ajax-- The full name is Asynchronous JavaScript with XMLHttpRequest. Ajax calls XMLHttpRequest to Implement Asynchronous Communication with the server and processes the returned XML message using the xmldom of the corresponding platform, then, you can use Dom to perform operations on HTML elements on the page to create a rich and friendly user interface. As we all know, this is an old technology. "the reincarnation of fashion-Ajax" points out that,
Microsoft Remote scripting is almost the same as Ajax. However, due to the popularity of server-side technology at the time, a single deployment that runs everywhere (as long as there is a browser) was a wave of buzz, so that people ignored user interaction. Microsoft Remote scripting has not received much attention to improve user experience.
We know that the post back and view State of ASP. NET 1.x introduces a new concept: the event-driven programming mode on the server side. Its side effect is that the entire web page is constantly refreshed. However, the script callbacks of ASP. NET 2.0 will introduce a new concept refresh the data, not the page. What is the difference between its core idea and Ajax.
Therefore, whether or not Ajax is "Old wine has a new bottle", the continued development of technology is definitely a very good thing for the website. There are many very cool Ajax Development kits, such as script. aculo. Us and Rico, which can help us easily implement complicated asynchronous data processing. Ajax matters has more development information in this area.
In addition to Google's emphasis on AJAX, we can see that Microsoft is also preparing to launch related software on the PDC in September. It seems that the trend of focusing on user experience is irreversible.
Benefits:You can complete asynchronous data exchange without refreshing the page.
Limitations:Some browser versions have different support for XMLHttpRequest and JavaScript.
Suggestion:What applications is Ajax suitable? I agree with the views of the author of buffalo on AJAX:
From the perspective of appearance, it is suitable for Web applications that are not URL-sensitive. If an application is more concerned about the URL than the interaction feature, do not assume that the entire application uses Ajax; otherwise, AJAX can be used completely. for example, in a forum system, if a user cannot locate a page through a URL, the application fails, but in an email system, the traditional email needs to download the entire page every time you click it. Compared with Gmail's interactivity and operability, the success or failure is obvious.
User Experience:Greatly enhanced, as long as the technology is used, it is no different from the client software. This also shows that AJAX is one of the best technologies for implementing rich Internet applications.

Wiki-- A one-person CMS system
Benefits:Gather strength to build Internet Content
Limitations:Aside from excluding spam, popularity is also a problem and we cannot expect an encyclopedia to be around
Suggestion:I am not very optimistic about the development of Wiki in China, for the same reason as open source.
User Experience:The common creation and Connection Methods of Wiki allow users to learn enough information in one place (of course, wiki information is sufficient ).

About user experience, I recently read the about face 2.0 of Alan Cooper, father of VB. There are a lot of cases in the book to analyze the design and principles of user interfaces. Although most of them are for software, but it is of reference value for web design. In addition, patterns in interaction design is also a very good web design model website. All the cases in it are for the web, so it is worth learning.

End with an old saying: Don't worry about Web 2.0, care about the technologies that actually improve your web user experience, and care about the development trend of web technologies.