The first step into the big world of Web3.

Pretty important to get right.

Yet here is an example from Zapper, with commentary from ChainLinkGod:

Untitled

https://twitter.com/ChainLinkGod/status/1553137243845378048

To be fair to Zapper, this is more of a technology problem than a DApp problem, and we’re stuck waiting until wallets are better integrated with browsers and web3 is just “the web”.

1inch is even worse, because they make you choose network first. They literally just add an extra step to confuse you:

Untitled

The curse of too many options

Nielsen’s Usability Maturity Model is a good way of judging your project’s overall approach to UX. A lot of web3 apps are somewhere around the “developer-centred usability” step. The tendency is to give as much control as possible, even if that creates information overload for the less experienced. There’s nothing wrong with catering for the experts, but as the industry progresses, this flexibility should be in the form of hidden shortcuts, not overwhelming customisability.

What this means in real terms is you should strive for fewer options, less overload, and simpler designs.

WalletConnect and Browser Default

WalletConnect can be used to connect to all mobile wallets.

Most desktop browsers identify the wallet that you are currently using as a default option. This can be detected by web3 apps.