Scoring visualizer

No linked atoms.

Atom	Weight
Passkeys are unlocked using device biometric methods such as Face ID or fingerprint scanning, often letting users sign in without remembering a password, especially on synced devices in the same ecosystem, similar to Apple Pay and phone unlocking.	0.338ω=0.88
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	0.267ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	0.251ω=0.96
A memorized password can be entered on any phone or laptop with a keyboard, allowing access even if the user's primary device is lost or stolen.	-0.233
When a website does not support passkeys, browsers can display a message such as "no passkey for this website".	-0.218ω=0.70
Passkeys are stored on a device, hardware key, or synced vault such as an operating system, browser, or third-party manager rather than in a user's memory; many users do not know where their passkey resides or lack backup access, so losing that device or vault without backup can lock them out of accounts that rely on that passkey.	-0.204ω=0.75
The WebAuthn protocol has undergone multiple iterations and is considered production-ready.	0.187ω=0.91
Password-manager applications can generate and store random long passwords and synchronize them across devices, but often require users to copy-paste credentials and can suffer from field-recognition failures and mismatched or differing URLs.	0.114ω=0.55
Passkeys are being adopted by all companies.	0.028ω=0.10

Atom	Weight
Passkeys are unlocked using device biometric methods such as Face ID or fingerprint scanning, often letting users sign in without remembering a password, especially on synced devices in the same ecosystem, similar to Apple Pay and phone unlocking.	0.541ω=0.88
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	0.464ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	0.448ω=0.96
When a website does not support passkeys, browsers can display a message such as "no passkey for this website".	-0.369ω=0.70
A memorized password can be entered on any phone or laptop with a keyboard, allowing access even if the user's primary device is lost or stolen.	-0.350
The WebAuthn protocol has undergone multiple iterations and is considered production-ready.	0.334ω=0.91
Authenticator apps generate a time-based one-time password (TOTP) that the user must manually enter or paste during authentication.	-0.317
Passkeys are stored on a device, hardware key, or synced vault such as an operating system, browser, or third-party manager rather than in a user's memory; many users do not know where their passkey resides or lack backup access, so losing that device or vault without backup can lock them out of accounts that rely on that passkey.	-0.308ω=0.75
Chrome’s password manager can autofill saved passwords and stores them in the user’s profile.	-0.202ω=0.70
Password-manager applications can generate and store random long passwords and synchronize them across devices, but often require users to copy-paste credentials and can suffer from field-recognition failures and mismatched or differing URLs.	0.198ω=0.55
After setup, conditional login flows can let a passkey serve as the routine login method, replacing separate OTP or magic-link steps while using on-device user verification.	0.159ω=0.70
Support for passkeys varies across browsers, PWAs, devices, websites, and platforms, producing inconsistent experiences and making migration between ecosystems or passkey managers sometimes clumsy or impossible, especially in mixed-device setups.	-0.145ω=0.70
Many sites that offer passkeys still retain a password or SMS code as a backup authentication or recovery method.	-0.096ω=0.40
Passkeys are being adopted by all companies.	0.044ω=0.10

