> Passkeys are going to be a complete failure, because a) vendor lock-in

It's pretty easy to avoid vendor lock-in. Here's what I do when I decide to add passkeys for a site I use.

1. I press the "create a passkey" button on the site's security page (finding this is usually the most time consuming part).

2. My browser gives a dialog offering to save the passkey in 1Password. I let it do so.

3. I press the "create a passkey" button again.

4. I get the same save dialog. This time I pick the option on the dialog to save elsewhere.

5. That dialog goes away and I get a new dialog for saving the passkey in Apple's iCloud. I let it do so.

That all is just "click", "click", "click", "click", <touch fingerprint reader>.

The result is that I now have two passkeys for the site, handled by two different vendors.

> I can easily move a password around; it's just a string. As far as I understand it, major passkey implementations are basically non-portable

There's a spec being worked on for passkey export/import [1].

[1] https://blog.1password.com/fido-alliance-import-export-passk...