Why OpenID sucks from a user experience perspective

Many people seem to be touting OpenID as the next big thing in authentication. Early adopters request it, web geeks love it, and sites having it claim to be easier to use and more modern. The idea of maintaining only one login to access everything else sounds like a great idea until you thoroughly examine it. I personally have been considering the concept, especially since many Cashboard customers are requesting OpenID login as a feature addition.

What problem are we solving exactly?

The first gripe most people have with regular login systems is memory. There’s no doubt about it, maintaining all of the login information across your accounts can become tedious.

I personally have about 40 web logins and passwords I have to maintain for various services. The idea of having only one login to remember is nice, but is this really a problem?

Today all browsers allow you to save your login/password information, and if you’re worried about security you can always use a program to manage your passwords which also encrypts everything for safe keeping. Most password managers also have mobile versions for your phone so you can take login information with you on the go.

Replacing non-problems with confusion

OpenID claims to solve this memory "problem" another way, by providing one password to rule them all. It sounds good in theory, but in reality quickly it falls apart from a usability perspective.

I stumbled across a great article that explains the usability downfalls of OpenID which I suggest you check out. I won’t rehash all of the discussion there. Rather, I’d like to take a look at a real world example I personally ran into on Stackoverflow.

Stackoverflow login screen

One can imagine the following thoughts racing through the average web visitor’s head when this screen initially pops up.

  • Huh?
  • Where’s the username and password fields?
  • I like Google, but don’t like Yahoo. Should I click Google?
  • What do I type here?
  • What’s my OpenID URL?

Even those that know what OpenID is could be challenged when presented a screen like this. I personally have a Google account, 2 Yahoo accounts, a WordPress account, and an AIM/AOL login. Which one do I use to login here?

At least with the majority of my other accounts I use a standard email address which I’ve been conditioned to remember. OpenID invents a whole new bag of problems, this being just the first.

New problems being invented with OpenID

I’ve actually logged into Stackoverflow before and had linked it with my Yahoo account. Returning to the StackOverflow site to ask a question I attempted to login with my Yahoo OpenID once again. The problem is, now Stackoverflow didn’t recognize my Yahoo OpenID.

Instead of being logged in after completing the OpenID process I was greeted with this screen.

OpenID not found

I thought I must have forgotten which OpenID I used to login. Perhaps it was my Google account? Nope, not that one…not any of them in fact.

Feeling frustrated I finally stumbled to this page which is supposed to email your forgotten login information. I played roulette with my different email addresses, finally hitting one that it found acceptable.

When I received the "account recovery" email it told me something quite bizarre; I had linked my account to my Yahoo/Flickr OpenID. The problem is I had just deleted my Flickr account a couple of days ago thinking I would never use it again. Even though I still had a Yahoo account, I did not have my Flickr account. It turns out that you can actually have MULTIPLE OpenIDs through the same provider.

This is supposed to be better than a regular username / password combination how?

Select a Yahoo OpenID

Unfortunately there is simply no way to ever login again to the site, or reset my account to be linked with another OpenID.

What a horrible user experience.

Where do we go from here?

I’m sure the example I ran into is just one of many usability scenarios that nobody has bothered to think through. Multiple this by the number of sites implementing OpenID logins and you can quickly start to imagine the myriad of usabilty problems being invented daily.

OpenID does solve a number of interesting security problems, but at the moment I think it’s not mature enough from a usability standpoint to be useful.

I hope the interaction problems surrounding OpenID continue to be worked on, as Yahoo is doing. They’ve conducted a very thorough usability study on OpenID, which I encourage you to read if you’re interested in the topic. It appears they’re making progress, but at a slow pace.

Alternatives

There seems to be a few great implementations of Facebook connect and Twitter oauth starting to pop up around the web.

I really like what Disqus is doing with blog commenting and linking to the social web, and I’m sure we’ll continue to see more interesting alternatives appear.

I’m interested to see where things go from here. Have you seen any great implementations of OpenID yet? Share them with me.

seth, Thu, 18 Feb 2010 01:48:00 GMT
2 comments

Designing like an engineer is bad for business

Making great software is a huge challenge.

The challenge only gets harder for those that have to wear multiple hats because of constraints, self-imposed or otherwise.

