The best way to solve a big problem is to break it up into lots of tiny problems. It seems like, IMO, the best way to get the general public to adopt passkeys,

The best way to solve a big problem is to break it up into lots of tiny problems. It seems like, IMO, the best way to get the general public to adopt passkeys, and to refine (cough debug cough) the UI, is to use them in low-stakes situations, in a gradual rollout. Instead of focusing on high-stakes use cases, like banking, perhaps: 1: Focus on low-stakes situations, like blogs and news sites 2: Services need easy ways to "add a device," such as opening a link in an email or SMS on the device they want to use. 3: Don't bother syncing passkeys across "devices." Instead, focus on syncing within the browser, where passkeys sync however bookmarks sync. 4: Work on APIs for a user to elect to use a 3rd party passkey manager At that point, services like iCloud, OneDrive, Google Drive, ect, could also provide passkey synchronization. It's up to elect to use such services; because otherwise, re-signing-in on each device the user uses might be "good enough."