June 23rd 2007
A New Paradigm for Design
I feel that we’ve reached an interesting point in software design as web applications become more interactive. Regardless of what the UI guidelines for your given platform detail, the real goals of design as I see it are:
- Familiarity: Is the user able to use your application by leveraging existing knowledge learned from other applications?
- Simplicity: Do you really need those 50 checkboxes of options for your advanced search?
- Ease of Use: Does a user need a manual to use your program?
I don’t believe that UI guideline conformance belongs on this list of design goals, and here’s why: With more and more content being delivered as web applications, the rules of design have changed because what the user is most familiar with is their browser and the web applications they routinely use. I feel that desktop software currently still has the best potential to deliver the best user experience, but I also feel that web applications are often kicking the butt of desktop applications in terms of the above three metrics.
And what I’m seeing is that the programs who throw out conventional desktop application design can often yield a better experience. A few quick examples: Delicious Library, NetNewsWire 3, Coda, and iLife. These applications use custom interface elements for portions of the program because they provide a more familiar and simpler way of presenting and interacting with “data.”
What’s interesting to note is that none of these programs are without competition. In fact I knew someone with a Delicious Library-like application that was released before Delicious Library, and it followed the UI standards down to the button. However, that application never took off while Delicious Library quickly became an extremely popular application and sparked the “delicious” revolution in many developers’ imaginations.
Let’s take a closer look at an application that I recently replaced with a web app: NetNewsWire. It’s interesting because I had a draft of an article talking about this mentality change after I had switched from NetNewsWire to Google Reader. The reason? Two-fold actually — the syncing feature in NetNewsWire didn’t work that great, and I preferred the simplistic UI of Google Reader over NetNewsWire’s three-pane approach. After beginning writing the post, I noticed NetNewsWire 3 was announced. I must confess I haven’t retested syncing, but the interface: it now offers a similar interface to that of Google Reader!
I find this progression interesting, because I know NetNewsWire wasn’t the only RSS reader that used the three-pane approach. While I won’t claim that these programs copied Google Reader or Blogline’s UI, I find it interesting that the default implementation of how the “web guys” solved it has become the best UI on a desktop application. To this extent, I believe designing your program as if you were going to make it a web application may inspire new ways at solving information display issues.
Common user interface guidelines are good for certain things like forms or dialogs. However when designing the core portion of your application, try to be creative and solve the problem in the best way imaginable.
