<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/web_20_expo_all_things_widgets.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:,2008:/1/tag:72.47.210.69,2007://1.3719-</id>
  <updated>2008-07-07T14:30:11Z</updated>
  <title>Comments for Web 2.0 Expo: All Things Widgets</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.1</generator>
  <entry>
    <id>tag:72.47.210.69,2007://1.3719</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/web_20_expo_all_things_widgets.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=3719" title="Web 2.0 Expo: All Things Widgets" />
    <published>2007-04-19T06:50:08Z</published>
    <updated>2007-12-16T23:11:24Z</updated>
    <title>Web 2.0 Expo: All Things Widgets</title>
    <summary> 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...</summary>
    <author>
      <name>Sean Ammirati</name>
      
    </author>
    
    <category term="Web 2.0 Expo 2007" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><img hspace="5"
src="http://www.readwriteweb.com/images/expo_widgets/web20_expo_logo.jpg" align="left"
vspace="5" width="130" height="69" /> Yesterday afternoon the Web 2.0 Expo included two
sessions on widgets. The first was a presentation by Dion Hinchcliffe, which provided an
<a href="http://www.web2expo.com/cs/webex2007/view/e_sess/13699">Overview of Badges and
Widgets</a>. Immediately following that session, two widget syndication companies
provided back to back presentations in a session called <a
href="http://www.web2expo.com/cs/webex2007/view/e_sess/12172">Using Widget Syndication
for Online Marketing and Measurement</a>. 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 <a
href="http://www.readwriteweb.com/archives/widgetsphere_expo07.php">good overview of the
second session</a> for Read/WriteWeb. What follows are some of the key points from Dion's
presentation.</p>

<h2>Why are Widgets Popular</h2>

