Posts tagged usability in 2007
Filters: Year: 2007 × usability × Sorted by date
OpenID and Google’s Blogger. Blogger gets it wrong by displaying a nickname derived from the OpenID URL (in Malcolm’s case, “blog”) instead of the user entered nickname.
But here's the thing: Regular people on the web love Snap previews. I know you don't believe it - I didn't want to believe it. But it's completely true. In the testing and feedback I've seen, it's some emotional pull about the fact that links "do something" now, instead of just being on the page.
If It Looks Like a Cow, Swims Like a Dolphin and Quacks Like a Duck, It Must Be Enterprise Software. Interesting discussion about why enterprise software tends to completely suck from an end-user point of view.
Radiohead Album Available for Free, But Fileshared Anyway. “Why are some people getting In Rainbows from P2P rather than the band’s site? Probably because they find P2P easier to use.”
The arc of TF2 is something that's probably familiar to a lot of amateur developers or designers. When we got here the first thing we built was overly complex, very hard core, almost impenetrable to anyone who wasn't familiar with FPSs in general. And as we found as we played it, wasn't more fun because of it.
Amazon makes you lie to log off (via) Amazingly, the only way to sign out of Amazon these days is to use the “If you’re not XXX, click here” link—the traditional “sign out” link has quietly vanished.
Halo 3 Site Demonstrates Flaws in SilverLight. The Halo 3 “interactive manual” is like a throwback to Flash in the late 90s—“skip intro”, pointless transitions, text you can’t select or enlarge, links that aren’t links—all wrapped up in an ugly blob (only this time it’s XML instead of binary data).
Jottit. Aaron Swartz’s latest venture: a complete rethink of the Infogami concept. Well worth checking out for the extremely thoughtful way it introduces features, and the way account creation with a password remains optional until you want to add access control.
I've actually been using the latest version of JAWS recently, as part of my work on HTML5. From a usability point of view it is possibly the worst software I have ever used. I'm still horrified at how bad the accessibility situation is. All this time I've been hearing people worried about whether or not Web pages have longdesc attributes specified or whatnot, when in fact the biggest problems facing blind users are so much more fundamental as to make image-related issues seem almost trivial in comparison.
Primary & Secondary Actions in Web Forms. Fascinating results from an eye tracking study on the placement of “Submit” and “Cancel” buttons—one layout was a whole six seconds slower than the others. Luke Wroblewski’s “Web Form Design Best Practices” book looks like it will be excellent.
In 1997, I chose to suppress a similar finding: users tend to click on banner ads that look like dialog boxes, complete with fake OK and Cancel buttons.
OpenID: Great idea, bewildering consumer experience. Realistic, detailed look at the many usability problems that currently surround OpenID—and a good list of suggested fixes at the end. This is why I’ve been advocating OpenID as a tool for early adopters: they can help smooth out the experience for everyone else.
Dynamic Help in Web Forms. Luke Wroblewski catalogues patterns for providing contextual help.
E-Trade financial tried using a RSA fob as a second factor of authentication, but as of their 11/07/06 financial report their fraud losses continue to increase. That said, they considered this program a success because users indicated they feel safer and are more likely to provide assets.
Never use a warning when you mean undo. The abundance of “undo” is one of my favourite things about Gmail. I wonder if there’s anything Django could do to make implementing undo functionality easier...
On any given Web page, users will either click something that appears to take them closer to the fulfillment of their goal, or click the Back button on their Web browser.
You need to lay out the user interface components visually, by hand, with total control over where they go. Automated LayoutManagers don't cut it. A corollary of this is that you can't move a UI layout from one platform to another and have the computer make everything fit. Computers don't lay out interfaces by themselves any better than they can translate French to English by themselves.
In Which I Think About Java Again, But Only For A Moment. Convincing argument as to why desktop applications written in Java rarely have decent user interfaces.
The way you make users understand your program model is with metaphors. When you make things look, feel, and most importantly, behave like things in the real world, users are more likely to figure out how to use the program, and the app will be easier to use. When you try to combine two very dramatically different real-world items (email and appointments) into the same kind of thing in the user interface, usability suffers because there’s no longer a real-world metaphor that applies.