Couple screens from the whole scenario

A DEX gives users access to early and niche tokens — swapping digital assets directly from their wallet, without third parties or the KYC process mandatory in traditional finance.

Behind swaps sits Liquidity Provision, where users lock a pair of assets (like TON and USDT) and earn a share of every swap fee from that pair — and Farming, which lets users stake their token pair position into additional reward programs (the DeFi equivalent of a certificate of deposit).

Farming and liquidity have a high entry barrier and are popular only among advanced users.

High-level DEX user journey and conversion funnel

Part of the V1 UX audit

First: consolidate everything. Then define the scope — release by release. What ships in the first release, what comes next, what needs to be accounted for now even if it's built later. Everything lands in one structured file — a shared source of truth for design and engineering before jumping into wireframing.

High-level overview of the technical changes

We audit DEXes across the market spectrum, mapping every step of the LP provision flow: Uniswap, Zapper, Beta, and others. There are no similar products on the market. Still, we identify recurring UX patterns — the traps to avoid and the solutions worth borrowing.

UX audit overview

In a team session, we land on a flow where the user first selects the liquidity pool version — a decision driven by technical constraints. Early usability tests with less experienced users reveal that they get lost at the v1/v2 selection step. On top of that, the version filter obscures a large portion of available pools from view. What users actually care about first is the token pair and the farming yield on it. We also discover that most users don't know what farming is or why it matters. We take that feedback seriously, step back, and rethink the entire flow.

Iteration 1

After a brainstorm with the engineering team, we move all technical complexity behind the scenes and cut unnecessary steps, simplifying the flow further.

On the pool selection page, we highlight the new pools and add a tooltip to the existing Farm label — keeping Tesler's Law in mind: some complexity has to live somewhere. We bring AI tools into the copy workflow — cutting that step down significantly.

Tooltips on the pool list page

As part of onboarding, we add a link in the form description pointing users to a guide that answers their most common questions.

If a user arrives from the pool page, the token pair is pre-selected. If not, the first token defaults to TON — the base asset for all transactions — and we prompt them to select a second token to continue.

Once the second token is selected, we surface the highest-yield pool automatically.

If a user somehow lands in the liquidity form with a lower-yield pool already selected, we surface a smart recommendation pointing them to the better-performing option.

As the final touch, we embed a farming card directly into the liquidity form — combining liquidity provision and farming into a single transaction to drive conversion into farming. For onboarding, we add a modal that walks users through each step.

When farming is available in the selected pool, we auto-enable the toggle. We make the APR change explicit — so users immediately see how their yield improves.

We can’t meaningfully grow anything without an entry point on the main screen.

As a final step, I run all in-product copy through AI tools to check grammar and punctuation.

From there, we assemble the full flow with all states, animations, and specs for a clean handoff to engineering.

Final layouts with full user flow and specs