frames-devs

We're doing it wrong. 

This is a hot take: I don't think legacy wallet UX is a problem (as long as you stay away from metamask).
None of the crypto-noobs I've onboarded had issues with writing down a seed phrase and signing transactions. The "signature popup fear" is unfounded. People like to get a confirmation when they are doing something, especially with the strong commitment that comes with blockchains. If people don't want to create/use a wallet to use your product, the wallet is not the problem, your product is. 

Yet we are trying so hard to make web3 look like web2. And people hate creating and logging in their web2 accounts (I've been locked out of my google account more often than any wallet that I own).

Today I have passkeys and embedded wallets all over the place, and every time I'm prompted to login I have no idea if I'm logging in to the right account or creating a new one. 

An example of today, trying to sign in my Bracket account:

Ensuring smooth user experience in navigating web3 platforms is crucial. Simplifying processes and enhancing user guidance can alleviate uncertainties and boost adoption rates. Streamlining authentication methods can prevent user frustration and increase platform usability.