Orion currently supports passkeys, but it seems to be using its own implementation.
I hope this explanation would clear up some issues and allow a proper implementation of passkeys
safari
safari saves the passkey to iCloud Keychain, which is synced on all devices, authenticated via touch id.
but, it also provides an option ot using a nearby device (iphone, ipad, or android device) to use a camera to create the passkey
or, using an external security key.
then, when authenticating, it defaults to touch id, bu also provides other choices.
firefox
exact same UX and UI as Safari. this is what orion should have implemented.
chrome
chrome saves the passkey to exact same iCloud Keychain that Safari uses (you can see that fdsa1 which was created on Safari is suggested for autofill), which is synced on all devices, authenticated via touch id.
but, it also provides an option ot using a nearby device (iphone, ipad, or android device) to use a camera to create the passkey, or an external security key
the option "using your chrome profile" creates a local-only passkey. this is what orion is doing currently. the flow for this also looks like what orion currently offers, using the same touch-id popup that orion has
chrome likely has a slightly different flow than safari/firefox bc of its "using your chrome profile" option that safari and ff don't support (and isn't necessary)
orion
orion, on the other hand, only allows for touch id and security key, providing a very different popup.
it also uses a different touch id verification popup
also, when authenticating, it uses a different touch id popup, and doesnt offer other choices for authentication
