Notes * Building With Claude Code → Notes * Building With Claude Code → Notes * Building With Claude Code → Notes * Building With Claude Code → Notes * Building With Claude Code → Notes * Building With Claude Code →
Case study · Web3

Trady — Interface

Refocusing a trading terminal around how memecoin traders find, assess and act.

After Early Access feedback that V1 felt overloaded, Trady refocused on active memecoin traders. I led the V2 redesign and rebrand, and designed Discover and Trade end to end.

My roleHands-on Design Lead
Team2 senior product designers, 1 graphic designer
TimelineSept 2025 – Jun 2026
PlatformDesktop web
View live product ↗
Trady's live Trade page for the AGI token, showing the price chart, Buy/Sell panel, and live trades list
Trade: the live product — chart, execution panel, and trade activity in one workspace.
Context

Trady is a non-custodial, cross-chain trading terminal. V1 was a customisable, modular terminal for a broad crypto audience.

Finding

Early Access feedback in March 2026: the interface felt overloaded and hard to scan.

Response

The CEO narrowed V2 to active memecoin traders — more frequent trading was the business bet.

The V2 journey, shaped with the CEO.

My role and responsibilities

As a hands-on Design Lead, I designed the core trading surfaces myself and led a team of two senior product designers and a graphic designer, working directly with the CEO and CTO. My goals were to:

  1. Set up design processes that would get the product to release.
  2. Improve the speed and consistency of design delivery.
  3. Set up an AI-assisted design workflow.

V1 — Organising the work for early access

  • Reorganised Figma into three files: design system, work in progress and approved designs.
  • Reviewed existing flows with the CEO and CTO, closed design gaps and designed parts of V1.
  • Established regular design reviews, syncs and engineering handoff.
  • Worked on the design system and hired a dedicated designer for it.

V2 — Product design and leadership

  • Shaped the main user journey with the CEO: find → assess → act.
  • Designed Discover and Trade, including the trading module, end to end.
  • Worked on the rebrand with the team and ran daily design reviews.
  • Set up the AI-assisted design workflow and coordinated engineering handoff.
How it unfolded
Autumn 2025

Prepare V1 for early access

I joined pre-launch, when the CEO managed designers directly and there was no design process. With the CEO and CTO, I audited V1 for missing work and technical constraints before release.

March 2026

Early access and audience pivot

V1 entered Early Access; the feedback that it felt overloaded led to the focus on active memecoin traders.

April – May

V2 redesign and rebrand

We redesigned V2 around find → assess → act and rebranded in under two months, with daily design reviews and an AI-assisted workflow.

June – August

Handoff and release

My involvement ended in June, after design handoff. A part-time designer supported implementation, and V2 was released in August.

01 — Discover: find and assess from the list

V1 Markets gave space to market-wide sentiment, price and a 7-day chart, and squeezed risk into one Audit score behind a hover. The goal: spot, judge and act on a token without leaving the list.

RiskOne Audit scoreIndividual risk indicators in every row
DataPrice, change % and a 7-day chartMarket cap, liquidity, volume and transactions first
DiscoveryFavourites, All Crypto, TrendingTrending, Smart Money, KOL Alpha and Custom Radar
ActionA Buy button per rowQuick Buy and Sell with shared amount controls

How we decided: our V1 audit against the new audience, Early Access feedback, my competitive analysis (Axiom as the main reference), the CEO's AI-assisted wireframe and our trading advisor's review. Several options went through advisor review and iteration before the final direction was aligned with the CEO.

V1 Markets page: a broad, sortable asset list with core metrics and a single aggregated audit score
V1 — Markets
V2 Discover page: Biggest Movers panel, Trending/Smart Money/KOL Alpha/Custom Radar modes, and a token list with individual risk indicators
V2 — Discover
02 — Trade: should I enter, and how?

