Posts Tagged 'UX'

CHIFOO part deux

Two observations on my second CHIFOO meeting:

  1. I’m batting 1000 for striking up random conversations at the preceding CHIFOOd event and then finding out later that the person was the night’s speaker. This is despite having previously read about the nights’ topics and seeing photos of said speakers. Thankfully, both speakers were very approachable and seemed to regard contrary points of view as springboards for discussion rather than dismissing me as being argumentative (which would not entirely be a stretch of the imagination).
  2. As the night’s main presentation began I noticed that in a room full of usability geeks the preferred method of note-taking was pen & paper.

Back to the Future

Browsing the web has changed plenty since the debut of the dub-dub-dub in the early 1990s, but the basic design of the graphical web browser is still remarkably similar to the first entries in the field. From NCSA Mosaic 1.0 (1993) to Internet Explorer 6 (2001) to Google Chrome 14 (2011), a degree of consistency has been firmly established and users now have solid expectations about the core functions of the browser.

So when a website decides to roll its own navigation controls and warns, “Don’t use your browser’s Back button,” it places an enormous cognitive burden on the user. By explicitly warning users not to follow their instincts, the website developer is implicitly acknowledging the likelihood that users will rely on those instincts.

The recent push by browser developers to reduce browser chrome to all but the bare necessities means that the Back button is one of the few UI elements outside the web content itself. All browsers place the Back button in the prominent upper left corner; some browsers go as far as making the Back button larger than the Forward button, thus making the Back button the largest and most visible widget in the browser. Telling users to simply forget about that very large and very useful button is not a recipe for success.

“But my website is special! It’s OK.” No, it’s not. Jakob Nielsen’s Law of the Web User Experience states that “users spend most of their time on other websites.” And if you design a website that will fail under normal expected usage, you can bet that they will spend all of their time on other websites.

Gettin’ Higgy wit It

Human interface guidelines go far beyond the idea of a simple visual style sheet — “Buttons should have X units of padding” or “Window title bars should be dark gray” — and provide a comprehensive framework for developing consistent and enjoyable user interfaces. As my interest grew in the overall user experience, I dove into the HIGs for the major desktop environments: Mac OS X, Windows, GNOME[1], and KDE. The level of thoroughness and strictness of each HIG roughly mirrored my layman’s opinion of each environment, though there were some surprises.

Mac OS X

Far and away the most useful HIG in my opinion. Sure, Apple has been known to deviate from their own HIG (sometimes in baffling, trivial, or confusing ways), but the baseline from which they work is much clearer in both explicit specifics and its implied intentions.

Of particular interest to me were the menu guidelines, for both the menu bar and contextual menus. I was working on improving both menu types in a major product for the company I was working for at the time, and Apple’s HIG provided clear guidelines on how to standardize the common elements and rationale for managing custom elements. One thing which sets Apple’s HIG out from the pack is that it doesn’t shy away from explicitly telling you not to do something (contrast with the Windows HIG, below).

OS X Lion’s bothersome tendency towards skeuomorphic nonsense notwithstanding, Apple is unsurprisingly the leader when it comes to defining the user experience of their platform.


The Windows HIG is expansive, but it suffers from the platform’s long history of allowing a myriad of ways to accomplish any given task. The ability to say no is an important quality of any editor, and the strength of the Windows HIG is sometimes diluted by allowing similar widgets which operate in subtly different ways. If developers don’t have a clear directive of which widgets to use for a given situation, it stands to reason that most users won’t grok the differences in behavior when one developer chooses A and another chooses B.

I’ll be interested to see what the Windows 8 HIG looks like, as the Metro UI will require a tighter rein to maintain a consistent experience.


Having only using Linux in general and GNOME in particular sporadically at best, GNOME’s HIG turned out to be a good deal more thorough than I expected. Concise guidelines for most standard uses were provided, and importantly, explanatory text was included to help define the rationale. This supporting text helps to inform decisions when a situation is encountered that is not explicitly covered by the HIG.

As one might expect the GNOME HIG is not as comprehensive as the Mac OS X HIG (or as restrictive, some might say), but it does show that a collaborative project can execute a clear vision.


