web3 design thought of the day #60
📎 no contextual help
hover hints, tooltips, microcopy—these aren’t optional. your users are smart, but they’re not psychic.
#Web3Design#TooltipUX
web3 design thought of the day #59
🔧 unclear error messages
“something went wrong” is a design sin. explain what happened, what it affects, and what users can do about it.
#UXDesign#ErrorUX
web3 design thought of the day #58
🧰 no beginner mode
not everyone wants to ape into layer 3 liquidity mining. offer a beginner mode or simplified ui for the crypto-curious.
#Web3UX#BeginnerUX
web3 design thought of the day #57
💤 zero delight
not everything needs to be a party, but small moments of delight go a long way. celebrate wins. animate gently. humanize the chain.
#InterfaceDesign#DelightUX
web3 design thought of the day #56
📇 no wallet metadata
what chain is this on? what app was this signed in? when did it happen? give users metadata they can use, not just tx hashes.
#UXCrypto#WalletMetadataUX
web3 design thought of the day #55
🎯 vague success states
“transaction successful” is good. “you’ve just added 1.3 eth to the vault” is better. show users the impact of what they did.
#UXDesign#SuccessUX
web3 design thought of the day #54
🗃 no organization in wallets
users have 30 tokens, 10 nfts, and 3 positions. show them folders, categories, or filters. chaos is not a feature.
#CryptoUI#WalletUX
web3 design thought of the day #53
🛠 missing testnets
letting users play with your product on a testnet builds confidence. if your app is high-stakes, give them a safe place to learn.
#Web3Design#TestnetUX
web3 design thought of the day #52
🚫 ignoring tx simulation
if you can simulate a transaction before sending it, do it. help users know what will actually happen, not just guess and click.
#CryptoDesign#SimulationUX
web3 design thought of the day #51
📍 unclear active chain
if a user is on optimism but the dapp expects mainnet, say so—clearly and early. don’t wait for the tx to fail.
#BlockchainDesign#ChainUX
web3 design thought of the day #50
🪄 “magic” wallet interactions
signing messages that change state without user feedback is spooky. explain what’s happening post-sign, even if it’s just a toast.
#UXCrypto#MagicUX
web3 design thought of the day #49
📉 value graphs with no context
a chart going down isn’t always bad. give people timeframes, benchmarks, and captions. otherwise it’s just crypto anxiety in graph form.
#InterfaceDesign#DataVizUX
web3 design thought of the day #48
👥 unclear roles or permissions
many dao or protocol tools assume users understand their access level. show roles clearly and explain what users can and can’t do.
#Web3UX#PermissionsUX
web3 design thought of the day #47
📫 no notifications
users vote, stake, deposit, bridge—and then? silence. use in-app or email notifications to close the loop and confirm success.
#Web3UI#NotificationUX
web3 design thought of the day #46
📣 no changelog or updates
if your protocol just upgraded or changed a feature, tell users. a subtle banner or changelog link goes a long way.
#ProductDesign#ChangelogUX
web3 design thought of the day #45
🔄 confusing refresh behavior
refreshing the page shouldn’t kill your session, wallet connection, or open modal. persist state wherever possible.
#UXDesign#RefreshUX
web3 design thought of the day #44
🧾 too many steps to sign in
connect wallet. switch chain. approve. sign message. refresh. for what—just to see your dashboard? minimize steps or batch them smartly.
#Web3Design#SignInUX
web3 design thought of the day #43
🎛 settings buried or missing
wallet preferences, network toggles, appearance settings—they all get buried like treasure. bring them closer to the surface.
#UIDesign#SettingsUX