Reported by the Telegraph today:
Those applying via computer or mobile phone for services ranging from tax credits, fishing licences and passports will be asked to choose from a list of familiar log-ins to prove their identity… Under the proposals, members of the public will be able to use log-ins from “trusted” organisations, chosen to appeal to as wide a demographic as possible, to access Government services grouped together on a single website called Gov.uk… A user logging onto the site by phone would be asked to choose to select from a logo from one of the trusted brands, such as Facebook.
Two days ago, on the blog of email newsletter service MailChimp:
[We were convinced] that adding social login buttons to our app were essential to improving our depressing failure rate… I was shocked to see that just 3.4% of the people that visited the login page actually used Facebook or Twitter to log in.
Even a 3.4% drop in failures is worth having them there, right? Maybe not… Do you want to have your users’ login credentials stored in a third-party service? Do you want your brand closely associated with other brands, over which you have no control? Do you want to add additional confusion about login methods on your app? Is it worth it? Nope, it’s not to us.
Of course, the MailChimp position is slightly undermined by the use, immediately below this very blog post, of ‘Sign in with Facebook’ and ‘Sign in with Twitter’ buttons on their comment form. They argue in the comment thread that commenting is a very different user scenario; and it’s a view I have some sympathy with.