One of the things that I spend a lot of time talking about internally is how the lowly web browser is being outfitted with the mechanics for much richer client applications. I've talked before about how scripting tools like PHP and AJAX are synching development and runtime environments, and how these tools also enable lead user theory in application development. The latter is really interesting because it could result in product cycles being shorter and ultimately more innovative products and services as a result of users taking web apps in directions that were never originally anticipated.
The other aspect of this evolution is that techniques and tools are emerging to outfit the browser with "state" and this, IMO, is what will really unleash the web browser as a container for much more powerful applications. Instead of each page refresh or load being treated as a separate transaction, developers can now use tools that assume things like authentication over a series of user interactions.
Okay, so my definition of web 2.0 is evolving from the rather vague but often mentioned "small parts loosely connected" to:
- synchronization of development and runtime environments
- ability to take advantage of application state for complex interactions
What else should be considered?
Link: TechCrunch � New Yahoo Maps Shows Power of Flash.
Because Yahoo Maps is a flash application, it avoids the need for page refreshes changes are made to the page. A simple drag and drop module on the top left lets users move around easily (even easier than the great Google drag method). There are multiple ways to zoom into and out of a map, including using the scroll wheel on the mouse, or the page up/down buttons on the keyboard. The arrow keyboard keys also allow for scrolling off-screen to new areas.
Comments