Describe your idea for an enhancement:
In VoidAuth’s login card and passkey dialog(app-passkey-dialog), platform-aware wording is used for “passkey”(e.g. Face ID)
But this can be confusing. Just because a user has an apple device doesn’t mean they use Face ID / Touch ID. They might use a hardware key like a yubikey or they might save the passkey in bitwarden without using biometrics.
In the FIDO Alliance docs, it says to “Associate the unfamiliar (passkeys) with the familiar.” and to “Pair passkeys language with wording they know.”. I think what this means is to use the generic wording(=passkey) and add extra wording alongside it, not replace the word “passkey”.
Also when a user creates or uses a passkey, the OS dialog already shows the specific auth method. So i think when a passkey system is used, VoidAuth doesn't need to change the word "passkey".
UX flow I'm envisioning:
in login page with use passkey button
“passkey” button(voidauth) → signing passkey(os) → done
in login page with use ID and PW
ID and PW login(voidauth) → “enable passkey” dialog(I want an option to always disable this dialog, but that’s off track!)
in register passkey button e.g.
button(voidauth) + explaining passkey message(optional, dialog or link to "what is a passkey" docs... etc.) → generating passkey(os) → passkey created!(dialog title, currently "passkey name") set a name for the new passkey? + input(voidauth)
(reference https://www.passkeycentral.org/design-guidelines/principles#2-use-clear-handshake-messages-before-and-after-os-dialogs)
Describe alternatives you've considered:
Additional context:
Describe your idea for an enhancement:
In VoidAuth’s login card and passkey dialog(app-passkey-dialog), platform-aware wording is used for “passkey”(e.g. Face ID)
But this can be confusing. Just because a user has an apple device doesn’t mean they use Face ID / Touch ID. They might use a hardware key like a yubikey or they might save the passkey in bitwarden without using biometrics.
In the FIDO Alliance docs, it says to “Associate the unfamiliar (passkeys) with the familiar.” and to “Pair passkeys language with wording they know.”. I think what this means is to use the generic wording(=passkey) and add extra wording alongside it, not replace the word “passkey”.
Also when a user creates or uses a passkey, the OS dialog already shows the specific auth method. So i think when a passkey system is used, VoidAuth doesn't need to change the word "passkey".
UX flow I'm envisioning:
in login page with use passkey button
“passkey” button(voidauth) → signing passkey(os) → done
in login page with use ID and PW
ID and PW login(voidauth) → “enable passkey” dialog(I want an option to always disable this dialog, but that’s off track!)
in register passkey button e.g.
button(voidauth) + explaining passkey message(optional, dialog or link to "what is a passkey" docs... etc.) → generating passkey(os) → passkey created!(dialog title, currently "passkey name") set a name for the new passkey? + input(voidauth)
(reference https://www.passkeycentral.org/design-guidelines/principles#2-use-clear-handshake-messages-before-and-after-os-dialogs)
Describe alternatives you've considered:
Additional context: