Ask HN: Why is WebAuthn so slow to take off?
<i>Passkeys</i> is a new FIDO standard that will let the private keystore be backed by the cloud. It was added to WebAuthn fairly recently. Having keys tied to specific physical devices was a terrible &amp; frustratingly limited scheme that never had any hope. Now that there&#x27;s something a little bit looser, there&#x27;s some small hope WebAuthn starts to become interesting &amp; viable. <a href="https:&#x2F;&#x2F;developer.chrome.com&#x2F;blog&#x2F;webauthn-conditional-ui&#x2F;" rel="nofollow">https:&#x2F;&#x2F;developer.chrome.com&#x2F;blog&#x2F;webauthn-conditional-ui&#x2F;</a><p>Another huge challenge is that there are so very many ways for developers to use this tech. There are a truly humbling amount of scenarios &amp; flows one can set-up. Many of the most direct paths continue to have the user already set up an account via regular email&#x2F;password, so users still end up doing the same account management anyways. I&#x27;m missing the link to the wonderful wonderful guide I spent a couple commute rides reading, but it was one of the longest most technical pieces I&#x27;ve read in quite a while. &quot;Introducing the WebAuthn API&quot; is perhaps a reasonably ok substitute. <a href="https:&#x2F;&#x2F;medium.com&#x2F;webauthnworks&#x2F;introduction-to-webauthn-api-5fd1fb46c285" rel="nofollow">https:&#x2F;&#x2F;medium.com&#x2F;webauthnworks&#x2F;introduction-to-webauthn-ap...</a>