To Web 2.0 or not to Web 2.0

Yahoo, Google, Microsoft and others are making their APIs open and increasingly easy to use. Often with only a few lines of copied and modified code, a Google map swatch or search bar or Flickr photo cloud providing visual accompaniment or now Yahoo mail information can be added to any website. Google's code is primarily client-side so can run more easily, Yahoo's mainly runs server-side and requires ISPs to have Apache 2.0 and PHP 5 installed.

Those sneaky software companies! At a basic level, open APIs expand the outsourcing trend from user-generated content to user-generated applications too. This actually benefits both the software companies and users.

At the more important conceptual level, open APIs are extending the componentization of software, which has been progressing in fits of cohesion and rollbacks of proprietary standards. As Jaron Lanier and others have long pointed out, the software industry lacks an effective standardized component library and rebuilds the wheel each time. The same point is made in global productivity speak by former McKinsey consultant William Lewis in "the Power of Productivity;" industries that standardized components early became leaders, homebuilding is a notable example.

Users featuring more prominently in the development process as well as other current factors such as Web 2.0 applications being organized in chunkable components may provide a stronger more fungible foundation for software development from which we can all benefit.