Atom	Weight
Passkeys are unlocked using device biometric methods such as Face ID or fingerprint scanning, often letting users sign in without remembering a password, especially on synced devices in the same ecosystem, similar to Apple Pay and phone unlocking.	0.788ω=0.88
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	0.677ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	0.661ω=0.96
When a website does not support passkeys, browsers can display a message such as "no passkey for this website".	-0.541ω=0.70
The WebAuthn protocol has undergone multiple iterations and is considered production-ready.	0.511ω=0.91
A memorized password can be entered on any phone or laptop with a keyboard, allowing access even if the user's primary device is lost or stolen.	-0.500
Authenticator apps generate a time-based one-time password (TOTP) that the user must manually enter or paste during authentication.	-0.472
Passkeys are stored on a device, hardware key, or synced vault such as an operating system, browser, or third-party manager rather than in a user's memory; many users do not know where their passkey resides or lack backup access, so losing that device or vault without backup can lock them out of accounts that rely on that passkey.	-0.454ω=0.75
Chrome’s password manager can autofill saved passwords and stores them in the user’s profile.	-0.307ω=0.70
Password-manager applications can generate and store random long passwords and synchronize them across devices, but often require users to copy-paste credentials and can suffer from field-recognition failures and mismatched or differing URLs.	0.277ω=0.55
After setup, conditional login flows can let a passkey serve as the routine login method, replacing separate OTP or magic-link steps while using on-device user verification.	0.257ω=0.70
Support for passkeys varies across browsers, PWAs, devices, websites, and platforms, producing inconsistent experiences and making migration between ecosystems or passkey managers sometimes clumsy or impossible, especially in mixed-device setups.	-0.231ω=0.70
Native apps distributed via app stores can implement passkey authentication with full control, bypassing browser integration constraints.	0.175ω=0.85
Many reputable websites typically offer either a passkey login flow or a password-plus-two-factor-authentication login flow; in the latter case, intercepting the password alone is insufficient without the second-factor device.	0.171ω=0.70
Passwords are the de facto standard authentication method today, and user-chosen memorized passwords are frequently weak, short, or reused across multiple sites, making password-based access more vulnerable to compromise than passkeys.	0.159ω=0.70
Authenticator apps for two-factor authentication are familiar to many users, but they can create access problems if the device storing the secret is lost before the secret is synchronized elsewhere.	-0.154ω=0.70
Many sites that offer passkeys still retain a password or SMS code as a backup authentication or recovery method.	-0.153ω=0.40
Passkeys are being adopted by all companies.	0.062ω=0.10

No linked atoms.

Atom	Weight
Authenticator apps generate a time-based one-time password (TOTP) that the user must manually enter or paste during authentication.	-0.294
After setup, conditional login flows can let a passkey serve as the routine login method, replacing separate OTP or magic-link steps while using on-device user verification.	0.285ω=0.70
Passkeys are being adopted by all companies.	0.029ω=0.10

Atom	Weight
Authenticator apps generate a time-based one-time password (TOTP) that the user must manually enter or paste during authentication.	-0.515
After setup, conditional login flows can let a passkey serve as the routine login method, replacing separate OTP or magic-link steps while using on-device user verification.	0.462ω=0.70
SMS codes can be used as a login method.	-0.278
Passkeys are unlocked using device biometric methods such as Face ID or fingerprint scanning, often letting users sign in without remembering a password, especially on synced devices in the same ecosystem, similar to Apple Pay and phone unlocking.	0.270ω=0.88
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	0.237ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	0.237ω=0.96
Authenticator apps for two-factor authentication are familiar to many users, but they can create access problems if the device storing the secret is lost before the secret is synchronized elsewhere.	0.228ω=0.70
According to the author, cryptocurrency exchanges known to them have moved away from multi-channel code delivery toward authenticator-app-based two-factor authentication, and multi-channel email/SMS code delivery is viewed as unsafe.	-0.113ω=0.40
Many sites that offer passkeys still retain a password or SMS code as a backup authentication or recovery method.	-0.089ω=0.40
Passkeys are being adopted by all companies.	0.049ω=0.10

