Brett Berntsen: April 2008 Archives

I have a habit of returning my library books a few days after their due dates. I don't like the fines and returning the books late is disrespectful to other people on the waiting list. In order to make myself feel better (and save a few bucks), I signed up for the Hennepin County Library's email alert service because it promised to send me a reminder a few days before the books are due.

When the first alert arrived, I remembered the books sitting on my nightstand, but the most interesting thing about the email was the comment link next to each book. Clicking the link opened library's site and allowed me to write a review or leave a comment about the books for other library patrons to read.

The comment feature probably isn't new for the Hennepin County Library. Afterall, I have been writing and reading product and service reviews on sites like Amazon, Expedia, and Trip Advisor for years. The link did, however, remind me of an article I read in the most recent issue of Wired magazine (May 2008). In the "Information Overlord" article, the author discusses the virtues of a semantic Web applications. He writes:

"...sometimes social connections are less useful than semantic ones... My Facebook page attracts my friends, with whom I share social bonds. Meanwhile, my science blog attracts complete strangers, with whom I share a common interest in a topic... It's a semantic relationship, based on shared meaning."

The point is interesting and relates to the library link. When I'm planning a vacation, I read the customer reviews at Trip Advisor and Expedia. Before I buy a book, I read the customer reviews at Amazon.com. The library now provides the same convenience. Before I check out another book, I'll read other people's reviews before I spend my time on a book that won't meet my expectations.

While I trust my friends about some topics, books and vacations are a different story. I need to depend on my semantic relationships. Those real people who have already read the book will be more useful than some pretentious reviewer or uniformed friend.

One of the primary tenets of Web 2.0 is allowing people who don't possess special skills to update content regularly and distribute it easily. Blogs, wikis, and podcasts are examples of technologies that support this tenet, and YouTube, Flickr, and Facebook are examples of implementations.

Emails, phone calls, newspapers, newsletters, and websites are all great ways government entities have been distributing content to citizens. Widgets (a.k.a. widgets, gadgets, badges, modules, and many other monikers) are another possibility. Widgets are movable, mini-applications that can be installed on most web pages, making them a perfect example of a Web 2.0 technology.

Google, AOL, and Yahoo! all allow users to add widgets to their personalized home pages. Common uses are weather forecasts, stock price updates, and news feed widgets.

20080416-AddiGoogWidgets.png




Amazon also provides widgets that allow users to add product catalogs and other interactive devices to websites.


20080416-AmazonWidget.png






Widgets are extremely popular with web users, especially 18-25 year olds who are adding them to their MySpace and Facebook pages in large numbers. Widgets are also big business. Some of the most popular of the 14,000 widgets available to Facebook users are produced by Slide, a San Francisco-based company. Slide's widgets include SuperPoke and FunWall. Fidelity and T. Rowe Price recently invested $50M in Slide.

Users can find and add widgets through personalized portal applications, like Google, Yahoo!, AOL, and Facebook; directly from the creator, including Amazon; and from widget galleries, such as Widgetbox and SpringWidgets.

Governments are also participating in the widget revolution, check out the widgets offered by FBI, NASA, and Veterans Administration.

The ROI for creating and distributing widgets is still difficult to quantify, but reaching citizens where they live, work, and play is always valuable to government. GovDelivery is experimenting with widgets that will allow our government clients to distribute their content across the web. We're excited about the future of this content distribution technique and will continue to monitor its evolution.

Email is clearly the most efficient way for governments to reach citizens. According to David Daniels, Vice President of JupiterResearch, "87% of Consumers online time is spent reading their emails" (Dec. 2007).

Not surprisingly, most citizens use common operating systems, browsers, and email clients to register for subscriptions and read their email.

More than 95% of citizens registering for government subscription options hosted by GovDelivery use a computer equipped with a Microsoft Windows operating system, and more than 85% use Internet Explorer. The following chart shows the browser operating system combinations for one federal government department.


02-BlogBrowserOS2.png

Email client and ISP choices are a bit more diverse, but there are still clear winners. Citizen subscribers, at a rate of 65.7%, receive government emails sent through GovDelivery at one of the top 5 email domains, including Yahoo!, AOL, Hotmail, Gmail, and Comcast. We can only assume that the vast majority of citizens are using the email clients provided by these vendors to read the messages, and not forwarding the messages to a separate email client, such as Mozilla Thunderbird or Microsoft Outlook. The following chart shows the ISP usage statistics for all GovDelivery subscribers.

01-BlogEmailClientUsage.png

The GovDelivery statistics are fairly consistent with overall US Internet usage. While it may be tempting to disregard the small minority of users who use Macintosh, Linux, or PalmOS, government serves everyone. When it is viable, I know that governments want to accommodate these users.

Accommodating email clients and operating system/browser combinations includes avoiding commonly unsupported content, like Flash, javascript (or other scripting languages), or large attachments. It also includes sending emails using common protocols, like Multi-Part MIME or Plain Text that most email clients can render. As technology evolves, and more citizens use more mobile devices to access their email, being flexible will be even more important.

About this Archive

This page is a archive of recent entries written by Brett Berntsen in April 2008.

Brett Berntsen: May 2008 is the next archive.

Find recent content on the main index or look in the archives to find all content.