Mobile App Authentication: Passkeys or Passwords?

Compare passkeys and passwords for mobile app authentication. Plan recovery, platform support and security tests before release.

9 min read
A man and a woman talking at a cafe table

Mobile app authentication is not only a login screen. It is a decision about how people register, sign in on another device, recover a lost account and authorize sensitive actions. Passkeys can remove a reusable password from the sign-in exchange, but they do not remove the need for sound server-side checks or a safe recovery route. Australian product owners choosing between passkeys and passwords should evaluate their audience, existing accounts and supported devices before choosing a primary path.

Key Takeaways

  • Passkeys use public-key credentials; the app's server stores a public key rather than the account's reusable password secret.
  • A passkey does not fix weak account recovery, authorization or compromised sessions.
  • Keep a supported fallback during migration, but test that it does not silently weaken a high-risk action.
  • Verify registration, sign-in, device change, recovery and credential removal on each supported platform.

Choose for the account journey, not the sign-in screen

Start with the account model. Are users signing in to an existing website and app, registering for the first time, using employer-managed devices or switching between personal devices? Are there shared devices or users who cannot rely on a particular credential manager? List the actions that need a fresh identity check, such as changing a payout destination or adding another credential. A fast first login is not enough if account recovery later creates an easier path for takeover.

Passkeys are discoverable public-key credentials bound to a relying party's domain. Apple's implementation guidance describes a device creating a public-private key pair and sharing the public key with the server. Google's developer guide describes server challenges, registration and assertion verification, and recommends retaining existing sign-in methods while transitioning users for compatibility. A person may still use device biometrics or a PIN to release the credential; that local device check is not the app storing their biometric template.

Passwords remain familiar and can be appropriate as a transitional or fallback route. They require a secure verifier, credential reset, rate limits and additional protection where risk demands it. For a new product, the decision may be to offer passkeys first with a carefully designed alternative; for an established product, migration of existing accounts and support capacity will drive the sequence. Do not call an authentication choice a certification or a guarantee.

Compare the trade-offs explicitly

  • Sign-in secret - Private key stays with authenticator; server verifies assertion.; User enters reusable secret; server verifies it safely.
  • Platform work - Domain association, credential APIs, server verification.; Autofill, reset, abuse controls and optional MFA.
  • Lost device - Check sync, second credential and recovery policy.; Check reset identity proof and MFA continuity.
  • Main failure risk - Weak fallback or incorrect server binding.; Reused, phished or stolen passwords.

On iOS, passkey registration requires the correct associated domain and its web credentials relationship. On Android, Credential Manager supports passkeys and the app must be associated with the relying-party domain through the platform's association mechanism. A domain mismatch is an implementation failure, not a prompt to fall back silently to an unreviewed login flow. Test the app and website together if they share accounts.

Protect the full lifecycle

Use a maintained server-side WebAuthn implementation rather than writing challenge and signature verification from scratch. The OWASP passkey security guidance calls for validating ceremony fields on the server, binding registration to the intended account, requiring recent authentication before credential changes and treating recovery with the same care as login. A correct cryptographic ceremony does not stop an attacker who already controls an active session from adding their own credential unless the change flow is protected.

Allow people to view and remove registered credentials through a secure account-management path. Consider a second credential before the first device is lost, but do not force one specific vendor or device ecosystem unless the audience supports it. If a passkey is unavailable, explain the alternative openly. If an account is marked for a higher-assurance workflow, a failed passkey ceremony must not automatically downgrade to a weaker method for a sensitive action.

Passwords, where retained, should work with platform autofill and account recovery without exposing whether a particular email address exists in public-facing errors. Additional checks for unusual sign-ins and high-risk changes should be decided by the service's threat model. The Australian Cyber Security Centre describes passkeys as an alternative to passwords, but that public guidance is not a substitute for application-specific design and testing.

Check authorization and sessions separately

OWASP's mobile authentication controls distinguish secure authentication protocols, local authentication and extra checks for sensitive operations. Server endpoints must still verify authorization for each resource. A biometric check in the app is not proof that a server request may access another account's record. Test signed-out requests, expired sessions and account switches.

Set clear session expiry and revocation rules. After logout, a shared device should not expose another user's cached content or retain an active session through a deep link. When an account is recovered or a credential removed, decide which existing sessions should be invalidated. Log registration, recovery and administrative credential changes with appropriate access limits and without storing secrets in ordinary logs.

For organisations using assurance frameworks, AICPA's Trust Services Criteria address categories including security, availability, processing integrity, confidentiality and privacy. They are criteria for examining controls, not a ready-made passkey configuration or evidence that a product has passed a SOC 2 examination. The AICPA has published a proposed criteria update, so confirm the applicable version for any actual engagement. Neither selecting passkeys nor following an OWASP checklist implies certification.

Define a testable release gate

Test clean registration, existing-account migration, sign-in after reinstall, cross-device sign-in, cancellation, wrong domain, expired challenge, replayed assertion, credential removal and recovery after device loss. Test on the supported iOS and Android versions, including the credential providers users are likely to bring. Include users who do not have a passkey available and users who must continue on a supported alternative route.

A measurable acceptance gate is that every registration and sign-in scenario in the test matrix reaches the expected account or a clear failure state, no replayed or wrong-domain assertion is accepted, and every sensitive account change requires the specified fresh check. The server must reject requests for another account's records even when the app has a valid local session. Review recovery cases with security and support before release, then pilot the flow and monitor successful sign-ins, fallbacks, recovery requests and account-lockout reports without logging credential material.

The enterprise mobile architecture article discusses broader app structure, while the mobile backend article covers service choices. Neither replaces this identity lifecycle review. A team considering mobile application development should bring its account map, supported device list and recovery requirements to the scoping discussion.

Related Resources

Common Questions About Mobile App Authentication

1. Are passkeys safer than passwords?

Passkeys remove a reusable account password from the sign-in exchange and can resist phishing when domain binding and server verification are correct. They do not protect against weak recovery, compromised sessions or missing authorization checks.

2. Can an existing app add passkeys without removing passwords?

Yes. A gradual migration can keep a supported password route while people register passkeys. Review whether that alternative permits a weaker route to sensitive actions.

3. What happens if someone loses a device with a passkey?

Recovery depends on the credential provider, other registered credentials and the service's account recovery policy. Plan and test the path before launch rather than assuming every key is available on another device.

4. Does biometric sign-in replace server authorization?

No. Local device verification helps release a credential or open an app. The service still needs to validate the session and authorize each sensitive resource and operation.

Test Recovery Before Choosing a Default

Map account creation, returning sign-in, second-device access and lost-device recovery on one page. Decide where passkeys are the primary route and what alternative is acceptable for each audience. Validate server checks and the full failure matrix before introducing the flow to everyone. The safest-looking sign-in screen is only as strong as the account path around it.

Ready to build what is next?

Talk to our Melbourne engineering team about modernising your systems or shipping your next product.