Atom	Weight
Authenticator apps generate a time-based one-time password (TOTP) that the user must manually enter or paste during authentication.	-0.797
After setup, conditional login flows can let a passkey serve as the routine login method, replacing separate OTP or magic-link steps while using on-device user verification.	0.651ω=0.70
SMS codes can be used as a login method.	-0.455
Passkeys are unlocked using device biometric methods such as Face ID or fingerprint scanning, often letting users sign in without remembering a password, especially on synced devices in the same ecosystem, similar to Apple Pay and phone unlocking.	0.371ω=0.88
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	0.355ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	0.355ω=0.96
Authenticator apps for two-factor authentication are familiar to many users, but they can create access problems if the device storing the secret is lost before the secret is synchronized elsewhere.	0.321ω=0.70
The WebAuthn protocol has undergone multiple iterations and is considered production-ready.	0.218ω=0.91
European banking regulations such as PSD2 require multi-factor authentication for online banking, making password-only logins non-compliant in that context.	-0.211
Many reputable websites typically offer either a passkey login flow or a password-plus-two-factor-authentication login flow; in the latter case, intercepting the password alone is insufficient without the second-factor device.	-0.183ω=0.70
According to the author, cryptocurrency exchanges known to them have moved away from multi-channel code delivery toward authenticator-app-based two-factor authentication, and multi-channel email/SMS code delivery is viewed as unsafe.	-0.180ω=0.40
Many sites that offer passkeys still retain a password or SMS code as a backup authentication or recovery method.	-0.136ω=0.40
Passkeys are being adopted by all companies.	0.072ω=0.10

Null: When products make passkeys the default, this would have no relevant impact on resistance to account compromise relative to password- and magic-link-based access for reasons other than many products still keeping fallback or recovery routes that attackers can phish or abuse with roughly the same practical success as the pre-passkey login path, or the relevant non-passkey baseline already relying on password-manager-generated unique passwords combined with separate multi-factor or hardware-key protection.

d: 0.00

No linked atoms.

Atom	Weight
Passkeys are marketed as ending phishing.	0.277
Passkeys are scoped to specific domains, providing phishing resistance so a lookalike site cannot obtain a reusable credential even if a user proceeds with the login flow.	0.232ω=0.70
Passwords are the de facto standard authentication method today, and user-chosen memorized passwords are frequently weak, short, or reused across multiple sites, making password-based access more vulnerable to compromise than passkeys.	0.206ω=0.70
After setup, conditional login flows can let a passkey serve as the routine login method, replacing separate OTP or magic-link steps while using on-device user verification.	0.206ω=0.70
The WebAuthn protocol has undergone multiple iterations and is considered production-ready.	0.203ω=0.91
Hardware security keys such as YubiKey provide stronger authentication security than software-based second factors like Google Authenticator or SMS codes.	0.175ω=0.70
Magic-link authentication methods have known security risks, including susceptibility to phishing and link interception.	0.164ω=0.55
Many sites that offer passkeys still retain a password or SMS code as a backup authentication or recovery method.	-0.098ω=0.40
Passkeys are being adopted by all companies.	0.030ω=0.10

Atom	Weight
Passkeys are marketed as ending phishing.	0.440
Passkeys are scoped to specific domains, providing phishing resistance so a lookalike site cannot obtain a reusable credential even if a user proceeds with the login flow.	0.437ω=0.70
After setup, conditional login flows can let a passkey serve as the routine login method, replacing separate OTP or magic-link steps while using on-device user verification.	0.396ω=0.70
The WebAuthn protocol has undergone multiple iterations and is considered production-ready.	0.382ω=0.91
Passwords are the de facto standard authentication method today, and user-chosen memorized passwords are frequently weak, short, or reused across multiple sites, making password-based access more vulnerable to compromise than passkeys.	0.372ω=0.70
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	0.319ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	0.319ω=0.96
Magic-link authentication methods have known security risks, including susceptibility to phishing and link interception.	0.300ω=0.55
Hardware security keys such as YubiKey provide stronger authentication security than software-based second factors like Google Authenticator or SMS codes.	0.298ω=0.70
European banking regulations such as PSD2 require multi-factor authentication for online banking, making password-only logins non-compliant in that context.	0.246
Authenticator apps generate a time-based one-time password (TOTP) that the user must manually enter or paste during authentication.	-0.206
Many sites that offer passkeys still retain a password or SMS code as a backup authentication or recovery method.	-0.172ω=0.40
Chrome’s password manager can autofill saved passwords and stores them in the user’s profile.	-0.148ω=0.70
Passkeys are being adopted by all companies.	0.052ω=0.10

