top | item 40885970

(no title)

Wronnay | 1 year ago

Your app will be held back by requiring to create an account with email and password.

Most of the users just use "Login with Google" or other well known OAuth providers and also want to try the product before creating an account.

When I switched from user / password to OAuth I couldn't believe how many users choose it. I could deactivate traditional user & password login and nobody would notice it.

discuss

order

xavdid|1 year ago

That's fascinating! I mostly don't use "sign in with X" anymore since my password manager flow is pretty fluid at this point (so making a password is easy and secure). I guess for the many people who are less comfortable with password managers, a 1-click sign up/in is very useful.

Thanks for sharing!

lygaret|1 year ago

I'll add my 2c, and say that even with a really fluid password manager flow, "signin with X" is usually a 1-click entry (possibly 2 for scope authorization), rather than a signup form + leaving the site to click through an email verification.

I'd much prefer 1password to do it's "you last signed in with github here" popup, than just have easy new passwords created.

osigurdson|1 year ago

Having a password manager plug-in thing installed on every web browser that I might use seems pretty arduous to me (not to mention I also then have to trust the plug-in). The fact that LastPass for example had a major breach doesn't help either.

IndySun|1 year ago

Why do you say "most users just use google" to login? What is this based on?

osigurdson|1 year ago

So it seems to be based on their own experience. The parent comment says this:

"When I switched from user / password to OAuth I couldn't believe how many users choose it. I could deactivate traditional user & password login and nobody would notice it."

saghm|1 year ago

Based on the paragraph following the part you quote, it sounds like it's based on what they've seen in their own app.