Skip to main content
Crypto · Web3

Crypto wallet UX, designed by someone who's actually shipped one.

Crypto UIs lose users in the same three places — dense numbers without context, chain identity buried two taps deep, send flows that pile every decision onto one screen. I designed the Enrichplay product end-to-end with a responsive system that holds across mobile and web, and the patterns that survived are the ones below.

Hire me if you're building a wallet, a DEX, a yield product, or any Web3 thing that real (crypto-curious, not crypto-native) humans need to use. I bring patterns from shipped work, not tutorial-grade case studies.

See Enrichplay case study
Featured project

Enrichplay — end-to-end wallet UX.

End-to-end UI/UX for Enrichplay — a crypto product by founder Abdul Ahad Magsi. One responsive visual system that holds across a 375px phone and a 1440px desktop dashboard. Send flows chunked into single-decision screens. Network identity always near the amount.

Read the case study
  • Responsive system — mobile + web
  • Two density tokens, one component library
  • Network badge always near the amount
  • Chunked send flow + explicit review sheet
  • Tabular figures so amounts don't reflow
  • Tone: confident, not cold
Where the hard work lives

What I focus on in crypto UX.

  • Send / receive flows

    Multi-step money flows broken into single-decision screens. Recipient and amount on one step, network and memo on the next, an explicit review sheet before signing — chosen over the all-on-one-screen pattern that reads badly under stress.

  • Network identity always near the amount

    A network badge that sits within glance-distance of every balance and transaction. Different chains, different totals — surfacing chain identity inline cuts the most common confusion in crypto UIs at the root.

  • Transaction states

    Pending → confirming → confirmed → failed. Tabular figures so amounts don't reflow mid-update; status reads as the answer to the question the user came in with.

  • Gas-fee comprehension

    Most wallets display gas as a raw number. I write it as "this transaction will cost roughly $X to send" — with the breakdown one tap away for the user who wants it.

  • Web3 onboarding for the crypto-curious

    Designed for the user who's two months into crypto, not the user with a Ledger on their desk. Plain language at the boundary, never inline; explain WHY before HOW; keep the surface readable without dumbing the product down.

  • Recoverable vs irreversible UX

    Crypto is unforgiving — once you sign, it's gone. I design recoverable mistakes (typo in amount, wrong contact) with light confirms, irreversible ones (sending to wrong address) with an explicit confirm sheet — Nielsen's error-prevention heuristic applied at the source.

One product, two surfaces — same components, different composition.

A crypto product that lives on phones and on the web has to feel like one product — same hierarchy, same density grammar, same trust signals — even though the screen sizes invite very different layouts. Most crypto UIs fail this on first principles.

From Enrichplay: I built the system before the screens — tokens, components, and patterns that scale. Two density tokens (mobile vs web) carried the breakpoint difference. The components stay identical between mobile and web; what changes is what sits next to them.

ElementMobile compositionWeb composition
LayoutSingle column, thumb-anchoredTwo- or three-column system view
Action railBottom bar — Send / Receive / SwapSide rail on the left edge
Transaction historyBelow the balanceInline next to the balance
Density tokensCompact (8 / 12 / 16 / 24)Spacious (12 / 16 / 24 / 32)
Send flowChunked into two steps + reviewSame chunked flow, wider review sheet
Pricing

How to work together on crypto.

Three engagements — a Sprint for a single flow (send, receive, onboarding) or a wallet UX audit, a Full Project for end-to-end wallet design, or a Retainer for an ongoing crypto product.

  • D
    1–2 weeks

    Design Sprint

    Quick win, ship in 2 weeks.

    $450

    A focused engagement to fix a specific flow, audit an existing product, or design a single feature end-to-end.

    • 1–2 weeks of focused design time
    • 1 specific flow OR a heuristic audit
    • Hi-fi screens for desktop + mobile
    • Interactive Figma prototype
    • Async Loom walkthrough at delivery
    • 1 round of revisions
    Best forFounders who need a specific thing done well, fast — landing page, onboarding flow, settings redesign, or an audit before raising.
  • Most chosen
    F
    4–8 weeks

    Full Project

    End-to-end, research to handoff.

    $800–$1,200

    The full engagement — user research, wireframes, hi-fi screens, prototype, usability testing, and developer handoff.

    • Discovery interviews + research synthesis
    • Wireframes for every flow
    • Hi-fi design (iOS + Android OR desktop + mobile)
    • Design system + reusable components
    • 5-person moderated usability test
    • Interactive prototype + walkthrough
    • Dev handoff specs + 2-week Q&A office hours
    • Up to 3 rounds of revisions
    Best forFounders shipping v1 or doing a serious v2 redesign. The work that needs to feel right, not just look right.
  • M
    Rolling, 2-month min

    Monthly Retainer

    Ongoing design partner.

    $500/mo

    Reserved hours every month for ongoing design work — new features, iteration, system maintenance, async reviews.

    • 40 reserved design hours / month
    • Weekly 30-min sync
    • Async Figma + Slack throughout
    • Design-system governance + extensions
    • Roll-over up to 8 hours / month
    • Priority response (< 24h on weekdays)
    Best forFunded startups (seed to Series B) with a roadmap that needs a consistent design hand — and a founder who values speed over RFP processes.

Full pricing breakdown, side-by-side comparison, and add-ons live on the pricing page.

Crypto-adjacent work.

See all case studies
10+
Products Shipped
4+ Years
UI/UX Experience
5
Industries Designed For
4+
Countries Served
Services

What else I design.

Crypto-specific questions.

  • Enough to design for them. I can read Solidity at a "what does this function do" level, work with engineering to surface contract states in UI, and design for ERC-20 / ERC-721 / ERC-1155 patterns. I'm not a smart-contract auditor — pair me with one for the contract design.

  • Very different. Custodial = treat it like a fintech app (account recovery via email, customer support). Non-custodial = the user IS the bank — every UX decision multiplied by 10x because there's no support to bail them out. I've shipped both.

  • I design for the user who is two months into crypto, not the user with a Ledger on their desk. That means defaults that hide chain selection, plain-language gas copy ("this transaction will cost roughly $X to send"), and a review sheet before any signature. Send flows get chunked into single-decision screens — not because the all-on-one-screen layout doesn't fit, but because money flows read badly under stress.

  • Common pattern. The trick is hiding the Web3 layer from users who don't care (sign-in with email, paymaster covers gas) while exposing it to power users who do. I've designed dual-mode UX where the same screen serves both audiences.

  • Some patterns transfer from gallery-style ecommerce — see Painted Juttay, where every product is one-of-one and the IA had to read as a small gallery rather than a generic grid. I haven't shipped a full NFT marketplace end-to-end, so I'll be upfront on scoping if it's a stretch.

  • A focused redesign of a single flow (recovery, onboarding, send) is 2-3 weeks. End-to-end wallet design (everything from onboarding to settings) is 6-10 weeks. I scope per-project after the discovery call.

How it works

Four steps to shipped.

  1. Discovery call

    30-min free call. We figure out if we're a fit and what the engagement looks like.

  2. Fixed-scope proposal

    Within 48h, you get a written scope with timeline and price. No hourly billing.

  3. Kickoff + 6-phase build

    Research → Wireframes → Visual → Test → Handoff. Weekly Loom, async Figma.

  4. Handoff + 2 weeks Q&A

    Dev specs, animation specs, 2 weeks in your engineering Slack.

Related

Also explore.

Available now · 1 slot open

Got a crypto thing to ship?

Or email me
Based in
Karachi, PakistanUTC+5