Atom	Weight
Passkeys are scoped to specific domains, providing phishing resistance so a lookalike site cannot obtain a reusable credential even if a user proceeds with the login flow.	0.589ω=0.70
Passkeys are marketed as ending phishing.	0.587
The WebAuthn protocol has undergone multiple iterations and is considered production-ready.	0.549ω=0.91
After setup, conditional login flows can let a passkey serve as the routine login method, replacing separate OTP or magic-link steps while using on-device user verification.	0.541ω=0.70
Passwords are the de facto standard authentication method today, and user-chosen memorized passwords are frequently weak, short, or reused across multiple sites, making password-based access more vulnerable to compromise than passkeys.	0.515ω=0.70
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	0.480ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	0.480ω=0.96
Magic-link authentication methods have known security risks, including susceptibility to phishing and link interception.	0.424ω=0.55
Hardware security keys such as YubiKey provide stronger authentication security than software-based second factors like Google Authenticator or SMS codes.	0.397ω=0.70
European banking regulations such as PSD2 require multi-factor authentication for online banking, making password-only logins non-compliant in that context.	0.317
Authenticator apps generate a time-based one-time password (TOTP) that the user must manually enter or paste during authentication.	-0.300
Passkeys are unlocked using device biometric methods such as Face ID or fingerprint scanning, often letting users sign in without remembering a password, especially on synced devices in the same ecosystem, similar to Apple Pay and phone unlocking.	0.296ω=0.88
SMS codes can be used as a login method.	-0.250
Many sites that offer passkeys still retain a password or SMS code as a backup authentication or recovery method.	-0.250ω=0.40
Chrome’s password manager can autofill saved passwords and stores them in the user’s profile.	-0.237ω=0.70
Platforms can offer account recovery by letting users log in with email and, after manual verification, add a new 2FA method.	-0.210ω=0.70
When a website does not support passkeys, browsers can display a message such as "no passkey for this website".	-0.148ω=0.70
According to the author, cryptocurrency exchanges known to them have moved away from multi-channel code delivery toward authenticator-app-based two-factor authentication, and multi-channel email/SMS code delivery is viewed as unsafe.	0.131ω=0.40
Passkeys are being adopted by all companies.	0.074ω=0.10

Atom	Weight
A memorized password can be entered on any phone or laptop with a keyboard, allowing access even if the user's primary device is lost or stolen.	0.451
Passkeys are scoped to specific domains, providing phishing resistance so a lookalike site cannot obtain a reusable credential even if a user proceeds with the login flow.	-0.326ω=0.70
After setup, conditional login flows can let a passkey serve as the routine login method, replacing separate OTP or magic-link steps while using on-device user verification.	-0.322ω=0.70
Many sites that offer passkeys still retain a password or SMS code as a backup authentication or recovery method.	0.309ω=0.40
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	-0.267ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	-0.267ω=0.96
Passkeys are marketed as ending phishing.	-0.257
The WebAuthn protocol has undergone multiple iterations and is considered production-ready.	-0.249ω=0.91
Passkeys are stored on a device, hardware key, or synced vault such as an operating system, browser, or third-party manager rather than in a user's memory; many users do not know where their passkey resides or lack backup access, so losing that device or vault without backup can lock them out of accounts that rely on that passkey.	0.161ω=0.75
Support for passkeys varies across browsers, PWAs, devices, websites, and platforms, producing inconsistent experiences and making migration between ecosystems or passkey managers sometimes clumsy or impossible, especially in mixed-device setups.	0.157ω=0.70
Password-manager applications can generate and store random long passwords and synchronize them across devices, but often require users to copy-paste credentials and can suffer from field-recognition failures and mismatched or differing URLs.	0.121ω=0.55

