惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Engineering at Meta
Engineering at Meta
D
Docker
IT之家
IT之家
博客园_首页
罗磊的独立博客
V
V2EX
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
美团技术团队
Y
Y Combinator Blog
博客园 - 聂微东
量子位
阮一峰的网络日志
阮一峰的网络日志
GbyAI
GbyAI
Microsoft Security Blog
Microsoft Security Blog
博客园 - Franky
Martin Fowler
Martin Fowler
Jina AI
Jina AI
大猫的无限游戏
大猫的无限游戏
C
Check Point Blog
月光博客
月光博客
G
Google Developers Blog
B
Blog
T
The Blog of Author Tim Ferriss
爱范儿
爱范儿

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
What Web3 Founders Actually Think About Design (And Why M...
soma ryuu · 2026-05-19 · via DEV Community

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.