\n
![](\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEg_U3Am1xHEJCOfvxwHh3sU-TgtPGh7ScMYQH4PhmXyZuLsnGoT1eRhmpU5L8qq07jxICVcHcWJAmR4vjMhN8RMBA_xC3pmtgnGQ0EZk6ce7PmatwSMdYpFt3ZfuPWIf7IAMbD4ZCqJ_t4ciOJeyEUM_ASkQfMhHAuEjKpxjnkYnTK0ugRz42oPyTTv-7s\/s1600\/social-Blog-post-describing-migration-from-existing-Auth-APIs-to-CredMan-API.png\")
<\/p>\nPosted by Diego Zavala and Jason Lucibello \u2013 Product Managers<\/em><\/p>\n In 2023, we introduced Credential Manager for Android<\/a>. Credential Manager creates a unified experience for passkeys, Sign in with Google, and passwords, allowing seamless sign-in and eliminating the need for users to type in usernames or passwords.<\/p>\n To bring Credential Manager\u2019s benefits to more Android users and simplify developers\u2019 integration efforts, APIs that were previously deprecated<\/a> will continue their phased removals and shutdowns. These APIs include:<\/p>\n Developers with apps that still use these APIs should migrate to Credential Manager<\/a> as soon as possible.<\/b> Credential Manager supports all authentication features included in these legacy APIs, as well as streamlined journeys for users and modernizes the experience with passkey support and streamlined user journeys. Developers looking to implement authorization functionality for Google Accounts, such as scoped access to a service like Google Drive, should continue to use the AuthorizationClient<\/a><\/span> API.<\/p>\n Status: <\/b>Removed<\/p>\n Next Update: Fully shut down<\/b> in Q1 2025<\/p>\n Status: <\/b>Deprecated<\/p>\n Next Update:<\/b> Removed in H1 2025<\/p>\n Status:<\/b> Deprecated<\/p>\n Next Update:<\/b> Removed in H1 2025<\/p>\n Status:<\/b> Deprecated<\/p>\n Next Update:<\/b> Removed in H2 2025<\/p>\n Status:<\/b> Deprecated<\/p>\n Next Update:<\/b> Removed in H2 2025<\/p>\n<\/blockquote>\n Credential Manager delivers multiple advantages to users and developers over the deprecated APIs:<\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n For developers previously using our deprecated APIs, the transition to Credential Manager is smooth and intuitive. Developers like X (formerly known as Twitter), Pinterest have already experienced the benefits of the upgrade. X shared with us that Credential Manager\u2019s unified approach made migration and maintenance effortless, while Pinterest expressed a smooth process for both users and engineers with Credential Manager.<\/p>\n <\/image><\/p>\n <\/image><\/p>\n Developers can use the following guides to make adopting Credential Manager even easier:<\/p>\n Your input is very valuable to us as we continue to refine and improve our authentication services. Please keep providing us feedback on the issue tracker<\/a> and share your experience<\/a> integrating Credential Manager!<\/p>\n<\/div>\n![](\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEjFZAwTuEczCixWe-6SN-cKy9wx7VuFML578tLjcX-sI4TfzG0M3Y7ODYo_dOEWZzrizvLDgQit-aRGtvmixausO1waHpb_ERBvwmkX6vMMBdFqJXMTGfW43B2KyVZVigGgRcBESvFnR8UST5aAzRBM1mn7FSz-ICYUoxe44NfsxAinWDB48XOhMN_rVEg\/s1600\/header-Blog-post-describing-migration-from-existing-Auth-APIs-to-CredMan-API.png\")
<\/a><\/p>\n<\/div>\nCurrent status of APIs as of September 2024, update plans, and recommended migration guides.<\/span><\/h4>\n
\n
What does each status mean?<\/h4>\n<\/p>\n
\n
\n
\n
\n
Credential Manager offers streamlined, more secure auth journeys<\/h3>\n
\n
1. Easier, more secure sign-ins with passkeys:<\/b> Passkeys are an alternative to passwords that provide an easier and more secure authentication experience, based on industry standards. Credential Manager brings support for passkeys to Android apps.<\/ul>\n<\/ul>\n
\n
2. Frictionless, one-tap sign-in:<\/b> Users select their preferred saved credential from the options offered, without needing to remember or type username or passwords.<\/ul>\n<\/ul>\n
\n
3. Unified UI across all credentials:<\/b> Credential Manager\u2019s one-tap sign-in works with passkeys, Sign in with Google, and passwords. It deduplicates methods for the same account, so users no longer need to remember which method they last used, or which one is the \u201cright\u201d method.<\/ul>\n<\/ul>\n
\n
4. Extended support for password managers:<\/b> Users benefit from using the credentials stored in their preferred password manager on Credential Manager flows, and can even enable multiple password managers at the same time! Passwords managers not only protect users\u2019 credentials, but they also provide additional action and protections to keep users safe, such as upgrading passwords to passkeys, alerting users to password reuse, and containing usage to affiliated apps and domains.<\/ul>\n<\/ul>\n
\n
5. Simplified development:<\/b> Developers can consolidate their sign-in logic into a single, modern API, reducing development overhead and maintenance efforts. New authentication functionality will be released through Credential Manager going forward.<\/ul>\n<\/ul>\n
Adopting Credential Manager is an intuitive upgrade for developers<\/h3>\n
<\/div>\n<\/div>\nShare your feedback<\/h3>\n