All case studies

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
Fyde wireframe: a deposit panel in the centre with a Retain governance toggle and fees, eligible tokens in the wallet on the left, and price and token concentration charts on the right.

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.

Option 1, DEX view: deposit goes from main page to choose asset from dropdown to input amount to deposit; withdraw goes from main page to choose withdraw to input amount. A note asks whether it is confusing to hit withdraw and then not choose a token.

Option 2, Vault view: deposit goes from main page to choose asset, then to its asset page or straight to a supply button, then enter amount; withdraw follows the same pattern through TRSY.

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

DEX view wireframe: a deposit and withdraw panel beside a TRSY price chart and a token concentration chart.

Vault view wireframe: a portfolio page with deposits split into governance rights and a standard pool, then a table of assets to supply with wallet balance, TVL, target and actual concentration, and deposit buttons.

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.

A Figma board: an agenda of open questions on layout, graphs, fees and pages, then five rows of versions: V1, V2 centred layout, V3 vaults view, V4 different charts and V5 multiple tokens.

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 Fyde app in May 2024: a dark home page headed Welcome to Fyde, with Vault, Portfolio, Governance and Leaderboard in the navigation and Deposit and Fyde Points buttons.

Further down the same page: a portfolio summary with deposits, total value locked, TRSY value and points, then a Manage Vault table with columns for asset, wallet balance, liquid and governance TVL, current against target weight, and vault balance.

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.

The live Fyde vault table marked up under the heading Visual importance, Medium: green and red percentage chips are circled, with notes asking whether the visual hierarchy matches importance, since over or underweight may matter more than the coloured liquid and governance percentages.

A suggestion with three versions of the vault table that combine the underweight and overweight figures into one slider per asset, remove the colours and add tooltips.

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.