Conditional UI Optimizes the User Transition to Passkeys

Key Facts

Conditional UI is a WebAuthn mode that displays a credential selector only when the user's device already has a registered passkey, preventing modal dialog errors for uncredentialed devices.
The passkey autofill dropdown appears directly under the username field, showing available passkeys alongside saved passwords without requiring a separate passkey button.
Opportunistic passkey deployment is possible because applications cannot distinguish between a user lacking a passkey and a user choosing not to reveal one, eliminating UX risk.
Conditional UI enables parallel authentication transition: non-passkey logins remain fully functional while passkey users get a streamlined Face ID or fingerprint flow.

1. What is Conditional UI?#

Conditional UI , a new mode for WebAuthn, is designed to solve the bootstrapping problem that arises when replacing traditional username and password with passkeys. This mode displays a credential selection UI only when the user's authenticator has a credential registered with the website or app. This credential is then shown alongside autofilled passwords, meaning websites can make a WebAuthn call while displaying a regular password prompt without running the risk of showing a modal dialog error in the event the device lacks appropriate credentials.

2. Boost the UX for Passkey Transition#

For passkey transition, the concept called Conditional UI is introduced to optimize the user experience for everyone. Non- passkey logins must still be possible as not everyone will immediately switch to passkeys. However, Conditional UI avoids an extra passkey button. It lets your browser display all available passkeys in an auto-fill dropdown that opens directly under the username field of a login form. If no passkey is available, the user needs to type in the email address and password (as it is now). If a passkey is available, it can be selected from the dropdown and the passkey authentication flow via Face ID or fingerprint starts. Basically, passkeys can be "hidden" behind the username field. The application will not be able to distinguish between the user not having a passkey or choosing not to reveal it.

To aid in the transition from passwords to passkeys, Conditional UI integrates with password-based authentication and leverages user familiarity with the UX. Applications can employ passkeys opportunistically without the fear of generating a poor customer experience if there is not an already registered passkey available.

Subscribe to our Passkeys Substack for the latest news.

Corbado's solution implements Conditional UI and offers your users their preferred login method. Start your passkeys journey now with Corbado to quickly obtain the benefits of passkeys and Conditional UI without thinking of complex integration or device issues. Integratewithout any risks in parallel to your existing authentication solution and transitiony our users smartly into the passkey era.

Frequently Asked Questions#

What problem does Conditional UI solve during a passkey rollout?#

Conditional UI solves the bootstrapping problem of replacing passwords with passkeys. It only surfaces the passkey selector when a credential actually exists on the device, so users without passkeys see a normal password prompt and never encounter a confusing modal error.

When a user focuses the username field, the browser opens an autofill dropdown listing any available passkeys alongside saved passwords. If no passkey is registered, the user simply types their email and password as normal, with no visible disruption to the existing flow.

Yes. Conditional UI integrates with password-based authentication in parallel, meaning your current login flow remains intact. Passkeys are offered opportunistically and the application cannot tell whether a user has no passkey or simply chose not to use one, so there is no risk of degrading the experience for existing users.