← Back

Simplifying the crypto deposit flow

Overview

The crypto deposit flow was one of the most critical — and most friction-heavy — parts of the app, and a legacy flow that hadn't been improved since 2021. At the same time, the team was rebuilding the design system, and deposit became the first flow to be redesigned under it, given the time and effort available. I wasn't involved in building the new design system itself, but I worked in parallel to migrate it into the deposit flow redesign as I went, given the limited timeline.

Deposit sits directly on the critical path. A user cannot place their first trade without depositing funds first, making it one of the highest-leverage flows to get right.

Role
Product Designer
Involvement
UX Design
User Flow
Copy & Instructional Design
Competitive Benchmarking
Timeline
Oct–Dec 2025
Challenge

How might we simplify the crypto deposit flow so that both new and experienced traders can complete their first deposit with confidence?

Metrics were limited at the company, so I relied heavily on competitive analysis, current UX patterns, and heuristics rather than quantitative data to drive this redesign.

From a design audit of our existing flow — compared against current industry standards and competitor patterns — I identified three main issues.

The deposit information screen had become a dense wall of detail, mixing essential information with content users didn't need. For experienced traders it was manageable. For newer crypto users, it created immediate hesitation.

  • 01Excessive detail on a single screen obscured what actually mattered
  • 02Unnecessary information made it hard to distinguish critical steps
  • 03The coin list was static and alphabetical, with no display order that made sense to the user — unhelpful, especially for first-time users
Before: static alphabetical coin list with no hierarchy, and a deposit screen burying important information below the fold amid too many irrelevant details
Personalizing coin selection

Every user saw the same undifferentiated list regardless of their existing holdings, so I introduced a "Quick Select" section that surfaces personalized options first.

  • The original list worked reasonably well for new users with no funds, but for users who already held tokens, it did nothing to reflect that
  • Quick Select is ordered by the user's actual holdings: if a user already has certain tokens in their wallet, those surface first, since they're the most likely tokens to be re-deposited
  • For users with no wallet holdings, the list defaults to popular market tokens instead, to support decision-making with no personal signal to draw on
Before: static, undifferentiated coin list with no personalization
After: Quick Select section prioritizing the user's held assets, then popular coins, followed by the full alphabetical list
Isolating network selection

This step lived bundled with coin selection — a technical decision folded into a simple one, and not even applicable to every token — so I split it into its own dedicated step.

  • One of the more confusing concepts for beginners; giving it a dedicated step gave users the focus to actually understand it
  • Added processing time and required confirmations per network
  • Added an explicit note that the selected network must match the network the user is transferring from, to reduce mismatched transfers

Stakeholders and engineering assumed fewer screens meant faster, simpler completion. I argued the bundling, not the screen count, was the real source of hesitation — backed by benchmarking against Binance, Kraken, OKX, and Coinbase, all of which isolate this step.

This follows Miller's Law: breaking a complex decision into smaller steps reduces cognitive load, even at the cost of an extra screen. Making the step conditional — shown only when a token required it — meant the added structure never penalized the simpler, more common case.

Before: network selection bundled into the deposit screen alongside unrelated information
After: network selection split into its own dedicated screen, showing only information relevant to that choice
Prioritizing the deposit screen

Too much low-priority information surfaced on first landing, so I re-prioritized what actually appeared on that first layer.

  • Identified the core information users actually need on landing: selected token, QR code, selected network, processing time
  • Moved secondary actions out of the primary view: create deposit address, share deposit address
  • Converted the deposit address dropdown into an address book, hidden behind a secondary action — since not every user needs it, and surfacing it by default added confusion rather than utility
Before: dense deposit screen mixing essential and secondary information with no clear hierarchy
After
Outcome

Crypto deposit metrics weren't accessible, so this can't be backed by a completion-rate or conversion number. What I do have: the redesigned flow was well received by both stakeholders and users.

  • Post-launch, we conducted a small number of user interviews; participants were able to move through the new flow easily compared to the existing design
  • User feedback included comments that the information they needed was easier and cleaner to find, and that the processing time detail was helpful
Next Project
Portfolio Visibility for Active Trades
→