Web 2.0 and the Missing Business Model
Everyone has a Web 2.0 rant and I guess it's time for mine. Over at BloggingStocks, Tom Taulli in an article entitled eBay: The Web2.0 Killing Fields observes that ebay is seeing the liquidation of lots of Web 2.0 startups. He makes a valid point that Web 2.0, much like many of the dotcom startups, don't have a business reason for being:
But there's a problem: while these sites are definitely cool, the business model is often hazy. After all, when you give something away, you need either a premium product to upsell or a lot of users to monetize things with advertising.
How does this square with Tim O'Reilly's principles for Web 2.0? So far the only principles adopted by the Web 2.0 social bookmarking sites is "wisdom of crowds" (aka, let the users create the content for you) and "rich interaction" (aka, Ajax) to make their apps/site as usable and cool as possible, and counting on network effect to drive value for their users. Meanwhile all of the Web 2.0 "web is the platform" startups are either being acquired or driven out of business by Google. This far into the Web 2.0 hype cycle, from a business model perspective, the offerings out there are still very much of a yawn.
The social bookmarking sites, especially, are an inch deep when it comes to that user created content. Flickr and the user created Korean news site, Oh My News (english language site) are the exceptions here, with original content being contributed by its users.
We've all read the various models being bandied about, from micropayents, to advertising to selling offline copies of the agreggate. This may be the best one yet, through:
OK, so you buy a domain and web service hosting for one year ($200?). Then you quickly throw a webpage together that renders some XML as HTML. Put it on eBay and pocket $4,000? Repeat weekly and you are making $200,000 per year.
Fortunately for all of us Ajax developers, Web 2.0 isn't the only thing driving Ajax adoption.
Topics: Business Reasons for Ajax, Web 2.0
Comments: 1 so far
Leave a comment
About Pathfinder
Follow the Blog
-
Get a monthly update on best practices for delivering successful software.
Subscribe via email
Subscribe via RSS
Categories
Topics
Archives
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
Blogroll
Recent
- Elements of Testing Style
- Aesthetics and Web Design
- Asterisk-Java Testing with Groovy
- 3 Misuses of Code Comments
- Fluently NHibernate
- Digging a Hole and Covering it with Leaves — The Software Development Version
- The Importance of User Experience - Do You Understand It in Your Bones?
- Writing Your Own Protocol With NSURLProtocol
- What’s In Your Dock: iPhone edition
- Feature Fatigue

I’ve posted about something like this on my forums a while ago, check it out: http://forums.programming-designs.com/viewtopic.php?id=486
Comment by Daniel, Wednesday, August 23, 2006 @ 3:31 pm