<p>Dion opened by unpacking the fact that the web is becoming much more of what he
characterizes as a <a href="http://blogs.zdnet.com/Hinchcliffe/?p=80">DIY Phenomenon</a>.
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:</p>]]>
      <![CDATA[<ul>
<li>Building <b>open platforms</b> instead of stand-alone apps (self-distribution is
key);</li>

<li>Spreading your product beyond the boundaries of your site;</li>

<li>Building on the <b>shoulder of giants</b> (leveraging APIs from Yahoo!, Amazon, etc
...);</li>

<li>The <b>automated mass servicing</b> of markets of low demand content and
functionality (Long Tail).</li>
</ul>

<h2>Key Aspects of Widgets</h2>

<p>Based on this change on the web, there are three key aspects that every widget should
include, according to Dion:</p>

<ul>
<li>Supreme ease of consumption and distribution;</li>

<li>Connect to their underlying sites to provide value and control;</li>

<li>Have business model baked deeply into it (Driving site traffic, content consumption,
advertising, etc...).</li>
</ul>

<h2>Business Case</h2>

<p>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:</p>

<ul>
<li>Getting your content on millions of other pages instead of just your own site;</li>

<li>Letting users broaden your distribution globally 24X365 for virtually no cost;</li>

<li>Turning your applications into open platforms and foundation of dozens, hundreds, or
even thousands of other products.</li>
</ul>

<p>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 <b>YouTube Video Badge</b>. 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 <a
href="http://www.readwriteweb.com/archives/youtube_now_number4_alexa.php">the most
popular sites on the web</a>.</p>

<p>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:</p>

<ul>
<li>At the end of every video, there is one-click interaction to share the widget:<br /><img src="http://www.readwriteweb.com/images/expo_widgets/YouTube_Share.gif" /></li>

<li>Additionally, on the YouTube website itself, the code is shown on the site; allowing
users to copy and paste the html code required to put the YouTube widget on whatever
other site they want.<br /><img src="http://www.readwriteweb.com/images/expo_widgets/YouTube_code.gif" /></li>
</ul>

<p>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.</p>

<p>Dion's next example was interesting because I wouldn't have thought of it as a widget.
He actually pointed at the <b>Google AdWords Widget for Publishers (AdSense)</b> 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.</p>

<h2>Conclusion</h2>

<p>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.</p>

<p>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.</p>]]>
    </content>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.3719-comment:31747</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.3719" type="text/html" href="http://www.readwriteweb.com/archives/web_20_expo_all_things_widgets.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/web_20_expo_all_things_widgets.php#c31747" />
    <title>Comment from Mikael Bergkvist on 2007-04-19</title>
    <author>
        <name>Mikael Bergkvist</name>
        <uri>http://xinteleport.blogspot.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://xinteleport.blogspot.com">
        <![CDATA[<p>Cross domain widgets extending the webos, <a href="http://www.widgetplus.com" rel="nofollow"><a href="http://www.widgetplus.com" rel="nofollow">http://www.widgetplus.com</a></a></p>]]>
    </content>
    <published>2007-04-19T15:09:15Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.3719-comment:31748</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.3719" type="text/html" href="http://www.readwriteweb.com/archives/web_20_expo_all_things_widgets.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/web_20_expo_all_things_widgets.php#c31748" />
    <title>Comment from Tim on 2007-04-19</title>
    <author>
        <name>Tim</name>
        <uri>http://blog.tektag.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://blog.tektag.com">
        <![CDATA[<p>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."</p>

<p>I also think that widgets are the way we might finally achieve "composite applications," another hot buzzphrase that had many people scratching their heads.</p>

<p>Tim</p>]]>
    </content>
    <published>2007-04-19T16:38:23Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.3719-comment:31749</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.3719" type="text/html" href="http://www.readwriteweb.com/archives/web_20_expo_all_things_widgets.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/web_20_expo_all_things_widgets.php#c31749" />
    <title>Comment from AdvertiseSpace on 2007-04-19</title>
    <author>
        <name>AdvertiseSpace</name>
        <uri>http://www.advertisespace.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.advertisespace.com">
        <![CDATA[<p>I would hardly call Adsense a widget.  It's an AD.</p>]]>
    </content>
    <published>2007-04-19T19:50:20Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.3719-comment:31750</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.3719" type="text/html" href="http://www.readwriteweb.com/archives/web_20_expo_all_things_widgets.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/web_20_expo_all_things_widgets.php#c31750" />
    <title>Comment from Graeme Thickins on 2007-04-19</title>
    <author>
        <name>Graeme Thickins</name>
        <uri>http://graemethickins.typepad.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://graemethickins.typepad.com">
        <![CDATA[<p>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...</p>

<p>Graeme</p>]]>
    </content>
    <published>2007-04-19T21:53:05Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.3719-comment:31751</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.3719" type="text/html" href="http://www.readwriteweb.com/archives/web_20_expo_all_things_widgets.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/web_20_expo_all_things_widgets.php#c31751" />
    <title>Comment from Linky Love on 2007-04-20</title>
    <author>
        <name>Linky Love</name>
        <uri>http://www.linkylove.net</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.linkylove.net">
        <![CDATA[<p>If Adsense is a widget, then anything written in a script with a link to its origin would be a widget?</p>

<p>Then we shouldn't see widgets as that new...</p>]]>
    </content>
    <published>2007-04-20T10:17:51Z</published>
  </entry>

  <entry>
    <id>tag:72.47.210.69,2007://1.3719-comment:31752</id>
    <thr:in-reply-to ref="tag:72.47.210.69,2007://1.3719" type="text/html" href="http://www.readwriteweb.com/archives/web_20_expo_all_things_widgets.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/web_20_expo_all_things_widgets.php#c31752" />
    <title>Comment from Mikael Bergkvist on 2007-04-20</title>
    <author>
        <name>Mikael Bergkvist</name>
        <uri>http://xinteleport.blogspot.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://xinteleport.blogspot.com">
        <![CDATA[<p>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?<br />
It's like a rss, mashup and a webapplication feed in one package.</p>

<p>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.<br />
A 'search readwriteweb' widget..</p>

<p>You get the brand recognition, they get the ad business.</p>]]>
    </content>
    <published>2007-04-20T16:16:44Z</published>
  </entry>

</feed>