How to win the four boss battles of your passkey product development quest
summary
Dashlane decides in 2022 to build passkey support early, accepts short-term revenue tradeoffs, and ships a desktop-first solution that works: engineers intercept API calls to position the product as a browser extension authenticator, later adding mobile when platform APIs arrive. Internal buy-in uses Polaroid/Kodak lessons; UX follows pH working-group patterns; launch is quiet at first but usage grows as Amazon and Google add passkeys. Playbook links and PH tools accelerate other teams.
AI-written summary · about
chapters (10)
- 0:00Introduction and housekeeping
- 1:12Passkey quest inspiration
- 3:01Four product development risks
- 5:12Boss one value risk
- 8:24Boss two viability risk
- 14:23Boss three feasibility risk
- 16:30Boss four usability risk
- 19:24Launch and adoption
- 21:11Recap and next steps
- 23:58Q&A session
related talks
52mPasskeys: The Good, the Bad and the Ugly
24mPasskeys and digital identity best practices
37mAuthentication in 2026: A guide to passkeys, digital credentials and more
42mIntroducing Passkeys for Multiple Use Cases and UX Challenges
27mThe world of Passkeys 🤝🏽 Ruby Slides
26mPasskeys on Android
38mPasswordless App with Passkey
45mPast Time for Passkeys