As most readers of the blog know I act as the main designer and developer for Cashboard (shameless plug #10384). This situation arose from many factors, but the main one being I wanted to get the product up and running under my own power. I’ve seen too many projects fail and I didn’t want anyone to blame on this one but myself.

I tell most people I’m a designer first, but I program out of necessity. Anyone in the software engineering field knows this is usually a bad idea and results in a shit product, yet I believe I’m able to pull it off because I’m able to "switch modes" or "switch hats" most of the time.

I’m damn good at what I do, but I’m definitely not above the classic problem. I routinely have to catch myself "designing like an engineer" instead of designing as a user experience person. Case in point, Cashboard’s "Account Preferences" screen.

The old screen is shown below in all of it’s fucked up, cluttered, and confusing failure.

Old Cashboard preferences screen

This particular screen was built over time. Sections were added as the product grew, and it shows.

The design made complete sense to the programmer side of my brain. Sections of the screen directly map to functions of the code. As it usually turns out in situations like this, it was the exact wrong way to approach the design of that screen.

Non-relevant information is shown which clutters the view and detracts from the goal at hand. Things aren’t logically grouped from a customer’s point of view, and worst yet the screen has an overall busy look that’s quite perplexing.

There are two forms on the page, with two buttons, and a link to update other relevant information on yet another screen. (yuck!)

Preferences Screen Remix

Finally fed up with the design I took it upon myself to give that screen a makeover. Putting on my designer hat I busted out the design documents necessary, re-assessed the goals of customers visiting that screen, and had a revelation.

Customers of the app visiting this screen just want to update their preferences. They don’t care that changing their currency is a different operation from setting their date formats or billing address on the back-end, and they shouldn’t have to.

As with most design breakthroughs, this one was sitting right in front of my face. The solution was plainly there, yet I was missing it up until now because I wasn’t paying attention.

New Cashboard preferences screen

The updated design eliminates unnecessary information presented from the first screen, brings the "billing address" fields into the mix, and consolidates the multiple forms into one.

The result is a much cleaner looking form that actually makes sense for the goals at hand and is pleasing to look at as well.

As someone once told me – it doesn’t cost a thing to pay attention, but not paying attention can cost you dearly. True words indeed.

seth, Mon, 22 Dec 2008 21:02:00 GMT
3 comments

Minority Report interface is real

I’m one of those people who always used to complain about the "hacker" computer interfaces presented in most movies. People breaking into computer systems in minutes with pretty graphics and pictures zooming by. I find them an assault on my throwback days of hacking Taco Bell billing systems, hotel climate controls, and unprotected unix boxes. What can I say, I was young and bored…

Despite this fact, I’m also a sucker for those futuristic computer interfaces presented in movies like Minority Report, and the new 007 movie.

Imagine my shock when I ran across this video today showcasing that a group named Oblong Industries has recreated the Minority Report interface for real!

seth, Sat, 15 Nov 2008 22:29:00 GMT
1 comment

OS X Leopard and Cashboard, sitting in a tree

In the spirit of feeling (and being) productive, I’ve started tracking all the development hours I spend working on Cashboard. Up until now I’ve skipped it, estimating how long I spend working on it every month. It’s interesting to see exactly how much time it takes to get things accomplished, and keeps me motivated on those days I don’t feel like working. I also finally took the plunge and upgraded my development machine to Mac OS 10.5.4 yesterday. One of the great things in Leopard I’m enjoying so far is the web clip capability. It allows you to select any part of a web page, and use it as a desktop widget.

Cashboard widget and web clip, getting along

I’ve created a web clip widget to display all of my hours from inside Cashboard. It’s positioned right next to my Cashboard time tracking widget. Now I know how long I’ve worked, and I can keep tabs on how many more hours I need to put in for the rest of the day. Interesting feedback loop, if nothing else.

seth, Sat, 06 Sep 2008 07:45:00 GMT
no comments

When it rains it pours

I like all of the custom maintenance messages sites have these days.

Here’s one from one of my favorite music apps, SoundCloud.

SoundCloud maintenance page

seth, Tue, 26 Aug 2008 21:31:00 GMT
1 comment

Drooling over this music controller surface

I’ve been trying to justify the price of a JazzMutant Lemur or Dexter for quite awhile, but these pictures just make it harder to hold off.

Both are multi-touch control surfaces.

The Lemur comes with its own programming software which allows you to create your own interface for whatever audio software you run – while the Dexter comes pre-programmed for most digital audio workstations like Cubase.

I love to see designers breaking the norm and bringing the future to us today.

seth, Wed, 02 Apr 2008 03:46:00 GMT
no comments

Unique flash interface

It’s been awhile since I’ve really checked out any great flash interfaces.

Stumbled across this clean design today off of another site.

Slick.

seth, Mon, 18 Feb 2008 16:56:00 GMT
1 comment

GMail gets colored labels...Cool.

Just logged into my GMail account to find the Goog gang launched a new UI feature, colored labels. I geek out about small but great UI features like this.

I use my GMail account mostly for discussion lists and groups, which I auto-tag with labels. Great for keeping track of e-mail you don’t want clogging your regular account – and also a great targeted search resource when you’re looking for answers to technical problems you care about.

Of course, by default with this setup my inbox is usually a sea of things that I don’t immediately care about.

...Enter colored labels. As you can see, I’ve colored a couple of things I really care about which jump out now when I’m scanning my inbox. Killer.

seth, Wed, 05 Dec 2007 06:01:00 GMT
no comments