I have had the least hands-on experience with KDE. Working primarily from a vantage point of the stereotype that KDE appeals to the most devoted hackers and tweakers, I found the KDE HIG to mostly reinforce that view. In contrast with the GNOME HIG, which gave me a real sense of the GNOME design approach, the KDE HIG was an incomplete collection of loose guidelines. That’s not to say anything directly about the KDE environment itself, but the HIG didn’t paint a very clear picture. One might infer that a lack of clearly defined guidelines would manifest itself in the end user’s experience, but I’d have to demur on that point out of personal inexperience with KDE.


Evaluating these HIGs individually and collectively was an enlightening exercise. Not only did it sharpen the focus of each platform, but seeing where there was (and wasn’t) common ground between the HIGs provided a universal de facto desktop standard of sorts.

HIGs are also available for each of the major mobile platforms — iOS, Android, and Windows Phone 7[2]. The design choices outlined in each provide a look into both current and future mobile development, and as OS X Lion and Windows 8 are demonstrating, possibly the future of the desktop as well.

  1. This was prior to GNOME 3.0. I’m looking forward to exploring both GNOME 3.0 and Unity when I get the time, and I plan on posting after my first hands-on experiences with them.
  2. webOS also has a HIG, which could be an interesting read, but perhaps of muted practical relevance.


After receiving a tip to check Calagator (calendar + aggregator) for tech-related events in the Portland area, I decided to attend the October meeting of CHIFOO (pronounced “ky – FOO”), the Computer-Human Interaction Forum of Oregon.

First on the agenda was the “CHIFOOd” meet-up at a pub[1] for some food, drinks, and discussion, which proved to be a good introduction for a newcomer like myself. The speaker for the night’s event (who I arbitrarily sat down next to before realizing who he was) proved to be as approachable and talkative as anyone else there. And perhaps fitting for a meeting of people who explore the human side of computer interaction, it was there that I first heard that Steve Jobs had died that day.

After polishing off some sliders and pints[2], it was time to amble over a few blocks to the main event. Thomas Tullis presented a program titled, “Why It’s Time to Move Beyond the Usability Lab,” which discussed a number of engaging examples of how and why to explore options beyond the traditional methods. In addition to keeping the floor open for quick questions during his presentation, several times during the program all in attendance were able to participate in live polls via text messaging. (I did acquiesce and buy a cheap-o burner mobile phone before embarking on our cross-country drive. I had the phone on me that night and abstained from voting in the first poll, but eventually gave in for the second and subsequent polls. Damn you, snakes!)

All in all, a very interesting program and a group whose meetings I’m sure I’ll be attending more of in the future.

  1. In spite of (because of?) Calagator’s technology focus, “beer” is one of the most prominent entries in the site’s cloud tag.
  2. This pub in particular offers the choice of US or Imperial pints. I was tempted to ask for metric, but ultimately restrained myself.

Self-checkout lanes are checking out

It turns out that my avoidance of self-checkout lanes at supermarkets wasn’t just a demonstration of my personal tendency to be a stubborn old curmudgeon: major chains like Albertson’s and Big Y are phasing them out in favor of standard service lanes (,

Of the many things I have principled objections to, using automated tools isn’t one of them — my use of ATMs vs human bank tellers is easily 20:1 in favor of robots, for example[1]. But tools have to fit the job, work well, and most importantly, offer a noticeable benefit to the end user. Self-checkout lanes at supermarkets, in my experience, offered fewer advantages than they did drawbacks. Though there was a chance of enabling a speedier exit from the store, it was more likely that I would encounter a computer barking at me that there was or wasn’t some expected item in the bagging area, an item or coupon that couldn’t be scanned, or some other unspecified failure which required a manager’s attention.

These problems highlight how important it is to consider the overall user experience. Automation may be alluring to a business looking to shave costs, but when its effect on customer satisfaction is considered, the total cost of ownership may be much higher than expected. (Not to mention some of the other concerns mentioned in the linked articles, such as intentional and unintentional theft.) Sometimes a new technology just isn’t better than its predecessor.

  1. ATMs are often finicky and have a slew of minor usability issues of their own, but nonetheless generally earn a passing grade. I’ll be signing up for a new bank soon, so mayhap a future post will chronicle my first attempt to bumble through an ATM system I’ve never used before.


Flickr Photos