I have implemented janrain's social login on my website. I am wondering how important it is to include a traditional login (email/password) system.
I believe there may be a significant percentage of potential users that are either uncomfortable or unfamiliar with social login. These users may not sign up for my site if social login is the only option.
Does anyone know of any data comparing social login vs traditional login and the corresponding adoption rate?
Is there a current best practice? Do I need to give the user an option to sign up using username/password? Or is facebook/google/openID/twitter/MS/Yahoo enough?
Answer
The usual answer to this is: it depends. But what does it depend on you ask? Good question.
It depends on, firstly, how tightly integrated your application is into the social applications whose logins you are offering. If you need the functionality of say Facebook, then only offering Facebook integration is justified. Very often we would only like to have the data (e.g. name, avatar, age, etc.) and so forcing a Facebook login doesn't improve the experience for everyone.
Then, secondly, it depends on how likely your target audience is going to either not have a social account from one of the social apps which you are allowing logins from, and whether they are willing to use them. Many business people wont have a Facebook account, but they are very likely to have a LinkedIn account (depending on the country). Many people don't like using social logins and prefer traditional accounts for each application they sign up for.
If there isn't some good (UX) reason to leave out a traditional sign in, I would strongly urge you to include one. The onus is on you to decide if there is a good (UX) reason to leave one out or not.
No comments:
Post a Comment