This questions comes up a lot. It really comes down to your specific Product and the nature of your users. Are you selling a Social product that ideally talks t

This questions comes up a lot. It really comes down to your specific Product and the nature of your users. Are you selling a Social product that ideally talks to Google/FB/Twitter anyway ? Sure, go ahead and provide Social Logins. Are you selling a B2B SAAS that has nothing to do with Social stuff ? I am not comfortable giving you access to my Google/FB/Twitter then. I don't care about OAUth and stuff. Also, whats the big deal these days implementing a basic email/password based login. All the popular backend languages (PHP, Node, Golang, Ruby etc) have libraries or frameworks that provide email/username auth out of the box. One example: Laravel in PHP. You literally do "php artisan make:auth" and it sets up the scaffolding for login, registration, forgot password pages and of course uses bcrypt to hash passwords. I am sure other frameworks have similar options. So this is a not one size fits all type of answer. You have to look at your users, their preferences and the use cases. But if in doubt, just implement a basic email/username auth. It never hurts and I would argue is not that big of a deal these days to implement due to the frameworks that are available.