3 ms·

> I thought of using Sign in with Google instead of creating my own authentication for a new project I am building. Besides the topic regarding "roll your own

> I thought of using Sign in with Google instead of creating my own authentication for a new project I am building. Besides the topic regarding "roll your own stuff" vs "use a huge library", I would ask a more business-oriented question: would your users be alright regarding signing in to your app using their Google accounts? What if they don't have one? Email address + password is usually a good approach when it comes to login: I can always use a fake email address if I don't trust your service, whereas if only "login via Google" is enabled, I'm just going to pass.

yashg 5y ago
I guess it boils down to personal preferences. I have come to detest passwords in general. Especially a new one for each website. (Because you don't know how the site is storing the passwords). I have created a Password Manager (HexaVault.com). If I am using a new service and it asks me to create an account, I go, "Oh man not one more password". Sure I can save it in my password manager which has around 500 passwords now I guess. So if I see an option to login via some other service - Google/Facebook/Twitter/LinkedIn/Microsoft I prefer that. What I have come to like is the password-less email only login on a few sites. They either mail you a link or a code to login. Which I think is the way forward. Nothing to remember as a user.