I have hit some issues wrt ease of use of oauth in mobile apps thats causing me some grief. Some context first..I have an app handsfree.ly that leverages oauth for gmail access. I have been watching users navigate the oauth handshaking and noted these problems:
1. Entering an email address/password is very painful and most users consider this step too painful for the benefits it provides (no password storage) 2. When there are errors in #1 multiple times, a captcha is shown. This is unreadable on small screens. I wanted your opinion on these possible solutions (pl. suggest more..) 1. Add an additional parameter to the OAuthAuthorizeToken step- email_address. When control transfers to google for authorization, the email field is prepopulated with this address. User merely enters password, clicks Grant and has saved time entering a potentially erroneous long email id. http://code.google.com/apis/accounts/docs/OAuth_ref.html#GetAuth 2. Not all captchas are unreadable (on my LG Ally eg). Check out http://www.androidcentral.com/user/register Can the fancy squiggly captchas in google accounts be changed to be a lot more readable on smaller screens? rgrds. -- You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/oauth?hl=en.
