James.Cridland.net

James Cridland's blog

Where radio and new platforms collide. With beer.

« A week in the life of meetings | Blog index | Lies, damn lies, and statistics »

A day in the life of a widget

Posted on Sunday, March 2nd, 2008 at 11:30am. #

Last Thursday, I went to a moderately unsatisfactory conference on widgets. I say it was moderately unsatisfactory, because during the event we saw precisely no widgets at all, but mostly sales pitches from improbably-named companies, one of which used the fantastic bullshit bingo claim that widgets help “leverage virality”, which was so splendid bollocks-language that I made a special note of it.

We also had no examples of how widgets had done, who had used widgets, and how their takeup has been. The audience were more interested in “where’s the money coming from?”, and the whole event appeared to be moderately negative towards widgets and gadgets - probably because the audience didn’t really understand what it was that they were talking about.

I piped up from the back, essentially saying that the big thing that nobody had stressed was the need for an API, and to make that API public. Without a public API, your audience can’t make widgets with your content. Everything you build should have an API. (Thankfully, I practice what I preach, at least in this case).

The BBC runs something called BBC Backstage which contains a (woefully inadequate) list of APIs and feeds that the BBC runs. Some aren’t very reliable, which is something that I wish to change. Some obvious feeds aren’t there yet, which - for radio, at least - I wish to change, too.

One of those feeds for BBC Weather, for which I spent a rainy afternoon coding an iGoogle BBC weather gadget. I placed that blog entry live, announced it on the Backstage mailing list, submitted it to the iGoogle directory, and forgot about it.

The screenshot above, therefore, shows what happens to a widget once released into the wild. As you can see, its takeup is really rather good: it’s regularly getting 8,500 hits every day. And I’ve simply not promoted it. (Nor’s anyone else, from what I can tell). And let’s be very clear: this is a widget which is designed to replace a weather widget which is installed on every single new iGoogle page: hardly the easiest job to convince people to change.

What I’ve not monitored (but could) is how many people use it to click through to the BBC website, to satiate those who wanted ROI information. (It’s not really the purpose of this gadget, being honest.)

So hopefully this information helps those who were at that event, but couldn’t see the benefit of widgets. Build an API - make it open - and watch your community do stuff with your content.

If you’re looking for good widgets to add to your iGoogle front page, by the way, try Media UK’s media news, and Media UK’s live radio and television player. I’ve used them every day since I, er, wrote them.

The screenshot is straight from my Asus Eee PC, which I’ve customised to add a sensible desktop to, instead of the tabbed interface. It’s a five minute job.

Disclosure: I was a guest at the Mashup widget event, and avoided paying the entrance fee. My full disclosure is relevant to this posting.

7 comments

Ivan Pope said at March 2nd, 2008 at 2:25pm

James,
Thanks for an excellent blog post. Sorry you found the event ‘moderately unsatisfactory’. I guess a main reason for this is, with a one hour event, it’s hard to anticipate and cover off all levels and directions of interest. The event was about commercial widget uses and opportunities, and I sort of presupposed that the audience would have got past the ‘what does a widget look like’ point.
While the audience did appear to have a slightly negative view of widgets and a ’show us the money’ fixation, there were also a lot of very interesting questions coming up around issues such as standards, SEO, resources etc, which made me feel there was more interest in the room than we were able to deal with. As I said, one hour is a very short time to get to the nub of a subject.
While I agree tht everything should have an API, an API is not essential for a widget. Plenty of widgets use RSS feeds and there are plenty of widget and widgetised applications around that give users a lot of value without opening up a public API.
My widget conference, (now called) Widget Web Expo, will have two days with two streams of widget content in New York in June and London in October - we’ll cover APIs and mashups and platforms and standards and technologies and tools. And I guarantee you’ll see more widgets on the screen than you really want to.
Now I’m going to ‘drop a blog’ about your widget.
[Disclosure - I was the Chair of the above event]

James Cridland said at March 2nd, 2008 at 10:52pm

Course, I kind of meant that everything should have some kind of data feed (an RSS feed being the simplest, and what I use here).

I certainly felt there was interest in the room, and appreciate your points.

Brian Butterworth said at March 3rd, 2008 at 10:16am

I love your weather iGoogle gadget.

I did a simple backstage’ gadget - one that puts the live stream of BBC News 24 on the Vista sidebar. It could do more, I guess, but 60,500 people have downloaded it now.

http://gallery.live.com/liveItemDetail.aspx?li=c10fdb04-dab5-4936-b317-411750afcc86&bt=1&pl=1

And there’s a iGoogle version of the same one:

http://www.google.co.uk/ig/adde?hl=en&moduleurl=http://ukfree.tv/bbcnews24_gadget.xml&source=imag&

Paul said at March 4th, 2008 at 3:06am

A *working* RSS feed is also good James… :-)

There has been an error of some kind. Ack!
FeedBurner could not deliver this feed to you because of the specific problem listed below:

Feed Address: http://rss.james.cridland.net/JamesCridlandsBlog

HTTP Error (Code) and Message: (404) Feed not found error: FeedBurner cannot locate this feed URI.

James Cridland said at March 4th, 2008 at 12:44pm

Ah, yes. The auto-discovery one works, the one in the side-bar works, but the ones in the footer… didn’t. Until now. Bah.

Jenni Lloyd said at March 4th, 2008 at 3:31pm

Hi James

I was also at the widget mashup event the other night. I’ve been to a few of these events before and it’s always a slightly strained mix of suits and scruffy types. The social networking one had a similarly negative tone - in the ‘I can’t believe people have got time to spend on facebook’ vein.

Because of the awkward nature of the audience it probably would have been better to define the majority interest at the beginning - which I think Ivan tried to do but was thrown off course by the freeform text question thingy and the sales pitches from Techenlightenment and Widget Avenue.

In terms of real life examples I would have been tempted to look at a business like the publishers Random House. They are an exemplar of a traditional company operating within the confines of a very old-school business model who have taken an amazing step forward by digitising their entire back catalogue. This enables them to offer their product - books - to a digital audience in new and extraordinary ways. Interesting write up here:
http://www.readwriteweb.com/archives/random_house_widgets_and_web_services.php

Perhaps what was missing at the event last week was a clear understanding of ‘why’ a business might pursue a widget strategy - which points to a lack of understanding in the changes to the way consumers are accessing content, products and services. It seems to be short sighted not to at least want to have a play with new technology, if only to gain understanding for the future.

You might also be interested in this case study:
http://www.sexywidget.com/my_weblog/2007/05/anatomy_of_a_wi.html

*disclosure: I work for Nixon McInnes who were represented on the panel

iGoogle gadgets for BBC News, BBC Weather, and BBC Radio - blog - James Cridland said at August 4th, 2008 at 10:16pm

[...] this year, I blogged about my BBC Weather widget, which, as the BBC News widget, I built as a bit of relaxation coding [...]

Leave a comment

This website's Gravatar enabled (that's the pictures on the right)

To prove you're human, type the two words below into the box provided.