Like most anything else in this business, it comes down to your users. If they don't know about OpenID already, are they the kind who'll accept it readily? Can you educate them easily? If neither of these things is true, I'd recommend against it
<br><br>If you don't know the answers, I advise user testing<br><br>I do have some examples:<br><br>Tim Lucas and Cameron Adams released <a href="http://meetweaver.com/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://meetweaver.com/</a> at Web Directions South last month. It uses OpenID only, but it has a very specific audience and could be supported (during the conference) by face-to-face explanations/coaching<br><br>Tim wrote that OpenID Rails code for the as-yet-unlaunched new version of
<a href="http://webjam.com.au/?s=ml" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://webjam.com.au/?s=ml</a> (the events, not the personal homepage service). We've got a lot more guidance and help structured around the whole registration process, but we'll be OpenID only as well
<br><br>It's still going to be messy, but given our audience are all people interested in innovation on the web, we're asking them to help us push this. To find the flaws and help develop the user experience. The launch of MeetWeaver already gave us some valuable insight and we'll be doing our own user testing
<br><br>We'll publish the lessons we learn :)<br><br>Good luck!<br><br>Lachlan Hardy<br>Co-founder, Webjam<br>