Prompt
How do I support passwordless authentication on iPhone, Android, and desktop?
Latest observation
Oct 28, 2026
OpenAI APIWeb search: off
To support passwordless authentication across iPhone, Android, and desktop, the most practical modern approach is to use Passkeys.
What to use
1) Passkeys as the primary passwordless method
Passkeys are based on WebAuthn / FIDO2 and work across:
- iPhone/iPad: via iCloud Keychain
- Android: via Google Password Manager / Android Credential Manager
- Desktop: via platform authenticators or synced passkeys in browsers/OS password managers
Users can sign in with:
- Face ID / Touch ID / device PIN
- A synced passkey on another device
- In some cases, a security key
Recommended architecture
Support these flows
-
Register passkey
- User signs up or upgrades account
- Create a public/private key pair on the device
- Store the public key on your server
- Private key stays on the user’s device / synced credential store
-
Login with passkey
- Server sends a challenge
- Device signs it with the private key
- Server verifies the signature with the stored public key
-
Fallback / account recovery
- Offer backup methods in case the user loses device access:
- Email magic link
- Recovery codes
- Support-assisted recovery
- Optional password fallback if needed
- Offer backup methods in case the user loses device access:
Platform support details
iPhone
- Use Passkeys with WebAuthn
- In native iOS apps, use:
- AuthenticationServices
ASAuthorizationPlatformPublicKeyCredentialProvider
Android
- Use Credential Manager API
- Under the hood, this supports passkeys and federated sign-in
- Older approaches used Google Play Services FIDO2 API, but Credential Manager is preferred
Desktop
- If you have a web app, use WebAuthn in the browser
- For native desktop apps:
- Use a WebAuthn-compatible library
- Or embed a browser-based auth flow
- Supported in modern browsers on macOS, Windows, Linux, and ChromeOS
Best practice UX
- Offer passkey first
- Show “Sign in with passkey” prominently
- Let users create a passkey after password login if they already have an account
- Make fallback methods obvious but secondary
- Support device-bound and synced passkeys where available
What not to rely on
- SMS OTP as your main passwordless method: less secure, vulnerable to SIM swap
- Email OTP alone: better than passwords in some cases, but weaker than passkeys
- Proprietary device-specific login only: poor cross-platform experience
Implementation stack
If you’re building a web-backed system:
- Frontend: WebAuthn / passkey UI
- Backend: challenge generation, signature verification, credential storage
- Libraries:
- Node.js:
@simplewebauthn/server,@simplewebauthn/browser - Java: Yubico WebAuthn Server
- Python:
fido2 - Go:
duo-labs/webauthnor similar
- Node.js:
Practical recommendation
If you want one unified solution for all platforms:
- Use passkeys everywhere
- Support WebAuthn on web
- Use native passkey APIs on iOS and Android apps
- Provide a recovery path for lost-device scenarios
If you want, I can also give you:
- a high-level system design,
- sample backend API endpoints, or
- code examples for iOS, Android, and web.