FIDO Alliance
Chair, UX Working Group

FIDO Alliance

Passkeys needed to make sense across products designed by different companies. As Chair of FIDO's UX Working Group, I organize specialist workstreams and help turn their contributions into shared UX guidance.

The aim is practical: give teams patterns, explanations, and platform resources they can use when designing their own passkey experiences.

FIDO Alliance

The shared problem

Agree on the decisions, not identical screens

Companies bring different product requirements, terminology, and security policies. Shared guidance needed to address recurring UX questions without prescribing one interface for every service.

I focused the work on those questions: what a prompt needs to explain, when to offer creation, and what happens when a passkey is unavailable.

How I organized the work

Give specialists a defined contribution to own

I established specialist workstreams, guided the research agenda, and connected related efforts. For Passkey Central, visual-design contributors shaped the presentation; content and accessibility specialists owned their respective contributions to the published resource.

That work served different needs: design guidelines for people building the flows, and Passkey Central for teams planning and deploying passkeys. The Figma resources below add operating-system dialogs and prototypes contributed across the group, including the teams designing those platforms.

FIDO's public Figma profile showing passkey operating-system dialogs and prototype resources
FIDO's published Figma resources, including operating-system dialogs and prototypes. Shared work that product teams can inspect and adapt.

A recommendation teams can apply

Prefer autofill. Preserve another way in

FIDO's published research compared a dedicated link, buttons, and autofill. Autofill produced the strongest sign-in success in those tests. Some participants did not remember creating a passkey and did not look for a dedicated button.

The resulting guidance gives teams a concrete choice: offer autofill and retain another route when it is unavailable. It also describes contexts where a dedicated button can help. This is the group's research and recommendation; my role was setting direction and organizing contributions, not sole authorship of the pattern.

Published FIDO flow showing passkey autofill and an alternative sign-in route
Two routes to authenticated access. The passkey branch uses OS/browser autofill. The email branch preserves another sign-in method. Source: FIDO's published sign-in pattern.

The shared output

Take a pattern into the team's own product

The published guidance puts the recommendation, research rationale, example copy, and platform prototypes together. Teams can examine the flow and adapt the editable resources to their own requirements, rather than reconstructing every system dialog and decision from scratch.

Real-world identity

Make proving who you are easier to understand

I co-founded and co-lead the Digital Credentials UX subgroup within FIDO's UX Working Group, shaping UX direction for how people prove who they are online.

The distinction matters: signing in to an account is not the same as proving something about yourself, such as your age. FIDO's digital-credentials work addresses how those experiences can work together, with privacy and user control at the center.

Explore FIDO's digital-credentials work

Public record

Explore the work

Continue exploringGoogle Authenticator: renewing an essential product