Personally I think that OpenID is the next best thing since sliced bread. I plan to use it on all my personal projects and advocate it whenever I can.

However, when I have to explain OpenID, and if they understood, it then raises a foray of debate - which is fine, but I don't want to argue just to get my user to log in.

My approach from here on in is to stop using OpenID. That is I'll reduce the presence of OpenID at the front line (i.e. what the user sees) but continue as it suites me behind the scenes.

UK EVENTAttend ffconf.org 2024

The conference for people who are passionate about the web. 8 amazing speakers with real human interaction and content you can't just read in a blog post or watch on a tiktok!

Why?

  • Your user should not care, or even have to know about OpenID.
  • It saves having to go in to the whole explanation of what OpenID is. My new explanation goes a little like this:

You have a Flickr account, right?

Right.

Well, you just use your username on my site, Flickr will authenticate you, proving you're really who you say you are, and on you go.

Tidy.

  • OpenIDs can sometimes be tricky to remember/get right.

For example, Technorati's OpenID caused me no end of problems. It boiled down to the Technorati OpenID requiring 'http://' at the start - whereas I can happily use 'remysharp.com' as my OpenID - regardless of the 'http' part.

In addition 'http://technorati.com/people/technorati/remysharp' is fairly long to type.

How?

The 'how' should make it even easier to get those users in to your web site. Since some of the big boys offer OpenID as part of your account, I'm going to assume that there's a large proportion of users who have an OpenID without knowing it.

  • Don't ask for OpenID urls: just ask for the username for X service, and construct the OpenID behind the scenes.

Have a look at the following example (taken from Code Dumper's login):

You'll need to have JavaScript enabled to view the demo.

Sign in
Behind the scenes OpenID is: xxx

This example still initially points the user to an OpenID login (I'd love to get a UI designer's direction on this) - but the key effect is the ability for the user to select their login and only specify their username.

  • Use a cookie to store the selection of services the user chose. I don't want to have to keep selecting the right service from the drop down each time I log in.
  • If you can add visuals on the login: icons for AOL, Flickr, Blogger, Yahoo, etc, will immediately connect people's understanding that they're logging in to that service, not only in the input field as above, but perhaps horizontally introducing the log in.

Next time I'll show you how to glean an avatar for your user without any input from them.