Design patterns and business model for Web 2.0


The new generation of business applications and the web begins to fall under the term Web 2.0. 

Here are some points to consider for anyone who is raised to open or maintain a business within the new stage of the Network:

1. The Long Tail (The Long Tail) 

Small websites are the vast majority of Internet content, the small niches constitute the vast majority of potential applications. So: Take advantage of the use of self by the client and the data management algorithms to reach the entire web, at the ends and not just the center, the long tail and not just the head.

2. The data is the next Intel Inside 

Applications are increasingly based on the data. Therefore: For competitive advantage, look to be the owner of a unique data source and difficult to reproduce.

3. Users add value 

The key to competitive advantage in internet applications is the extent to which users add their own data that you provide. Therefore: Do not limit your "architecture of participation" to software development. Involve users both implicitly and explicitly in adding value to your application.

4.Externalidades default network 

Only a small percentage of users take the trouble of adding value to your application. Therefore: Set inclusive default parameters to allow the aggregation of user data as a side effect of using the application.

5. Some Rights Reserved 

The intellectual property protection limits re-use and prevents experimentation. Therefore: When benefits come from collective adoption, not private restriction, make sure that barriers to adoption are low. Follow existing standards, licensing and use with minimal restrictions possible. Design for "hackeabilidad" and "remixed".

6.The Perpetual Beta 

When the devices and programs are connected to the Internet, applications are no longer any software artifact, they are ongoing services. Therefore: Do not bundle new features into monolithic versions of the package, but on the contrary add them regularly as part of normal user experience. Involve your users as real-time testers, and design the service so that you know how people are using these new features.

7. Cooperate, Not Control 

Web 2.0 applications are built from a network of cooperating data services. Therefore: Offer web services interfaces and content syndication and reuse of other data services. Support lightweight programming models that allow for loosely coupled systems.

8. Software is not limited to a single device 

The PC is no longer the only access device for internet applications, and applications that are limited to a single device are less valuable than those that are connected. Therefore: Design your application from start to integrate services across handheld devices, PCs and servers.

These points have been extracted from a translation of an article by Tim O'Reilly made the team of the Bulletin of the Information Society Telefónica 

The article defines what the term encompasses Web 2.0, at least under the vision of one of its creators, Tim O'Reilly, and the conclusions are justified here.

You can access the original article in the   O'Reilly Network web or translating the Bulletín of Telefónica