Acceptance Criteria

Designs

Scenarios

Edge Case

Commenting with hm://z6MkgisVMELvqnsCo3dYmtVpy8PiqPGMVwfAyBWFn84vebq4/:profile?v=bafy2bzacebcdqgkczlb6f6y4pfhegwdd27tomlrxwxmyai6kyr4mk2i5rxbks&l the proposal is to only show the password option if Passkey fails.
re we aligned on this hm://z6MkrbYsRzKb1VABdvhsDSAk6JK8fAszKsyHhcaZigYeWCou/:profile?v=bafy2bzacecoevvu2ebpntbrhm552uqp3ag5vrxvukpk7a4vvfmhazkk7smu5y&l , or should we still offer users a fallback option upfront if they're not comfortable with Passkey?

If we commit to Passkey as the only option, we need three things in place:

A rock-solid Passkey flow — this is the critical one. It needs to handle all edge cases smoothly. If a user gets stuck here, we risk losing them for good — they won't come back to the tool.

Build user confidence — reassurance copy that guides users through each step and makes the process feel clear and low-risk.

A short, clear "What is Passkey?" page — so users understand what they're being asked to do before they do it.