Design Model of Web 2.0

Design Model of Web 2.0

In the book a pattern language, Christopher Alexander provides a refined description of Solutions to architecture problems, prescribed a prescription in one format. "Each model describes a problem that occurs over and over again in our environment, and thus describes the core solution to the problem," he wrote. In this way, you can use this solution for tens of thousands of times, instead of repeating the same thing ."
1. Long Tail
Small websites constitute most of the Internet content; market segments constitute most of the possible applications of the Internet. Therefore, the customer's self-service and algorithm data management can be used to extend to the entire Internet, reaching the edge, not just the center, but the long tail, not just the head.

2. Data is the next intel inside
Applications are increasingly driven by data. Therefore, in order to gain a competitive advantage, we should try to possess a unique and difficult to recreate data resource.

3. adding value to users
For Internet applications, the key to a competitive advantage lies in the extent to which users will add their own data to the data you provide. Therefore, do not limit your "participating system" to software development. To add value to your program implicitly and explicitly.

4. Default Network Effect
Only a small number of users will not bother adding value to your program. Therefore, it is necessary to set the default value to aggregate user data and become a by-product of the user's use program.

5. reserve some power
Intellectual property protection limits reuse and hinders experiments. Therefore, when the benefits come from collective wisdom rather than private constraints, we should confirm that the adoption threshold is low. Follow existing guidelines and grant permissions with as few restrictions as possible. The design program makes it programmable and combiner.

6. Permanent Beta
When devices and programs connect to the Internet, programs are no longer software works and they are ongoing services. Therefore, do not package all the new features into the released version of the integrated enterprise, but add these features frequently as part of the normal user experience. Attract your users to act as real-time testers and record these services to learn how people use these new features.

7. cooperation rather than control
Web 2.0 programs are built on a cooperative data service network. Therefore, network service interfaces and content aggregation are provided, and other people's data services are reused. Supports lightweight programming models that allow loose integration with the system.

8. Software exceeded a single device
PC is no longer the only access device for Internet applications, and the value of a single device program is smaller than those connected programs. Therefore: from the very beginning, design your applications to integrate multiple services across handheld devices, PCs, and Internet servers.