On Nov 14, 12:28 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
>
> The downside is that OAuth suffers from many of the frustrating user
> experience issues and phishing scenarios that OpenID does. The
> workflow of opening an application, being bounced to your browser,
> having to login to twitter.com, approving the application, and then
> bouncing back is going to be lost on many novice users, or used as a
> means to phish them. [...]
I completely agree with Alex on the user experience issue. I've
written two
OAuth Consumer applications this year and the user workflow is
somewhat awkward.
Also, the user experience is especially poor on mobile devices.
These screenshots show what OAuth workflow looks like on an Android
phone:
http://code.google.com/p/jfireeagle/wiki/Android
http://code.google.com/p/jpoco/wiki/Android
> Another downside is that OAuth is a hassle for developers. BasicAuth
> couldn't be simpler (heck, it's got "basic" in the name). [...]
Agreed. OAuth has a non-trivial learning curve. Average developers
will
struggle with OAuth.
By the way, MySpace recently rolled out OAuth with it's REST API's.
Check the MySpace Developer forum and you'll see that many developers
are struggling with OAuth:
http://developer.myspace.com/Community/forums/t/5521.aspx
http://developer.myspace.com/Community/forums/t/5464.aspx
http://developer.myspace.com/Community/forums/t/5454.aspx
http://developer.myspace.com/Community/forums/t/5205.aspx
Cheers,
Sean