Atom	Weight
European banking regulations such as PSD2 require multi-factor authentication for online banking, making password-only logins non-compliant in that context.	0.482
Passwords are the de facto standard authentication method today, and user-chosen memorized passwords are frequently weak, short, or reused across multiple sites, making password-based access more vulnerable to compromise than passkeys.	-0.319ω=0.70
Hardware security keys such as YubiKey provide stronger authentication security than software-based second factors like Google Authenticator or SMS codes.	0.286ω=0.70
After setup, conditional login flows can let a passkey serve as the routine login method, replacing separate OTP or magic-link steps while using on-device user verification.	-0.237ω=0.70
Password-manager applications can generate and store random long passwords and synchronize them across devices, but often require users to copy-paste credentials and can suffer from field-recognition failures and mismatched or differing URLs.	0.236ω=0.55
Passkeys are scoped to specific domains, providing phishing resistance so a lookalike site cannot obtain a reusable credential even if a user proceeds with the login flow.	-0.223ω=0.70

No linked atoms.

Atom	Weight
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	-0.315ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	-0.315ω=0.96
The WebAuthn protocol has undergone multiple iterations and is considered production-ready.	-0.253ω=0.91
Support for passkeys varies across browsers, PWAs, devices, websites, and platforms, producing inconsistent experiences and making migration between ecosystems or passkey managers sometimes clumsy or impossible, especially in mixed-device setups.	0.231ω=0.70
When a website does not support passkeys, browsers can display a message such as "no passkey for this website".	0.229ω=0.70
Native apps distributed via app stores can implement passkey authentication with full control, bypassing browser integration constraints.	-0.194ω=0.85
Passkeys are being adopted by all companies.	-0.037ω=0.10

Atom	Weight
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	-0.549ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	-0.549ω=0.96
The WebAuthn protocol has undergone multiple iterations and is considered production-ready.	-0.465ω=0.91
When a website does not support passkeys, browsers can display a message such as "no passkey for this website".	0.393ω=0.70
Support for passkeys varies across browsers, PWAs, devices, websites, and platforms, producing inconsistent experiences and making migration between ecosystems or passkey managers sometimes clumsy or impossible, especially in mixed-device setups.	0.383ω=0.70
Native apps distributed via app stores can implement passkey authentication with full control, bypassing browser integration constraints.	-0.345ω=0.85
Many reputable websites typically offer either a passkey login flow or a password-plus-two-factor-authentication login flow; in the latter case, intercepting the password alone is insufficient without the second-factor device.	-0.167ω=0.70
Passkeys are being adopted by all companies.	-0.060ω=0.10

Atom	Weight
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	-0.795ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	-0.795ω=0.96
The WebAuthn protocol has undergone multiple iterations and is considered production-ready.	-0.713ω=0.91
When a website does not support passkeys, browsers can display a message such as "no passkey for this website".	0.568ω=0.70
Support for passkeys varies across browsers, PWAs, devices, websites, and platforms, producing inconsistent experiences and making migration between ecosystems or passkey managers sometimes clumsy or impossible, especially in mixed-device setups.	0.559ω=0.70
Native apps distributed via app stores can implement passkey authentication with full control, bypassing browser integration constraints.	-0.515ω=0.85
Many reputable websites typically offer either a passkey login flow or a password-plus-two-factor-authentication login flow; in the latter case, intercepting the password alone is insufficient without the second-factor device.	-0.226ω=0.70
Passkeys are being adopted by all companies.	-0.088ω=0.10

Atom	Weight
Native apps distributed via app stores can implement passkey authentication with full control, bypassing browser integration constraints.	0.604ω=0.85
Support for passkeys varies across browsers, PWAs, devices, websites, and platforms, producing inconsistent experiences and making migration between ecosystems or passkey managers sometimes clumsy or impossible, especially in mixed-device setups.	-0.239ω=0.70

