DEV Community: soma ryuu

What Web3 Founders Actually Think About Design (And Why Most Get It Wrong)

soma ryuu — Mon, 18 May 2026 23:37:28 +0000

Design in Web3 is a contested topic. Founders disagree. Builders disagree. And the products reflect that disagreement — some are obsessively polished, most are not.

Here is what the people actually building the space have said about it, and what it means for anyone designing in this ecosystem.

"Making value exchange as simple as information exchange"

Hayden Adams, the founder of Uniswap, has been one of the clearest voices on why design matters in DeFi. His stated goal was to make value exchange feel as frictionless as opening a webpage — not as complex as using a brokerage.

Uniswap v1 launched with a single-screen interface when every other DEX looked like a Bloomberg terminal. That simplicity was not a limitation — it was the product. The interface was the insight.

When Adams announced the Uniswap Swap Widget in 2022, he described it as "a dream of mine for over 3 years" — the ability to embed a complete trading experience in a single line of code. The design goal was always about reducing distance between intent and action.

This is the right model: treat interface complexity as technical debt, not as a feature.

"If it feels like mobile banking, adoption widens dramatically"

Stani Kulechov, founder of Aave, has been consistent about what drives DeFi adoption. In interviews, his position is clear: if interacting with a protocol feels as familiar as a savings app, the audience grows from thousands to millions.

Aave has been building toward mobile-first experiences that hide technical complexity — seed phrases, gas, contract interactions — behind interfaces that feel like fintech, not blockchain.

This is not dumbing things down. It is respecting users enough to solve the hard problems on their behalf.

The counterargument: Andre Cronje

Not everyone agrees. Andre Cronje, the architect behind Yearn Finance and a significant part of the Fantom ecosystem, has argued that polished UIs create a false sense of security. His view: real DeFi should live closer to the protocol level, where users understand what they are actually signing.

He is not entirely wrong. A beautiful interface on top of a flawed contract does not make the contract safer — it just makes users more confident when they should be cautious.

But this is an argument for better design, not less design. The answer to "pretty UIs hide risks" is not "build ugly UIs." It is to design interfaces where the risk is visible and legible, not buried.

Vitalik on the UX problem Ethereum still has not solved

Vitalik Buterin has written and spoken about Ethereum UX challenges repeatedly. His position is that the "self-sovereign way of using Ethereum" — running your own node, managing your own keys — should have good UX, and currently does not.

This is the core tension in Web3 design: the things that make crypto trustless (self-custody, immutability, on-chain verification) are inherently harder to design for than the things that make Web2 easy (undo buttons, password resets, customer support).

The response from most projects has been to hide the complexity. The better response is to design for it — to make seed phrase backup feel as natural as Face ID setup, to make transaction confirmation feel as clear as a bank transfer notification.

Why VCs made this worse

There is a structural reason Web3 design is bad: capital in crypto flows to protocols, not interfaces. A new AMM mechanism raises $20M. The UI that sits on top of it gets a 2-week sprint from a contractor.

Founders are told to ship infra first, UX later. But "later" rarely comes — because by the time the protocol is stable, a competitor with the same ugly interface has captured the market, and there is no forcing function to clean things up.

The projects that bucked this pattern — Uniswap, Rainbow Wallet, Phantom — did so because a founder or early team member treated design as infrastructure, not decoration.

What this means practically

If you are building in Web3, here is the takeaway from everything the founders above have said, directly or implicitly:

Design is a trust mechanism. An ugly interface signals low investment. A polished interface signals competence. Users read this immediately.
Complexity is not a feature. Every technical concept you force a user to understand is a conversion you are not going to get.
UX debt compounds. The MetaMask onboarding flow — install extension, write down seed phrase, figure out how to buy ETH for gas, navigate to your app — is a documented failure that drove millions of potential users away. It was not fixed for years because no one owned it.
The interface is the product. Especially for consumer-facing protocols. Users do not interact with your smart contract. They interact with your UI.

I work as a Web3 creative director, helping protocols and crypto startups build interfaces that are both technically honest and genuinely usable. If you are working on something in this space, somaryuu.xyz.

Web3 Design: Why Beautiful Interfaces Are Also the Most Usable

soma ryuu — Mon, 18 May 2026 23:32:14 +0000

There is a persistent myth in product design that usability and aesthetics are in tension. That making something beautiful means sacrificing clarity. That "clean" design is a luxury you earn after the functional work is done.

In Web3, this myth is expensive. Here is why beauty and usability are the same thing — and how to design for both at once.

The aesthetics-usability effect is real

Researchers Masaaki Kurosu and Kaori Kashimura proved in 1995 what designers already knew: people perceive beautiful interfaces as easier to use, even when they are not. This is not a bug. It is a feature.

