Background
Web3 technology promises to revolutionize how we interact with digital finance, but its complexity creates a massive barrier to adoption. I noticed that existing Web3 platforms prioritized technical features over user experience, making it nearly impossible for newcomers to participate in the decentralized economy.
I decided to design Clamp as a case study exploring what Web3 could look like if it truly prioritized accessibility. The goal was to create a platform where anyone—regardless of technical expertise—could confidently list tokens, connect wallets, and complete KYC verification without confusion or frustration.
Core problem
Some Web3 platforms suffer from fundamental UX problems that actively prevent mainstream adoption. Complex user flows confused new users at every step. Inconsistent visual hierarchy made it unclear what actions to take next. Missing success states and error handling left users uncertain whether their actions succeeded or failed. Poor mobile experiences excluded users who primarily accessed crypto through their phones. Technical jargon created an intimidating barrier that communicated "this isn't for you."
These weren't just design issues—they were adoption blockers. Every confusing flow, every undefined error state, every piece of unexplained jargon convinced potential users that Web3 was too complicated for them. The platforms were designed by crypto natives for crypto natives, completely ignoring the millions of people who could benefit from decentralized finance if only it were approachable.
Crafting a User-Centered Approach
I focused on radical simplification—stripping away unnecessary complexity while maintaining the power and functionality that makes Web3 valuable. The aim was to prove that accessible design and Web3 technology aren't mutually exclusive.
The design approach centered on three core areas: token listing, wallet connection, and KYC verification. For each flow, I applied user-centered design principles that are standard in traditional fintech but rarely seen in Web3. This meant clear visual hierarchy, obvious next steps, comprehensive success and error states, and plain language that explained technical concepts without dumbing them down.
Key design decisions included:
Progressive disclosure to prevent overwhelming new users
Mobile-first responsive design for broader accessibility
Success states that clearly confirmed completed actions
Error messages that explained what went wrong and how to fix it
Plain language alternatives for technical terms, with tooltips for those who wanted deeper understanding
Streamlined flows that reduced steps without sacrificing security
I used Claude AI extensively throughout the design process—for copy iteration, wireframing exploration, and user flow optimization. This AI-assisted approach allowed me to rapidly test multiple variations of interface copy and interaction patterns, ultimately accelerating the design timeline while improving quality.
The design was built in Figma with a style guide that ensured consistency across all touchpoints. Every component was designed mobile-first, then scaled up to desktop, ensuring accessibility across devices.
Design Impact
The project successfully demonstrated that Web3 can be approachable without sacrificing functionality. The streamlined flows reduced cognitive load for new users, making complex actions like wallet connection and KYC verification feel manageable. The mobile-ready design positioned the platform for broader adoption beyond desktop-only crypto enthusiasts.
The AI-accelerated design process proved that leveraging tools like Claude can significantly speed up iteration while maintaining design quality. This case study serves as proof that accessible design isn't about removing power—it's about removing unnecessary barriers that prevent people from accessing that power.