[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eDashlane successfully integrated passkeys for passwordless authentication across its platform, enhancing security for its 18+ million users.\u003c/p\u003e\n"],["\u003cp\u003eUser satisfaction with passkey flows surpasses that of traditional password flows, with a 70% higher conversion rate for passkey authentication.\u003c/p\u003e\n"],["\u003cp\u003ePasskey registration conversion rates are significantly higher than password registration rates (63% vs 25%), showcasing improved relevance and precision.\u003c/p\u003e\n"],["\u003cp\u003eDashlane's swift implementation of passkeys, facilitated by the Credential Manager API on Android, demonstrates proactive adaptation to evolving authentication methods.\u003c/p\u003e\n"],["\u003cp\u003ePasskey adoption among Dashlane users is experiencing steady growth, indicating a positive trend towards passwordless security.\u003c/p\u003e\n"]]],[],null,["# Password manager Dashlane sees 70% increase in conversion rate for signing-in with passkeys compared to passwords\n\nDashlane is a password management tool that provides a secure way to manage\nuser credentials, access control, and authentication across multiple systems\nand applications. Dashlane has over 18 million users and 20,000 businesses in\n180 countries. It's available on Android, iOS, macOS, Windows, and as a web app\nwith an extension for Chrome, Firefox, Edge, and Safari.\n\nThe opportunity\n---------------\n\nMany users choose password managers because of the pain and frustration of\ndealing with passwords. While password managers help here, the fact remains\nthat one of the biggest issues with passwords are security breaches. Passkeys\non the other hand bring passwordless authentication with major advancements in\nsecurity.\n\n[Passkeys](https://developers.google.com/identity/passkeys) are a simple and secure authentication technology that enables\nsigning in to online accounts without entering a password. They cannot be\nreused, don't leak in server breaches of [relying parties](https://developers.google.com/identity/passkeys/developer-guide#anatomy_of_a_passkey_system), and protect users\nfrom [phishing attacks](https://developers.google.com/identity/passkeys#security-considerations). Passkeys are built on open standards and work on all\nmajor platforms and browsers.\n\nAs an authentication tool, Dashlane's primary goal is to ensure customers'\ncredentials are kept safe. They realized how significant the impact of\npasskeys could be to the security of their users and adapted their applications\nto support passkeys across devices, browsers, and platforms. With [passkey support](https://www.dashlane.com/passkeys)\nthey provide users a secure and convenient access with a\nphishing-resistant authentication method.\n\nImplementation\n--------------\n\nPasskeys as a replacement for passwords is a relatively new concept and to\naddress the challenge of going from a familiar to an unfamiliar way of logging\nin, the Dashlane team considered various solutions.\n\nOn the desktop web they implemented [conditional UI](https://developer.chrome.com/blog/webauthn-conditional-ui/) support through a browser\nextension to help users gracefully navigate the choice between using a password\nand a passkey to log into websites that support both login methods. As soon as\nthe user taps on the username input field, an autofill suggestion dialog pops\nup with the stored passkeys and password autofill suggestions. The user can\nthen choose an account and use the device screen lock to sign in.\n| **Note:** To learn how to add passkeys support with conditional UI to your web app check out [Create a passkey for passwordless logins](https://web.dev/passkey-registration/) and [Sign in with a passkey through form autofill](https://web.dev/passkey-form-autofill/).\n\nOn Android, they used the [Credential Manager API](https://developer.android.com/training/sign-in/passkeys) which supports multiple\nsign-in methods, such as username and password, passkeys, and federated\nsign-in solutions (such as Sign-in with Google) in a single API. The Credential\nManager simplifies the development process and it has enabled Dashlane to\nimplement passkeys support on Android in 8 weeks with a team of one engineer.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n| **Note:** If you are a credential provider, such as a password manager app, check out the guide on how to integrate [Credential Manager with your credential provider solution](https://developer.android.com/training/sign-in/credential-provider).\n\nResults\n-------\n\nData shows that users are more satisfied with the passkey flows than the\nexisting password flows.\n\nThe conversion rate is 92% on passkey authentication opportunities on the web\n(when Dashlane suggests a saved passkey for the user to sign in), compared to a\n54% conversion rate on opportunities to automatically sign in with passwords.\nThat's a 70% increase in conversion rate compared to passwords--a great sign\nfor passkey adoption.\n\n\n\u003cbr /\u003e\n\n\n*Password sign-in prompt.* \n*Passkey sign-in prompt* \nThe conversion rate here refers to user actions when they visit websites that support passkeys. If a user attempts to register or use a passkey they will see a Dashlane dialog appear on Chrome on desktop. If they proceed and create new or use an existing passkey it is considered a success. If they dismiss the dialog or cancel passkey creation, it's considered a failure. The same user experience flow applies to passwords.\n\n\u003cbr /\u003e\n\nDashlane also saw a 63% conversion rate on passkey registration opportunities\n(when Dashlane offers to save a newly created passkey to the user's vault)\ncompared to only around 25% conversion rate on suggestions to save new\npasswords. This indicates that Dashlane's suggestions to save passkeys are more\nrelevant and precise than the suggestions to save passwords.\nSave passkey prompt.\n\n\u003cbr /\u003e\n\n\n*Save password prompt.* \n\n\u003cbr /\u003e\n\nDashlane observed an acceleration of passkey usage with 6.8% average weekly\ngrowth of passkeys saved and used on the web.\n\nTakeaways\n---------\n\nWhile passkeys are a new technology that users are just starting to get familiar\nwith, the adoption rate and positive engagement rates show that Dashlane users\nare more satisfied with passkey flows than the existing password flows.\n\nDashlane tracks and investigates all passkey errors and says that there haven't\nbeen many. They also receive few questions from customers around how to use or\nmanage their passkeys. This can be a sign of an intuitive user experience,\nclear help center documentation, a tendency of passkey users today already\nbeing knowledgeable about passkeys, or some combination of these factors.\n\n\"Staying up to date on developments in the market landscape and industry,\nanticipating the potential impact to your customers' experience, and being\nready to meet their needs can pay off. Thanks in part to our rapid\nimplementation of the Credential Manager API, customers can rest assured that\nthey can continue to rely on Dashlane to store and help them access services,\nv no matter how authentication methods evolve.\"\n\n--Rew Islam, Director of Product Engineering and Innovation at Dashlane"]]