Dashboard Widgets for Fun and Profit
19 March 2009 · Estimated reading time: 4 minutes
I gave a presentation tonight to the Auckland Web Design Meetup on Dashboard widgets. Here are my slides and a little commentary for those who were unable to attend.
The slides are a bit sparse. This was intentional as I wanted folks to focus on what I was saying and not be reading massive bulleted lists of text. I’ll try to fill in the gaps in my commentary after the slides themselves. Feel free to ask for clarification or more detail in the comments.
Unfortunately, 280slides.com is no more and my slides are lost forever. This fact is not likely to make the list of significant losses to humanity.
There were 2 main points I wanted to get across in the presentation:
- Widgets are simple to build.
- Building widgets can be good for a web designer/developer’s career, even if they don’t make you rich directly.
The following is a slide-by-slide annotation:
- Title slide
- Outline for the talk
- My credentials as a widget builder—I mentioned that the number of downloads I list here is a conservative estimate because Apple.com doesn’t expose download statistics. Otherwise, I touted publicity my widgets have received, that some have been distributed on CD-ROMs with print magazines and that I’ve been interviewed on a couple of podcasts on the topic of widgets. My kids think I’m famous because my name has been in magazines. :-)
- Transition slide to “What is a widget?” section
- Graphic showing several of the default widgets that ship with Mac OS X—I made the point that widgets are simple, single-purpose mini-applications.
- Dashboard is the name for the platform upon which widgets are built.
- Dashboard’s foundation is WebKit, the HTML rendering engine used in Safari, Chrome, the iPhone and Android.
- Graphic showing the Coda workspace for my Hurl widget—The point of this slide was to show the web developers in the room how simple widgets are to build.
- Graphic showing the Hurl widget in Dashcode, Apple’s IDE for building widgets. It has advantages and disadvantages when compared to hand-coding, which is my personal preference.
- List of technologies available within widgets—There are lots of powerful things one can do with widgets, including anything you can do from the command line in OS X.
- I tried here to make a funny about the need to create tight, compact user interfaces for widgets, but the joke bombed. Anyway, my point was that thoughtful design wins over quick-and-dirty.
- Summary of “What is a widget?” section
- Take away: for a room full of web designers and developers, building widgets should feel within reach.
- Transition slide to “So what?” section
- In my experience, businesses try to do 1 of these 3 things when they build widgets. The most worthwhile is building add-ons to existing applications.
- My client, Whole Foods, tried push marketing, but obviously abandoned the effort after a bit.
- Businesses are better off focusing their effort on publishing a solid, free API and letting widgets (and gadgets, and Facebook apps, and…) come to them.
- Graphic showing several successful widgets that build on public APIs and RSS feeds
- Here, I offer 5 motivators for widget builders. I haven’t made much money off my widgets, directly. My widget work has led to some great contacts and consulting work. Many times, developers build widgets just to scratch their own itch, for some notoriety, to get better working with web technologies, and just for fun.
- Graphic showing the bobblehead widget I built for my 1000th follower on Twitter
- Snarky link to resources for further learning
- Closing slide
There were some great questions following the expository portion of my presentation. Folks asked about security within widgets (they can be made secure by using SSL and HTTP Basic Auth), tracking widget use (you could code that in, but if you do, be clear with users that your widget “phones home"), and using Google Analytics in widgets to track usage (I answered that it should work, but I’m not sure now that this will work because the “page” is only loaded once, when the widget is first loaded).
There were other questions, but I’m drawing a bit of a blank at the moment. If you were there, feel free to remind me in the comments.
Overall, indications are that people enjoyed my talk. Simon Young said on Twitter, “I want to be a widget developer now”. That’s about the highest compliment I can think of!