> Even though Apple (and likely a couple more) will provide their proprietary passwordless system with cloud sync, a lot of people don't want to rely on an iCloud account to be your backup in case you lose your phone.
This is the big one for me. The user story for logging in to a site on Windows with an iOS passkey is to scan a QR code with your phone, which sounds obnoxious.
I'd rather just have 1Password be the private key repository and those keys will sync to Mac/Windows/Phones through it instead of them being locked into iCloud Keychain, and it can handle logins just like normal.
That's a once type thing, the website is supposed to prompt you after that QR login whether you'd like to enroll your local authenticator (Chrome, Edge, Firefox,etc) after you login so you don't need to keep using the QR code.
The concept is that many people will frequently have multiple passkeys, thus not be 'locked in' to any one sync ecosystem.
> When signing in on a different computer, either the credential will already be locally present (if the computer is using the same sync fabric as the phone) and suggested by autocomplete, or else the user’s phone can be used to transmit the assertion to the computer. In the latter case, the service may invite the user to enroll a local platform authenticator for easier sign-in in the future. (Now the newly registered credential may be part of a different sync fabric, and thus enable local sign-in on other devices.)
It’s alright but it requires dismissing Windows Hello/FIDO2 every time and relies on establishing a BLE connection every time. (There’s no lasting BLE connection right now) So it’s also currently unusable on my desktop due to lack of Bluetooth.
I’d rather Windows Hello maintain a BLE connection itself and implement this (or the password manager suggestion).
Yeah that's why I think pw managers will be central to this story. Apple will try though, and they might have an edge and push the initial adoption, but eventually they'll come around. Their hubris usually calms down when their lock-in plans go further than they can handle.
I like Bitwarden more personally, but if the important aspects are standardized it shouldn't really make a difference.
Indeed, and Apple's pw manager is, as is typical, just a baseline implementation. I really need a full featured one so I can fix misfires (e.g. sign up on web, but the associated app doesn't set its domain properly), look for duplicates, get the info out for sites that can't auto entry (grr, js validation character-by-character) etc.
The calendar is another good example: adequate for many people, but trivially supplanted by a third party app (I use busycal) that apple treats as first class.
This is the big one for me. The user story for logging in to a site on Windows with an iOS passkey is to scan a QR code with your phone, which sounds obnoxious.
I'd rather just have 1Password be the private key repository and those keys will sync to Mac/Windows/Phones through it instead of them being locked into iCloud Keychain, and it can handle logins just like normal.