On 4 September 2025, Niharika Arora and Vinisha Athwani published Google’s recommended playbook for moving Android users from passwords to passkeys. The post is a developer-relations article, not a consumer newsroom splash, but it is an official announcement of how Google wants the ecosystem to behave. Passkeys are described as cryptographic credentials bound to device unlock, phishing-resistant because they use public-key cryptography rather than a shared secret. Credential Manager, a Jetpack API, is named as the unified interface for passkeys, passwords, and federated sign-in such as Sign in with Google. What Google announced is a set of product practices. Prompt passkey creation at account registration, immediately after a successful password or OTP sign-in, during account recovery, and after a password reset — the moment, the authors wrote, when users are most tired of passwords. Use Credential Manager’s bottom sheet so that passkeys, passwords, and federated options appear in one UI. Show passkey metadata in app settings. Educate in-product. Roll out progressively. Keep password fallback so that a user on a new device is not locked out. Those are instructions to app developers, not a schedule for deleting passwords from Gmail. The same post cites other companies’ outcomes as those companies described them to Google: X observed login rates improved 2x after adding passkeys; KAYAK observed 50% faster sign-up and sign-in; Zoho’s OneAuth Android app achieved 6x faster logins; Uber said more than 90% of passkey enrolments came from in-app prompts rather than organic discovery; Economic Times reported about 10% improvement in passkey-creation completion after it stopped prompting inside checkout. Those figures are attributed to the named firms via Google’s blog. They are not Google’s own measurement of Android as a whole and are not independently verified here. A companion developers.google.com page, last updated 19 May 2025 in the version loaded for this briefing, explains where passkeys actually live. Google Password Manager stores and syncs them on Android and Chrome, end-to-end encrypted. The first desktop passkey may require a Google Password Manager PIN. Android apps use Credential Manager from Android 9 (API 28) upward. On Android 14 or higher, users can choose a third-party passkey provider in system settings. Chrome on iOS can use Google Password Manager if the user enables Chrome as an autofill provider on iOS 17 or higher. Chrome on macOS can store passkeys in Google Password Manager or iCloud Keychain from macOS 13.5. Cross-device sign-in via QR code is supported so that a passkey on an iPhone can authenticate an Android app that has none stored locally. What has not been confirmed by these two pages is a date when Google Accounts stop accepting passwords, a mandate that every Play app must offer passkeys, or a claim that synced passkeys are immune to cloud-account takeover. Sync helps usability; it also means the security of the Google Account and of the device unlock becomes part of the passkey story. A stolen unlocked phone, or a recovered Google Account that can create a new passkey, is a different threat from phishing a password on a fake site. What this means in practice Bangladeshi Android users should enable a screen lock and, where possible, create passkeys for high-value apps that show the Credential Manager sheet. Developers should implement Credential Manager rather than home-grown FIDO dialogs, and should not block password sign-in until their own telemetry says passkey coverage is adequate. Losing a phone is recoverable if the passkey synced; it is not if the only copy was device-bound and no other method exists. Cyber71 cannot enrol a user in Google Password Manager or reset a Google PIN. What is still unclear Google did not, in the loaded posts, publish Android-wide passkey adoption percentages for 2026. Whether every OEM skin exposes third-party providers correctly is flagged on the developers page as possibly not reflected on some devices. Conditional automatic passkey creation, documented elsewhere in Android identity guides, is not detailed in the 4 September 2025 blog. Enterprise restrictions that disable screen lock or backup can silently prevent passkeys from working.

Sources

  1. Android Developers Blog — Best practices for migrating users to passkeys with Credential Manager2026-09-24
  2. Google for Developers — Passkey support on Android and Chrome2026-09-24

Cyber71 links the primary material behind each report so readers can check it directly. External pages are not under our control and may change.

All research

Need help with a security issue?

Describe the situation and we will open a private case for follow-up.

Get Security Help