64 karma · joined May 3, 2024
What changed: Apple & Google want to enter deeper into customer connection and at the same time offer a more secure and convenient authentication for their customers.
Google releasing this functionality to production is relatively new for those outside the passkey community, although it is not surprising when following Chrome Dev.
Overall, the tendency of Apple and Google to focus on passkeys for consumers and make them accessible is an interesting angle. In our blog, we frequently discuss password managers; in fact, we are also 1Password customers. Passage is a part of 1Password that operates in the same field as we do, likely because they recognize a potential threat from Apple and Google in the consumer space.
For companies implementing passkeys this is quite a significant change, because now a Chrome can carry a passkey that used to be a cross-device case before. The ecosystem is getting more complicated...
You are right. For transparency, I also work for Corbado and was part of the discussion. I think most of the developers prefer a native component if they have a framework in use. In this case, because of the SSR trend, it's just a bit more difficult to use web components as a base for all of them. Would you not agree? Of course, you could offer native implementation in all variants, but that's very difficult.