Yesterday afternoon the Web 2.0 Expo included two
sessions on widgets. The first was a presentation by Dion Hinchcliffe, which provided an
Overview of Badges and
Widgets. Immediately following that session, two widget syndication companies
provided back to back presentations in a session called Using Widget Syndication
for Online Marketing and Measurement. While officially these sessions were part of
two separate conference tracks, by a show of hands approximately half of the attendees in
the sessions attended both of them. Graeme Thickins wrote a very good overview of the
second session for Read/WriteWeb. What follows are some of the key points from Dion's
presentation.
Dion opened by unpacking the fact that the web is becoming much more of what he characterizes as a DIY Phenomenon. This cultural change is what he credits as the driver for the popularity of widgets. Specifically the DIY ethos on the web has four components:
Based on this change on the web, there are three key aspects that every widget should include, according to Dion:
Finally Dion got to the cornerstone of his talk, touching on three components that should be included when making a business case for building widgets. He then pointed to two examples of very successful widgets. The components of your business case should include:
While these all seem valuable in theory, it is important to look at widget examples that have actually contributed to an organization's goals. The first example, not surprisingly, was the YouTube Video Badge. This is an interesting example, because as readers of R/WW know, the viral popularity of a YouTube badge on MySpace and other social networks was a key component of YouTube's growth. This has resulted in YouTube becoming one of the most popular sites on the web.
Based on this popularity, Dion examined the social nature of the YouTube widget. There were two components which made this widget so easy to share and ultimately led to it being so popular:


I would add that the widget was something that users of MySpace and other social networking sites wanted badly. However, once you have built a widget that satisfies a need for your users, it certainly is interesting to reflect on YouTube for ways you can make that widget more social.
Dion's next example was interesting because I wouldn't have thought of it as a widget. He actually pointed at the Google AdWords Widget for Publishers (AdSense) as "probably the most successful widget in history." While certainly not a widget for self-expression, it certainly has created value for Google and the publishers using that widget. Specifically, this has made pages across the web a platform for Google to sell ads on.
As the Internet has evolved into a 'DIY Web', it is important for every site to evaluate how widgets fit into their strategy. They clearly have been critical in the successes of many web services and hopefully panels like the two covered above will help others figure out how widgets can help them.
I'm sure that many of you have additional observations and success stories from your experiences. Please feel free to share them in the comments below.
Comments
Subscribe to comments for this post OR Subscribe to comments for all ReadWriteWeb posts
Cross domain widgets extending the webos, http://www.widgetplus.com
Very interesting stuff. I wonder if we will still have web "pages" in the future, or if everything will just be a collection of widgets. No one has said this, but widgets seem to me to be open versions of what portal vendors were calling "portlets."
I also think that widgets are the way we might finally achieve "composite applications," another hot buzzphrase that had many people scratching their heads.
Tim
I would hardly call Adsense a widget. It's an AD.
Good point by Tim. Watch what's happened with portlets to predict where widgets might be going. At Web 2.0 Expo, I heard about a stealth company with some great technology in that regard. We're still in the early days of the widgetsphere...
Graeme
If Adsense is a widget, then anything written in a script with a link to its origin would be a widget?
Then we shouldn't see widgets as that new...
Is'nt the next step in the evolution of widgets, that you write and design one using markup, save it to your site, and then have a remote service executing it live as a serverside application (accessing all objects avaliable on that server, email, sql, etc) and which anyone on the web then can access as a live widget?
It's like a rss, mashup and a webapplication feed in one package.
If it was google, you'd write your own brand of search for your site as a widget, and then anyone would be able to include that widget on their site, searching your site via google, but with your interface and logo.
A 'search readwriteweb' widget..
You get the brand recognition, they get the ad business.