I owned this product end to end
As the Product Designer leading this project, I was responsible for taking the product from early definition through to development. I worked within a wider team of four Product Designers and a Head of Design, but owned this product independently, bringing in other designers when additional support was needed.
Strategy & UX
- Product and UX direction
- Information architecture
- Core user journeys and flows
Research & testing
- Research and usability testing
- Wireframing and prototyping
Design & systems
- High-fidelity UI
- Design system development
- iOS and Android design
Delivery
- Documentation and developer handoff
- Ongoing collaboration with engineering
Working with engineering
I worked closely with developers throughout, providing approved flows, production-ready assets and documentation, maintaining designs in Zeplin and answering questions during implementation. The collaboration didn't stop at handoff: I stayed involved during development to clarify interactions, resolve design questions and adapt solutions to technical constraints.
A new product, designed while the MVP was live
The company already had a live crypto payment MVP. In parallel, I led the design of its next-generation replacement from the ground up, rethinking the experience, expanding the feature set and building a scalable design system for iOS and Android.
The new product progressed through design and into ~90% of development before the project was paused when the company later entered administration.
Business context: the business wanted to evolve the MVP into a more complete payment product that could support a broader set of everyday financial journeys and scale alongside the company's trading platform.
Crypto payments feel fragmented and technical. Users worry about security, mix up wallets, exchanges and payment tools, and feel overwhelmed by complexity.
A trust-first experience that is simple for newcomers and still gives experienced users control: send, receive, pay, wallet, filterable history, KYC, SSO and an admin panel.
Two user mindsets, one need: control without complexity
Interviews and a focus group with existing users showed the same pattern: security concerns, confusion between products, and fatigue with complex platforms.
Sarah, 27 · Freelance designer
Works with international clients. Wants fast, low-fee cross-border payments she can trust and track.
“I want crypto payments to feel as simple as sending money through any modern banking app.”
John, 45 · Small business owner
Cautious about volatility and security. Wants predictable flows and jargon-free guidance.
“I'm open to innovation, but only if it feels secure, reliable, and easy to understand.”
Competitors are powerful, but complex
I compared Binance, Kraken, Crypto.com and Coinbase. Many suffer from complex flows, unclear terminology and feature-heavy interfaces: the gap this product was designed for.
| UX dimension | Common challenge across the platforms | Question for our product |
|---|---|---|
| Navigation and flow complexity | Complex flows made common actions harder to reach | How few steps can core payments take? |
| Terminology clarity | Unclear terms around wallets, exchanges and transfers | Which terms must be explicit? |
| Feature density | Feature-heavy interfaces gave every capability similar weight | What deserves priority? |
| Accessibility for newer users | Powerful for experts, but overwhelming for less experienced users | How do we support newcomers without limiting experts? |
| Clarity of financial actions | Balances, destinations and statuses were hard to read at a glance | How do we make every action unambiguous? |
Qualitative review of Binance, Kraken, Crypto.com and Coinbase: patterns across the platforms, not scores.
What I took forward
Simplify core journeys
Prioritise common actions rather than exposing every feature equally.
Make terminology explicit
Don't assume users understand wallets, exchanges and transfers.
Design for trust
Make balances, destinations and transaction states unambiguous.
From structure to high-fidelity
I turned the requirements into a simple, banking-inspired information architecture, iterated on low-fi wireframes, then built an atomic design system following Material Design for Android and Human Interface Guidelines for iOS.
Sketches and low-fidelity wireframes. Validated core flows before investing in visual design.
What users taught us
I ran moderated usability sessions using the interactive prototype, focusing on payments, balances, transfers and other core journeys. Participants were able to complete the main tasks without major barriers, while testing exposed two terminology issues that could undermine confidence in a financial product.
10 participants · 5–6 core tasks each
Balance was unclear
Users weren't sure whether the balance showed crypto holdings or the fiat-equivalent value.
The label now states exactly what the number represents.
Send vs Transfer overlapped
Users confused sending funds externally with moving assets between the app and the exchange.
Clear destination wording plus a visual cue removes the overlap.
Supporting evidence: usability test sheets.
From MVP to a product nearly ready for launch
I led the redesign from early product definition through to approximately 90% of development, covering the information architecture, core journeys, UX, UI, design system, usability testing and engineering delivery.
Testing validated the core journeys and helped us resolve important terminology issues around balances and transfers before launch.
The project was ultimately paused before release when the company later entered administration, so there is no post-launch product or business data to report.
In financial products, good UX isn't only about making an interaction easy. It's about giving users enough clarity and feedback to feel certain they're making the right decision.