Web3 · Treasury · Fyde
Fyde
UX for a new kind of DeFi product, from the first user flows to a launched app, and back later as a consultant to review it.
- Role
- UX consultant
- Scope
- User journeys, information architecture, flows and wireframes before launch, then a UX review of the live product
- Launched
- On Ethereum, late 2023
- Practice
- UX design · Information architecture · Wireframing · UX review

- $3.2Mseed round, led by OP Crypto Ventures
- 2023launched on Ethereum
- 2engagements: UX before launch, then a review of the live app
The problem
Many DAOs hold most of their treasury in their own token. Diversifying means selling it, which pushes the price down, and handing it over somewhere else usually means giving up the votes that come with it.
Fyde offered another way: deposit tokens into a shared pool and receive TRSY, a token backed by the whole basket. You could keep the governance rights of what you deposited. It launched on Ethereum in late 2023, backed by a $3.2 million seed round led by OP Crypto Ventures.
It was a new kind of product, part index fund and part vault, and people had to understand it well enough to trust it with a treasury. My job was to work out the experience before anything was built.
Two ways to build it
After reading the protocol’s documentation, I mapped the main journeys, depositing and withdrawing, and sketched two ways to shape the app around them. A DEX view worked like other index tokens such as DPI: pick a token, enter an amount, deposit. A vault view worked more like Aave, with a page per asset. I wrote the trade-offs on the flows themselves, such as how odd it might feel to press Withdraw and then not choose a token.


The two options as user flows, with open questions noted on them.


Wireframes for the DEX view (top) and the vault view.
Iterate in the open
We chose the DEX view and built on it over successive versions, with quick rounds of user testing in between. Each version answered a question I had listed for the team: which layout, which charts and the data behind them, what the fees panel needed to say, and how to handle several tokens at once.

The working board: questions on the left, five versions on the right.
I delivered the user flows, information architecture, wireframes and the pros and cons of each option. A UI designer then took the mid-fidelity wireframes into the visual design, and the team built and launched the product. The structure I set out made it through to the final app.


The launched app, captured from the Internet Archive (May 2024). The vault table keeps the columns from my wireframes, including current against target weight. The archive saved the page but not its live data, so the figures are empty.
Asked back
Once Fyde was live and the product had evolved, the team asked me back to look at it with fresh eyes. I reviewed the product against Nielsen’s usability heuristics, my own web3 heuristics and the DeFi checklists I use for reviews, and ranked each finding low, medium or high. They included confusing messaging about who the product was for, too many colours competing for attention, user flows that broke in places and too little help in context.
I marked up the live product in Figma and shared screenshots and the full file with the team. For one finding I also sketched several possible fixes.


A finding from the review, and three ways to fix it.
The team improved their messaging, made their icons consistent, added tooltips, streamlined the flows and simplified their use of colour.