My main piece of work. V1 put many controls on the same level as the order flow, so I sorted each by frequency × criticality × persistence: what changes on most trades stays in the primary flow, occasional settings move a level down, and set-once choices become presets.

Order typeHidden in a dropdownMarket, Limit and TP/SL visible in one clear order flow
ExecutionMostly just slippageExecution settings grouped into reusable presets
Token infoBehind a Token Overview sectionHolder and dev stats beside order preparation

How we decided: CEO and product input, sessions with our trading advisor to challenge the domain logic and find the minimum information needed during execution, patterns from other trading terminals, and technical constraints.

V1 Trade page: a dense workspace with the chart, a Dev/Tracked/You activity column, and the order form competing for space
V1 — Trade
V2 Trade page: a wider chart, a selective token summary, and a clearer buy/sell panel
V2 — Trade
AI-assisted design workflow

How we used Claude Code during the redesign — from an initial wireframe to refined UI in Figma. AI made the starting points faster; screen logic, design decisions and final quality stayed with designers.

A — Define the direction

  1. 01

    Inputs

    The existing screen, competitor references and V1 Early Access feedback.

  2. 02

    Initial wireframe

    The CEO used Claude Code to combine the inputs into a low-fidelity draft.

  3. 03

    Joint review

    The CEO and I discussed and refined the screen logic before any UI design.

  4. 04

    Design ownership

    I designed the screen myself, or briefed a designer on its logic and reviewed their work.

B — Build and refine the UI

  1. 01

    Manual foundation

    Brandbook → Figma styles → a reference screen designed by the team.

  2. 02

    Shared AI context

    The brandbook and the reference screen guided Claude Code.

  3. 03

    Working designs

    Screens, sections and basic library components brought into Figma.

  4. 04

    Iterate

    Manual edits in Figma, alternating with further Claude Code prompts.

The reference screen was designed by hand first, so AI-assisted UI work built on an approved look instead of inventing one. Claude Code was most useful for small components and their states; complex trading screens still needed substantial manual design, and every output was reviewed before it reached the library.

See a Claude concept refined into a library component →

Outcomes and deliverables
LiveV2 shipped in August 2026 at trady.xyz
< 2 monthsfor the redesign and rebrand, with a part-time team
PositiveKOL feedback on V2 — the group whose V1 feedback triggered the pivot

Against my goals

01

Get the product to release

Designs were handed off at the end of the redesign; engineering built V2 with a part-time designer supporting implementation, and it shipped in August.

02

Faster, more consistent delivery

Before: the CEO managed designers directly, with no shared process. After: daily design reviews, a reorganised Figma, a shared V2 library and documentation.

03

An AI-assisted design workflow

Claude Code became part of the team's workflow for small components and their states, with every output reviewed manually.

What I delivered

Product
Find → assess → act journey Discover page 4 discovery modes Token-risk indicators Quick Buy & Sell Trade page Trading module: Market, Limit, TP/SL Execution presets Token stats in the order flow V2 rebrand, with the team
Team and process
Figma reorganised into 3 files Shared V2 component library Documentation Daily design reviews Engineering handoff AI-assisted design workflow Design-system designer hired

These are delivery outcomes plus one qualitative signal. Decisions rested on the V1 audit, competitor analysis and a trading advisor's review rather than user testing, and impact on trading, conversion or revenue wasn't measured. Next I'd track time from Discover to first trade, the share of trades via Quick Buy/Sell, and trades per active trader.

What I learned
  • Pick the audience before the interface. V1 was designed for everyone. V2 got clearer once we fixed one audience first — and KOL feedback turned positive.
  • Removing is a design decision too. Not less information: V2 deprioritised whatever competed with the next decision — and risked hiding what some traders still need.
  • Make time for research, even when time is short. A few quick tests with target traders could have validated key assumptions; advisor input and competitor patterns helped, but don't replace direct user feedback.
← Back to all projects
Next project

Trady — Design System & Process

View case study →