[ghancock]

Update: I decided to go back and look at the settings pages for the two that worked.

Kayak shows a "Set up passkey" button with no indication that I already have one or any apparent way to revoke the existing one. Very bad.

Shop Pay does clearly show what passkeys exist, and allows revocation and addition. However, when I try to add one on Chrome on macOS, it only lets me set up a Chrome passkey. (These don't sync between devices. It should have let me set up whatever kind I wanted.) Also, the list just indicates passkeys by what browser type last used them, like "Chrome on macOS." So according to the list I have two passkeys that are just described as "Chrome on macOS" and they are indistinguishable.

I can't imagine recommending anyone try this unless they are consciously an early adopter.

[TheNewsIsHere]

Your points are all excellent examples of how far Passkeys have to go before they’re useful and usable for the masses.

They are cross-platform, but I’ve noticed that the platform makers want so strongly to keep you within their various gardens, that using them across ecosystems isn’t very intuitive or obvious unless you experiment or already know. That’s not a great way to foster mass adoption.

I’m using them everywhere I can and that make sense, but I’m tracking their use very closely in my password manager.