Skip to content
Book a call
UI Design

Passkeys and sign-in UX

Passkeys are supported by major browsers and platforms. We cover when to offer them, how to keep passwords as a fallback, and what copy helps users say yes.

MD Rakib Shekh5 min read
Cover illustration for the article "Passkeys and sign-in UX"

Passwords are a pain for users and a risk for products. Passkeys are the most promising replacement, and major browsers and platforms now support them. But supporting passkeys technically is only half the work. The other half is getting people to understand and use them.

This is the guide we would give a SaaS team adding passkeys. If you want us to look at your sign-in flow, a UX audit includes exactly that kind of review.

What passkeys are, in plain words

A passkey is a way to sign in without typing a password. It is based on public-key cryptography and the WebAuthn standard from the W3C, and the FIDO Alliance promotes it as a sign-in method. In simple terms:

  • Your device holds a private key that never leaves it.
  • Your account holds the matching public key.
  • To sign in, you prove you are at your device, usually with a fingerprint, a face scan or a device PIN.

Two features matter for design. Passkeys cannot be typed into a fake site, which makes phishing much harder. And on the big platforms they can be synced through the user's account (such as Apple, Google or Microsoft), so a new phone does not mean a lost login.

Users do not need this explanation. They need three things: it is faster, it is safer, and it uses the same fingerprint, face or PIN they already use to open their phone.

Offering passkeys at sign-up

The best time to offer a passkey is right after the user has signed up or signed in successfully by another method. They are present, they are trusting the product, and they know it worked.

  • Offer, do not force. A card or a short step saying "Sign in faster next time" with a clear "Create a passkey" button and a visible "Not now".
  • Keep it to one step. The system dialog does the hard work. Do not add a long explainer before it.
  • Confirm the result. "Passkey saved. Next time, use your fingerprint or face to sign in." Show which device it is on.
  • Do not nag. If someone says "Not now", wait a while before asking again, and let them stop the reminders.

On the sign-in page, the browser can suggest saved passkeys right in the username field. Setting autocomplete="username webauthn" on the field enables this, as described in the WebAuthn guidance on MDN. For users with a passkey, signing in can then be a single tap.

Fallbacks and recovery

This is where products get hurt. If passkeys are the only way in and a user loses access, you have a support problem or a lockout.

  • Keep another method. A password, an email link, or a code, until you are confident users have a backup.
  • Encourage a second passkey. On another device, or in a password manager that supports them.
  • Design the "I can't use my passkey" path. It should be easy to find on the sign-in screen.
  • Recovery must be at least as strong as the passkey. If anyone can reset access with an email alone, the attacker simply goes through recovery. Decide what proof your product needs.
  • Let people manage passkeys in account settings: see the list, give each a name, and remove the ones they no longer use.

Treat the first release as an addition to existing sign-in, not a replacement. Remove passwords later, if ever, once you have seen how people behave.

Copy that explains

Words matter more than usual here, because "passkey" is still a new word for many people.

Write short, concrete lines:

WeakBetter
Enable passkey authenticationSign in with your fingerprint, face or screen lock
Passkey creation failedWe couldn't save your passkey. You can try again, or keep using your password.
Register a new credentialAdd a passkey on this device

Other tips:

  • Use the word "passkey" consistently, and explain it once in a sentence.
  • Say what will happen before the system dialog opens, so it does not feel like a surprise.
  • When something fails, say what the user can do next. The system dialogs differ across devices and the error codes are not friendly.
  • Avoid scary security language. Calm and clear does more.

Shared devices and work laptops

Passkeys are tied to a device or an account that syncs. That raises questions in a few cases.

  • Shared computers: a passkey saved on a shared machine could let the next person in. Ask "Is this your own device?" before offering one, or add a note on public computers.
  • Work laptops: a company may block syncing, so a passkey might exist only on that laptop. Tell users that, and nudge them to add a second method.
  • Cross-device sign-in: a user on a desktop can often use a passkey stored on their phone by scanning a QR code. Make sure your interface does not get in the way of that flow.
  • Team accounts: if several people share one login, passkeys will expose the problem. A better fix is individual seats.

Support load

Done well, passkeys cut password resets. Done poorly, they create a new kind of ticket: "I got a new phone", "It asks for a QR code", "My laptop doesn't have a fingerprint reader."

Prepare for this:

  • Write a short help page that uses the same words as the interface.
  • Tell your support team how recovery works and what proof they may ask for.
  • Log passkey events (created, used, removed) so staff can see what happened.
  • Watch where people drop out of the flow in your analytics.

Checking your own flow

Try this today. Sign in to your own product on a phone and on a laptop, once with your password and once pretending you lost your phone. Where do you get stuck? That test shows most problems.

If you would like help, we can review sign-in and onboarding for your SaaS product and send back a clear list of fixes. Start with a free design review at the contact page.

Want a second pair of eyes on your product?

Send your site or app and get a free design review from Rakib. No sales call, no cost.