For consumers: it's considered good form for these services to allow multiple webauthn devices tied to an account. So you keep a yubikey somewhere to get back in, on the off chance that you simultaneously lose access to your phone and your computer.
For corporate accounts: an admin provisions a new device for you and gives it to you.
Since this technology is in a large part a response to consumers utilising passwords badly I don't see this as a valid assumption.
Let's ignore that some consumers won't have their own devices and therefore won't be able to use any service with this in place. I know people who do online banking at the library because they have no choice.
My current set up with my password manager offers way more flexibility. And the only downside it that the password gets transmitted, encrypted, but it leaves my device.
Hopefully keepass[xc] role out support too.
I wouldn't put my password vault in the cloud and neither will I put any passkeys either.
https://news.ycombinator.com/item?id=33948929
Another option is to use hardware keys running open source user-controlled software, like the Tomu:
If I sign up for a service I can never sign into it unless I have that device with me. For some ultra secure things that's a good thing, for day to day shopping, etc, it's so inflexible as to be useless.
Again what happens when the device breaks or is lost or stolen?
How do I migrate my credentials from Mac to android to windows to Linux to iOS?
I'll be sticking with my password manager until I'm unable to use it.