What: What is Web2.0 - article
When: 9/30/2005
Link: http://www.oreillynet.com/pub/a/oreilly/tim/news/2005/09/30/what-is-web-20.html
Reading Notes:
This is an oldie. Just did a reread of it and it left me a bit
breathless again. Trying to look at it from the perspective of a person
who doesn't care an iota about web2.0, but still end up enthused by the
ideas/methods described here. Here are my reading notes:
* Great Web2.0 Meme map. Standalone version here: http://www.2036ad.com/archives/images/web2mememap.jpg
Some key phrases from it:
* trust your users
* small pieces loosely joined
* rich user experience
* granular addressability of content
* emergent user behaviors
* software gets better as more people use it
* right to remix
* perpetual beta
* hackability
* long tail
* an attitude, not a technology
* web as platform
* services/not packaged software
* architecture of participation
* software not tied to a device
* harnessing of collective intelligence
The Web As Platform
* Google is standard bearer for web2.0
* the value of the software is proportional to the scale and dynamism of the data it helps to manage
* without the data, the tools are useless
* longtail = the collective power of the small sites that make up the bulk of the web's content
* bittorrent is an example of a web2.0 service that acts as an intelligent broker - connecting the edges to eachother and harnessing power of users themselves
Harnessing Collective Intelligence
* Ebays
product is the collective activity of it's users - it is an enabler of
a context in which user activity can happen. it's advantage comes from
the critical mass of buyers and sellers
* amazon made a science of
user engagement. they have invitations to participate at every turn.
they layered data on top of existing data structures.
Lesson: network effects from user contributions are the key to market dominance in the web2.0 era
Blogging:
- the chronological organization of a blog drives the value chain of a blog
- RSS was key in growth of blogs
- permalink was also key to building bridges between blogs
- bloggers have a disproportionate role in shaping search engine results
- also create an echo-chamber which amplifies their role
- the "former audience" decides what's important
Data is Key
* SQL is the new HTML
*
control over the database has led to market control - especially when
those data sources are expensive to create or amenable to increasing
returns via network effects
* failure to understand importance of owning an apps core data will undercut competitive position
*
amazon relentless enhanced data - adding on top of publisher supplied
data. harnessed users to build the data. they embraced and extended
data from their suppliers - and added a layer of value
* the race is on to own certain classes of core data: location, identity, public event calendaring, product IDs and namespaces
*
the winner will be the company that first reaches critical mass via
user aggregation, and turns that aggregated data into a system service
End of Software Release Cycle
* software is delivered as a service, not a product [as i write this in Google Docs]
* operations must become a core competency - the software will cease to perform unless it is maintained on a daily basis
* users must be treated as co-developers
Lightweight Programming Models
* simplicity sets the world on fire - simple apps/methods/protocols have won out over the complex. ie: RSS + REST
* support lightweight programming models that allow for loosely coupled systems
* think syndication, not coordination
* design for hackability / remixability - make barriers for reuse extremely low - use 'some rights reserved'
*
innovation comes from assembly - when commodity components are
abundant, you can create value simply by assembling them in novel or
effective ways
Software Not Tied to a Device
* it's no longer linked to the PC platform
* more and more devices are connected to the new platform - enabling flash mobs, citizen journalism...
Rich User Experiences
* companies that succeed will create apps that learn from their users and that use the richness of shared data
* getting more desktop like
Core Competencies of Web2.0 Companies
* services, not packaged software, with cost-effective scalability
* control over unique, hard to recreate data sources that get richer as more people use them
* trusting users as co developers
* harnessing collective intelligence
* leveraging the long tail through customer self-service
* software that works across devices
* lightweight user interfaces, development models, and business models