The message is clear: Ethereum is finally treating UX as core infrastructure 🛠️✨
For designers and builders, this opens the door to creating crypto apps that feel as smooth as Web2 *but way more powerful*
Ethereum rolled out the Pectra upgrade, introducing features like EIP-7702 and EIP-3074
Most see this as a backend change, but it’s a big deal for UX/UI too
Here’s why it matters 🧵
Even on the leadership side, Ethereum is getting more product-focused
Vitalik is stepping back so others can push UX-forward initiatives faster. There's a real appetite to make the protocol feel modern ✨
Cross-Chain = Cross-Messy
Most bridges overload users with steps, jargon, and zero context
Here's a better way to guide users across chains 👇
>Hints for every step
>Human-readable summaries
>No surprises
@hedera 9/ This tool is about more than transactions - it’s about enabling trust, coordination, and transparency at the highest level of decentralized governance.
The @hedera Transaction Tool is an open-source app for preparing, signing & submitting Hedera transactions.
We designed the full experience to support council members, devs & power users
Here’s a breakdown of how we built the UX 👇
@hedera 8/ Component System 🧩
To scale the UX, we built a flexible component library:
- Custom modals
- Status banners
- Button hierarchy
- Signature states
> Each designed for security-first environments.
@MetaMask@base@arbitrum@Optimism 7/ TL;DR: Better gas UX = more adoption 🚀
If your dApp expects users to understand gas, you’re designing for devs, not users
> Abstract when possible
> Educate when needed
> Design with clarity and context
UX around gas isn't just a dev task - it's a design challenge 🧑💻🎨
The UX of Gas Fees: How to Stop Confusing Users 🧵
Gas fees are one of Web3’s most frustrating UX hurdles
New users don’t understand them. Even experienced ones get annoyed
So how do we fix this? Let's break it down 👇
@MetaMask@base@arbitrum@Optimism 6/ Design tips: how to present gas fees better in your UI
Use real-world equivalents: eg “~$0.03 fee”
Explain why there's a fee in human terms (“fee to record this action on-chain”)
Avoid technical jargon unless in advanced mode
Offer multiple fee tiers, not just one number