Google introduced Credential Manager for Android in 2022 as a unified API that simplifies sign-in across apps and websites, letting users authenticate with passkeys, passwords, or federated identity providers through a single bottom-sheet UI. It replaces the fragmented Account Manager and Google Sign-In flows, aiming to make authentication both more secure and more seamless. This article explains what Credential Manager is, how it works, how to adopt it, and what it means for users and developers.
What Is Credential Manager?
Credential Manager is an Android Jetpack library that provides a single, consistent interface for all authentication methods on Android. It consolidates three previously separate APIs—Account Manager, Google Sign-In, and the FIDO2 API—into one. The library supports:
- Passkeys (passwordless, FIDO-based credentials)
- Passwords (saved in the Android password manager)
- Federated identity (e.g., “Sign in with Google” or “Sign in with Microsoft”)
When an app calls Credential Manager, the system shows a single bottom sheet listing all available credentials and sign-in options. The user picks one, and the flow completes without the app ever handling the raw credential material.
Why Google Built It
Before Credential Manager, Android developers had to integrate multiple SDKs and handle different UI flows for each sign-in method. This led to inconsistent user experiences and higher friction. Google designed Credential Manager to:
- Reduce the number of permissions and APIs developers need to manage.
- Provide a unified UI that users learn once and recognize everywhere.
- Support passkeys, which are more phishing-resistant than passwords and SMS codes.
- Make it easier for third-party password managers to integrate with Android.
The shift to passkeys is a major driver. Passkeys use public-key cryptography and are tied to the device, so they cannot be leaked from a server or intercepted in a phishing attack. Credential Manager is the primary way Google is bringing passkeys to Android apps.
How Credential Manager Works
From a developer perspective, Credential Manager works through a few key steps:
- Your app creates a
GetCredentialRequestspecifying the types of credentials it accepts (e.g., passkeys, passwords, or both). - The system UI displays a bottom sheet with matching credentials from the user’s password manager and any federated identity providers.
- After the user selects a credential, the system returns a
Credentialobject to your app. - Your app verifies the credential on your backend (for passkeys, this means verifying the signature; for passwords, it means sending the password to your server).
For users, the process is simple: they tap a sign-in button, see a bottom sheet with their saved credentials, and tap one to sign in. If they have a passkey saved, they may just use their fingerprint or face unlock to confirm.
How to Choose the Right Authentication Method
If you’re a developer, you don’t have to choose—Credential Manager supports all methods simultaneously. But you should understand the trade-offs:
- Passkeys: Best for security and user convenience (no password to remember). They work across devices via the password manager, but require user consent and a device with a screen lock.
- Passwords: Still the most widely used. Credential Manager can autofill saved passwords, but they are vulnerable to phishing and reuse.
- Federated identity: Good for reducing password fatigue, but you rely on a third party (like Google or Apple) for authentication.
For most apps, offering both passkeys and passwords is the safest approach. You can gradually phase out passwords as passkey adoption grows.
Common Problems and Misconceptions
One common misconception is that Credential Manager is the same as the old Smart Lock for Passwords. It’s not—Smart Lock is deprecated, and Credential Manager is its replacement. Another issue developers face is that Credential Manager requires an internet connection for some flows (like federated sign-in) and that passkeys are not available on Android versions below 9 (API 28) without Google Play services updates.
Users may also worry that Credential Manager stores their passwords in the cloud. It doesn’t—passwords and passkeys are stored locally in the password manager (like Google Password Manager or a third-party one), and only the public key for passkeys is sent to the server.
Comparing Credential Manager to Other Solutions
On iOS, Apple has a similar API called AuthenticationServices that supports passkeys and password autofill. On the web, the WebAuthn standard provides passkey support. Credential Manager is Android’s implementation of the same underlying FIDO2/WebAuthn standards, so cross-platform compatibility is possible when using passkeys.
Compared to the old Account Manager API, Credential Manager is simpler and more secure. It also supports third-party password managers, which the old API did not.
Costs and Adoption
Credential Manager itself is free and open-source (part of AndroidX). There are no licensing fees. The main cost is developer time to migrate from old APIs. Google provides migration guides and the library is backward-compatible with Android 4.4 (API 19) through Google Play services updates.
For users, there is no cost to use Credential Manager. It’s built into the Android system and works with whatever password manager they choose.
Safety and Security Considerations
Credential Manager improves security by reducing phishing risk and encouraging passkey adoption. However, developers must still follow best practices:
- Always verify credentials on your server—never trust the client alone.
- Use HTTPS for all communication.
- Store only the public key for passkeys on your server.
- Implement rate limiting and account recovery flows.
Users should enable a screen lock on their device, as passkeys require it. They should also use a reputable password manager and enable two-factor authentication where available.
Frequently Asked Questions
What is the difference between Credential Manager and Smart Lock?
Smart Lock for Passwords was an older API that only handled passwords and was tied to Google’s password manager. Credential Manager is a more flexible, modern API that supports passkeys, passwords, and federated identity, and it works with any password manager.
Is Credential Manager only for Google accounts?
No. Credential Manager supports any credential that implements the FIDO2/WebAuthn standard, including passkeys from third-party providers like 1Password or Dashlane, and federated identity providers like Microsoft or Facebook.
Do I need to update my app to use Credential Manager?
If your app currently uses the old Account Manager or Google Sign-In APIs, you should migrate to Credential Manager to take advantage of passkeys and the unified UI. The migration is straightforward and Google provides a compatibility guide.
Will Credential Manager work on older Android versions?
Yes. The library is backward-compatible to Android 4.4 (API 19) via Google Play services, but passkeys require Android 9 (API 28) or higher. On older devices, users will still see password and federated sign-in options.
Can users manage their saved credentials?
Yes. Users can view and manage saved passwords and passkeys in their password manager’s settings, usually under “Passwords & accounts” in Android settings. They can also remove credentials from the bottom sheet by long-pressing.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Samsung Smart Speaker Rollable Display: Facts
- HP 9730e: Wide Prints, Not A3 Scans
- What 8888 Does When You Use It as DNS Server
- API Governance for Public Data: What Growing Portfolios Need
- Smartwatches That Can Replace Your Phone
- Enterprise AI Hidden Cost: Data Architecture ROI