Solving the Final Roadblock to Passkeys: a Fractured Development Environment
summary
Claim: passkeys would stop phishing and scale with AI threats but adoption stalls because integration is a fractured full‑stack problem. Evidence: phishing volume is ~5× higher and linguistic complexity up ~177%; only a low double‑digit percent of apps support passkeys; 2022 saw ~400M breached records; ~25% of traffic is malicious and ~20% of logins are takeover attempts. Pain points are account recovery, browser/OS/password‑manager permutations, credential defaults, and management UI. Practical remedy: use a mature hosted provider or a fully featured open‑source reference rather than rolling your own. passkeys require full‑stack thinking hosted solutions today mask many edge cases
AI-written summary · about
chapters (6)
- 0:00Introduction and welcome
- 0:21Passkeys adoption challenges
- 7:20Developer friction with passkeys
- 16:09Solutions for passkey integration
- 19:40Creating demand for passkeys
- 24:10Q&A session
related talks
30mAuthentication for humans, why passkeys finally make sense.
52mPasskeys: The Good, the Bad and the Ugly
15mOur future without passwords
11mThe problem with passkeys
37mAuthentication in 2026: A guide to passkeys, digital credentials and more
24mPasskeys and digital identity best practices
45mPast Time for Passkeys
28mPasskeys: Goodbye Passwords, Hello Frictionless Security!