Designing fast sign in forms – diving into the data

https://www.clerk.dev/blog/designing-fast-sign-in-forms

by colinclerk • 5 years ago

7 2 5 years ago

But, Social Sign In was faster: ~5 seconds on average compared to ~8 seconds for email and password.

No wonder, you put email and password on separate pages! If you had exposed both fields on one page, email + password logins would be faster.

colinclerk• 5 years ago

We actually have a PR in review to fix this if you're using a password manager: https://user-images.githubusercontent.com/1811063/121708843-...

We put a hidden field on the page to accept a password from a password manager. If the password manager fills it, we expose the field to indicate the password was received.

---

The second page is helpful for users who originally sign up with Facebook/Google, and therefore don't have a password to enter on the first page. (It's also helpful for SAML, but we don't support SAML quite yet.)

Edit to add: Even if we had email/password on one page for everyone, I would still expect Social Sign In to win.

We don't actually have telemetry on password manager vs keyed, but the way things are distributed we can make an educated guess. I'd guess that PW manager users have a chance at beating Social Sign In users, but too many are still keying their passwords for passwords to win overall.

Thanks for another blog idea :)!

Designing fast sign in forms – diving into the data

Related Stories