Atom	Weight
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	0.509ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	0.509ω=0.96
The WebAuthn protocol has undergone multiple iterations and is considered production-ready.	0.484ω=0.91
Support for passkeys varies across browsers, PWAs, devices, websites, and platforms, producing inconsistent experiences and making migration between ecosystems or passkey managers sometimes clumsy or impossible, especially in mixed-device setups.	-0.286ω=0.70
When a website does not support passkeys, browsers can display a message such as "no passkey for this website".	-0.148ω=0.70
Passkeys are being adopted by all companies.	0.023ω=0.10

Null: When products make passkeys the default, this would have no relevant impact on failures of access continuity for ordinary users after device loss, device replacement, or ecosystem changes for reasons other than products keeping workable recovery routes or requiring more than one registered passkey even while passkeys are the default routine sign-in method, or the relevant secure-access baseline already depending on device- or cloud-stored authenticators or password-manager profiles with similar loss and recovery failure modes.

d: 0.00

No linked atoms.

Atom	Weight
Passkeys are stored on a device, hardware key, or synced vault such as an operating system, browser, or third-party manager rather than in a user's memory; many users do not know where their passkey resides or lack backup access, so losing that device or vault without backup can lock them out of accounts that rely on that passkey.	0.413ω=0.75
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	-0.299ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	-0.299ω=0.96
Support for passkeys varies across browsers, PWAs, devices, websites, and platforms, producing inconsistent experiences and making migration between ecosystems or passkey managers sometimes clumsy or impossible, especially in mixed-device setups.	0.264ω=0.70
Authenticator apps for two-factor authentication are familiar to many users, but they can create access problems if the device storing the secret is lost before the secret is synchronized elsewhere.	0.159ω=0.70
Many sites that offer passkeys still retain a password or SMS code as a backup authentication or recovery method.	-0.098ω=0.40

Atom	Weight
Passkeys are stored on a device, hardware key, or synced vault such as an operating system, browser, or third-party manager rather than in a user's memory; many users do not know where their passkey resides or lack backup access, so losing that device or vault without backup can lock them out of accounts that rely on that passkey.	0.625ω=0.75
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	-0.464ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	-0.464ω=0.96
Support for passkeys varies across browsers, PWAs, devices, websites, and platforms, producing inconsistent experiences and making migration between ecosystems or passkey managers sometimes clumsy or impossible, especially in mixed-device setups.	0.439ω=0.70
Authenticator apps for two-factor authentication are familiar to many users, but they can create access problems if the device storing the secret is lost before the secret is synchronized elsewhere.	0.299ω=0.70
When a website does not support passkeys, browsers can display a message such as "no passkey for this website".	0.187ω=0.70
Many sites that offer passkeys still retain a password or SMS code as a backup authentication or recovery method.	-0.164ω=0.40

Atom	Weight
Passkeys are stored on a device, hardware key, or synced vault such as an operating system, browser, or third-party manager rather than in a user's memory; many users do not know where their passkey resides or lack backup access, so losing that device or vault without backup can lock them out of accounts that rely on that passkey.	0.946ω=0.75
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	-0.688ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	-0.688ω=0.96
Support for passkeys varies across browsers, PWAs, devices, websites, and platforms, producing inconsistent experiences and making migration between ecosystems or passkey managers sometimes clumsy or impossible, especially in mixed-device setups.	0.611ω=0.70
Authenticator apps for two-factor authentication are familiar to many users, but they can create access problems if the device storing the secret is lost before the secret is synchronized elsewhere.	0.428ω=0.70
When a website does not support passkeys, browsers can display a message such as "no passkey for this website".	0.261ω=0.70
Many sites that offer passkeys still retain a password or SMS code as a backup authentication or recovery method.	-0.249ω=0.40
A memorized password can be entered on any phone or laptop with a keyboard, allowing access even if the user's primary device is lost or stolen.	-0.239
Platforms can offer account recovery by letting users log in with email and, after manual verification, add a new 2FA method.	-0.183ω=0.70
Native apps distributed via app stores can implement passkey authentication with full control, bypassing browser integration constraints.	-0.179ω=0.85
Password-manager applications can generate and store random long passwords and synchronize them across devices, but often require users to copy-paste credentials and can suffer from field-recognition failures and mismatched or differing URLs.	-0.122ω=0.55

