Scope of Work After Initial Launch to Rapidly Adopt Passkeys

This roll-out strategy is designed to rapidly increase adoption of passkeys after initial launch. This page presents variables to consider as you examine the scope of work required after initial launch of this roll-out strategy.

info

The initial launch is the moment in time when a service provider first makes passkeys available to customers.

Team

The same core team and extended team is kept in place after the initial launch to continue to rapidly increase the adoption of passkeys by end users.

Team structure

The same team is kept in place after the initial launch to continue to rapidly increase end user passkey adoption.

Supported use cases

After initial launch, your organization can consider supporting additional use cases. The use cases you choose to support next should be tailored to your organization's unique business needs.

The required use cases for initial launch include:

• Create, view, and manage passkeys in Account Settings
• Sign in
• New Account Creation with a Passkey
• Deprecate SMS OTP

If all of the use cases listed above were not included in the initial launch, consider including them after initial launch.

• Create Passkey After Account Recovery Due To Forgotten Password
• Use Passkeys Created on Websites to Sign In to Apps (and Apps to Websites)
• Passkey Management UI: Best Practices for Combining All Passkey Types
• Remove Passkeys from Service Provider Account Settings
• Cross-Device Sign-In

For example, if there is a business need to reduce costs associated with using SMS text messaging for purposes of authentication, then you can support the Deprecate SMS OTP use case.

If there is a business need to migrate users from your website to your mobile app, you should support the Use Passkeys Created on Websites to Sign In to Apps (and Apps to Websites) use case.

Supported passkey types

There are two type of passkeys, synced passkeys and device-bound passkeys. While the initial launch of passkeys supports both, you should implement the Passkey Management UI: Best Practices for Combining All Passkey Types if you have not already.

Supported operating systems

Your product managers should determine the priority of supporting passkeys on additional operating systems in relation to other requirements from the organization. You can monitor the Device Support page on passkeys.dev to identify supported operating systems and browsers.

Supported regions and languages

Your product managers should determine the priority of supporting passkeys in other regions and languages.

Password strategy

You might choose to continue using passwords for some number of years after launch. It is common for organizations to begin plans to remove passwords as an authentication method in the years after initial launch. To learn more about what this entails, refer to the The Future of Passkeys or watch Watch Matthias Keller from KAYAK outline why KAYAK uses passkeys and removed passwords from their services in this video segment from UX Webinar Series: Drive Revenue and Decrease Costs with Passkeys for Consumer Authentication.

Baseline metrics

After the initial launch, organizations typically document and analyze passkey usage metrics each month. You can learn more about passkey metrics and use the Authentication Method Inventory, Costs, and User Experience Analysis Worksheet as a guide in this process.