In crypto, where trust is the core product, a polished UI signals competence, legitimacy, and safety. An ugly dashboard does not just look bad — it feels risky. Users hesitate. They second-guess. They leave.

Beauty is not decoration. It is a trust mechanism.

Consistency is the foundation of both

Nothing makes an interface feel more broken than inconsistency. Different button sizes on the same page. Spacing that shifts between sections. Colors that almost match but do not.

Consistency is a usability principle: it reduces cognitive load by making interfaces predictable. It is also an aesthetic principle: it creates visual harmony.

A design token system — a shared set of spacing values, type scales, color variables — solves both problems at the same time. Build it once, apply it everywhere.

Whitespace is doing work

Empty space is not wasted space. It creates hierarchy, guides the eye, and gives elements room to breathe. Dense interfaces feel stressful. Spaced interfaces feel premium.

In DeFi dashboards and NFT platforms, the temptation is to fill every pixel with data. Resist it. Group related information, separate unrelated information, and let the important numbers stand alone.

The best financial UIs in the world — Bloomberg terminal aside — use whitespace aggressively. Your crypto app should too.

Typography is 90% of the interface

Most screens are text. Numbers, labels, actions, descriptions. Typography is not a finishing touch — it is the primary material.

A clear type hierarchy (one display size, one body size, one label size) makes an interface scannable in under a second. Mixing five font sizes with no system makes it impossible to know where to look.

For Web3 specifically: monospace fonts for addresses and numbers (they align, they scan faster, they feel technical in the right way). Humanist sans-serif for everything else.

Motion should explain, not entertain

Animation in UI design has one job: to make change visible. A panel opening, a value updating, a transaction confirming — motion that explains what just happened reduces confusion.

Animation that exists for its own sake — loading spinners with personality, hover effects that take 600ms — adds latency without adding meaning.

The rule: if removing the animation makes the interface harder to understand, keep it. If it just looks cool, cut it.

The practical test

Every design decision should pass two questions simultaneously:

Does this make the interface easier to understand?
Does this make the interface more visually coherent?

If the answer to both is yes, ship it. If only one, reconsider. If neither, delete it.

The best Web3 interfaces — the ones that actually convert visitors into users — are the ones where you cannot separate the functional decisions from the aesthetic ones. They are the same decisions.

I work as a Web3 creative director and full-stack designer, helping crypto projects and DeFi protocols build interfaces that are both beautiful and clear. If that is what you need, somaryuu.xyz.

Web3 Design Principles for DeFi Dashboards

soma ryuu — Mon, 18 May 2026 23:31:23 +0000

DeFi dashboards are some of the hardest UI problems in product design. You are asking people to make financial decisions — often with real money — inside interfaces that are dense, fast-moving, and technically complex. Most of them look terrible. Here is why, and what to do about it.

1. Hierarchy over completeness

The instinct in DeFi is to show everything: APY, TVL, 7d change, pool composition, pending rewards, gas estimate. The result is a wall of numbers that communicates nothing.

Pick one primary action per screen. Everything else is secondary. If a user lands on a staking dashboard, the primary action is "stake." The APY supports that decision — it does not compete with it.

2. Color carries meaning — be consistent

Green/red for up/down is a convention so deep it is basically a standard. Do not break it for aesthetics. If your brand color is red, use it everywhere except price movement indicators.

The same applies to status colors: green for active/healthy, yellow for warning, red for error or loss. Inconsistency here destroys trust faster than any other design mistake.

3. Numbers need context, not decoration

"$1,247,832.44" means nothing without context. Is that good? Compared to what? A sparkline, a percentage change, a benchmark — something that answers "so what?" in 200ms.

Format numbers for humans: $1.2M not $1247832. Round to meaningful precision. Show decimals only when they matter (gas costs: yes. TVL: no).

4. Trust signals are part of the UI

In DeFi, users are trusting your interface with real assets. Audit badges, contract addresses, security indicators — these are not legal boilerplate. They are UI components that reduce the cognitive load of "is this safe?"

Put them close to the action they relate to. An audit badge in the footer is decorative. An audit badge next to the "Approve" button is functional.

5. Loading states and latency are part of the experience

Blockchain transactions are slow. A "pending" state that lasts 30 seconds with no feedback kills confidence. Design for latency: show what is happening, give an estimated time, let the user do something else while they wait.

The best DeFi UIs treat the confirmation flow like a progress indicator, not a loading spinner.

These principles come from real work on DeFi protocols and Web3 products. If you are building something in this space and need creative direction or UI design, I am available at somaryuu.xyz.