When products make passkeys the default, this would have no relevant impact on failures of access continuity for ordinary users after device loss, device replacement, or ecosystem changes because passkeys would be the default routine sign-in method rather than the only way into the account, and products could keep workable recovery routes such as email login followed by manual verification or require more than one registered passkey, so losing one device would not by itself end access even if passkeys would otherwise add lockout risk.

d: 0.00Σ +0.827

Atom	Weight
A memorized password can be entered on any phone or laptop with a keyboard, allowing access even if the user's primary device is lost or stolen.	0.567
Passkeys are stored on a device, hardware key, or synced vault such as an operating system, browser, or third-party manager rather than in a user's memory; many users do not know where their passkey resides or lack backup access, so losing that device or vault without backup can lock them out of accounts that rely on that passkey.	-0.527ω=0.75
Chrome integrates passkey support with its password manager, enabling passkeys to be synchronized across a user's devices.	0.366ω=0.96
Apple's ecosystem can sync passkeys across a user's devices in many cases.	0.366ω=0.96
Support for passkeys varies across browsers, PWAs, devices, websites, and platforms, producing inconsistent experiences and making migration between ecosystems or passkey managers sometimes clumsy or impossible, especially in mixed-device setups.	-0.363ω=0.70
Many reputable websites typically offer either a passkey login flow or a password-plus-two-factor-authentication login flow; in the latter case, intercepting the password alone is insufficient without the second-factor device.	0.215ω=0.70
Many sites that offer passkeys still retain a password or SMS code as a backup authentication or recovery method.	0.203ω=0.40
Authenticator apps for two-factor authentication are familiar to many users, but they can create access problems if the device storing the secret is lost before the secret is synchronized elsewhere.	-0.185ω=0.70
Password-manager applications can generate and store random long passwords and synchronize them across devices, but often require users to copy-paste credentials and can suffer from field-recognition failures and mismatched or differing URLs.	0.185ω=0.55

Atom	Weight
A memorized password can be entered on any phone or laptop with a keyboard, allowing access even if the user's primary device is lost or stolen.	0.289
Passkeys are stored on a device, hardware key, or synced vault such as an operating system, browser, or third-party manager rather than in a user's memory; many users do not know where their passkey resides or lack backup access, so losing that device or vault without backup can lock them out of accounts that rely on that passkey.	-0.236ω=0.75
Platforms can offer account recovery by letting users log in with email and, after manual verification, add a new 2FA method.	0.148ω=0.70
Authenticator apps for two-factor authentication are familiar to many users, but they can create access problems if the device storing the secret is lost before the secret is synchronized elsewhere.	0.141ω=0.70
Password-manager applications can generate and store random long passwords and synchronize them across devices, but often require users to copy-paste credentials and can suffer from field-recognition failures and mismatched or differing URLs.	0.122ω=0.55
Many sites that offer passkeys still retain a password or SMS code as a backup authentication or recovery method.	0.118ω=0.40

Are passkeys ready to become the default way users access digital products?

After comment MhxJq7 (step 11)

Increasing practical day-to-day sign-in usability for typical users when products make passkeys the default.

Increasing the extent to which default passkeys remove separate two-factor-authentication steps from routine access.

Increasing resistance to account compromise relative to password- and magic-link-based access when products make passkeys the default.

Increasing browser-, PWA-, and device-specific integration problems when products make passkeys the default.

Increasing failures of access continuity for ordinary users when products make passkeys the default. Here, access continuity means keeping or regaining account access after device loss, device replacement, or ecosystem changes.