You can use any passkey provider app. I work at Bitwarden and we’re building mobile passkeys for android right now. We can do the e2e sync, but if you want you can always self host Bitwarden server and just use our clients app.
With discoverable credentials (which Passkeys by definition are), i.e. the flows where you don't even enter a username and the website learns it from the selected passkey, I don't think there's a way around a key selection process, but the UI can definitely be improved to distinguish the two.
Maybe something like "website XYZ is trying to verify your account 'username' – is that ok?" vs. "website XYZ wants to authenticate you – which passkey do you want to present to them (if any)"?
Patiently waiting for passkey support on Bitwarden iOS to replace all my passwords everywhere.
Do you guys have any rough idea how far away you are from launch? Is it weeks? Months? Quarters?
I'm eager to give it a try.
Unfortunately that API doesn't seem to be wired to anything in the app yet, so selecting it inevitably fails.