Challenge
Managing money gets far more complex when fiat and crypto live in the same product — different balances, currencies, methods, networks, fees, processing times, and transaction states.
Case Study
Mobile App · Fintech · Fiat & Crypto
Multi-Currency Financial App
Making fiat and crypto easier to manage in one place.
An end-to-end mobile financial experience that enables users to manage balances, deposit, withdraw, and convert across fiat and cryptocurrencies through one clear and consistent experience.
Project Snapshot
Solution
A unified mobile experience built around four core actions — manage, deposit, withdraw, convert — where the interaction model stays familiar and asset-specific detail appears only when it matters.
Responsibilities
- Product strategy
- UX/UI design
- Interaction design
- Design system
Outcome
Complex financial actions came together in one consistent framework, making it easier to move between fiat and crypto without learning a new pattern for every transaction type.
Context
Bringing fiat and crypto into one experience
Managing money becomes significantly more complex when fiat and cryptocurrencies exist within the same product. Users need to understand different balances, currencies, transaction methods, networks, fees, processing times, and transaction states — while still performing everyday financial actions confidently.
The product was designed as a unified mobile experience where users could manage both fiat and crypto assets, deposit and withdraw funds, convert currencies, and track transactions without navigating separate financial experiences. My role was to shape the end-to-end product experience and establish interaction patterns that could work consistently across currencies and transaction types.
Approach
One mental model, multiple financial rails
Rather than designing each transaction type in isolation, I built the experience around four core actions — manage, deposit, withdraw, and convert — sharing a single interaction model: choose an action and currency, provide details, review, confirm, and track.
The interface stays consistent where possible and different only where necessary, surfacing asset-specific requirements like networks, wallet addresses, and bank details when relevant, and always making amounts, rates, and fees clear before anything is confirmed.
Outcome
A coherent foundation for fiat and crypto
The result brought complex financial actions into one consistent framework, making it easier to move between fiat and crypto without learning a different pattern for every transaction — and established reusable components that can support more currencies and capabilities as the product evolves.
Project Context
A unified mobile financial app where users manage both fiat and crypto assets — deposit, withdraw, convert, and track transactions — without switching between separate financial experiences.
Why this project mattered
Getting the shared model right meant users could move between fiat and crypto confidently, and the product could grow to support new currencies and capabilities without redesigning every flow.
Who it's for
People who hold both fiat and cryptocurrencies and want to handle everyday financial actions in one place, without relearning the product each time they switch between currencies.
Business goals
- Unify fiat and crypto management in one product
- Reduce failed and abandoned transactions
- Establish reusable, consistent transaction patterns
- Create a scalable foundation for more currencies and features
Market context
Most products treated fiat and crypto separately — crypto-first tools felt technical, while fiat finance apps offered little crypto support. Few brought both into one coherent set of everyday financial actions.
Problem Statement
How might we make managing fiat and crypto feel like one coherent financial experience without hiding the important differences between them?
01
User Problems
- Fiat and crypto balances are hard to understand together
- Deposits and withdrawals require different details depending on the asset
- Networks, addresses, fees, and processing times are easy to get wrong
- Transaction status is often unclear after confirming
02
Business Problems
- Fiat and crypto handled as separate experiences
- Transactions abandoned when requirements felt unclear
- Support load from transaction-status questions
- Hard to scale to new currencies and methods
03
Technical Constraints
- Fiat and crypto transactions behave differently
- Crypto requires network selection and wallet addresses
- Fiat requires bank information and payment instructions
- Fees and processing times vary by asset and method
04
Product Constraints
- One consistent model across fiat and crypto
- Asset-specific detail must remain available when relevant
- Mobile-first experience
- Support multiple currencies and transaction types
Goals
01
User Goals
- Understand total balance across multiple currenciesFiat and crypto balances visible from one home screen
- Deposit, withdraw, and convert with confidenceA clear review step before every transaction is confirmed
- Know the status of any transactionProcessing, completed, failed and pending states surfaced clearly
02
Business Goals
- Unify fiat and crypto in one productA single app replaces separate financial experiences
- Scale to new currencies and featuresReusable patterns extend without a redesign
03
Product Goals
- One mental model across transaction typesDeposit, withdraw and convert share a consistent flow
- Surface asset-specific detail only when relevantNetworks, wallet addresses and bank details appear in context
Success Metrics
One view
Balance clarity
fiat + crypto together
Review
Before every action
amounts, rates, fees
Always visible
Transaction states
processing → completed
Reusable
Currency framework
scales to new assets
Research & Discovery
Discovery focused on how people actually manage money across fiat and crypto — how they read balances, what they need before depositing or withdrawing, where the two mental models diverge, and how they interpret rates, fees, and transaction states. I paired stakeholder alignment with user conversations, a scan of comparable financial apps, and a review of the existing experience, then distilled everything into a few decisions that shaped the product.
01
Stakeholder Interviews
Conversations across product, compliance, and support centered on one question: how to bring fiat and crypto into a single app without making either feel foreign.
- Fiat and crypto had to live in one coherent experience
- Transaction clarity was the clearest driver of support volume
- Asset-specific detail could not be dropped, only sequenced
Users shouldn't need to learn a different app just because they're moving crypto instead of dollars.
The moment people can't tell what a transaction is doing, they contact us.
02
User Interviews
Sessions with people who hold both fiat and crypto showed they think in actions — deposit, withdraw, convert, track — not in financial infrastructure.
I just want to see everything I have in one place, then move it.
Before I confirm, I want to know exactly what I'm sending and what I'll get.
Actions
Users lead with deposit, withdraw, convert, and track — not the underlying rails
Familiarity
Consistent patterns reduced what users had to relearn between currencies
Context
Networks, addresses, and bank details still mattered when relevant
03
Competitive Analysis
I looked at how comparable financial and crypto apps handle multi-currency balances, transfers, and conversion.
Crypto-first walletsDeep on-chain capabilityFiat felt bolted on and technical
Fiat finance appsClear, familiar money actionsLittle or no crypto support
Exchange appsBroad asset coverageTransfers and conversion buried in complexity
Opening
Few products treated fiat and crypto as one coherent set of everyday financial actions.
04
Analytics
Reviewing the existing experience highlighted where multi-currency complexity created hesitation.
Balances
Hardest to interpret
Total value across fiat and crypto was difficult to read at a glance
Review
Most valued step
Users wanted rates, fees, and amounts confirmed before committing
Status
Biggest uncertainty
Unclear transaction states drove repeat checks and questions
05
User Journey Insights
Mapping the deposit, withdraw, and convert journeys showed where confidence dipped across currencies.
- 01Read balancesUsers needed one clear view of fiat and crypto together
- 02Choose an actionDeposit, withdraw, and convert felt comfortable when consistent
- 03Provide detailsNetworks, addresses, and bank details raised questions if unexplained
- 04Review & confirmA clear summary of amounts, rates, and fees restored confidence
- 05Track statusSilence after confirming read as failure
Key Research Findings
- 01Users think in actions, not financial infrastructure — the rails should surface only when they affect a decision
- 02Consistency across fiat and crypto reduces how much users must relearn when switching currencies
- 03Context still matters — networks, wallet addresses, bank details, fees, and processing times must appear when relevant
- 04Financial actions require confidence — users need to understand what they send, receive, pay, and where funds go before confirming
Design Strategy
The strategy was to build a consistent product framework around four core actions — manage, deposit, withdraw, and convert. The underlying requirements change depending on the asset, but the overall interaction model stays familiar: consistent where possible, different where necessary, and always clear before commitment.
01
Key Insights
- Manage — understand fiat and crypto balances from one placeA single home surfaces every balance alongside the primary actions
- Deposit — add funds whether the method is a bank transfer or a blockchain networkOne deposit journey adapts its details to the asset
- Withdraw — move funds to bank accounts or crypto walletsA familiar flow covers destination, amount, fees, and review
- Convert — exchange between currencies with clear rates and amountsConversion leads with what you send, what you receive, and the rate
02
Design Principles
Consistent where possible
Keep navigation, hierarchy, confirmation patterns, and transaction states familiar across currencies
Different where necessary
Surface asset-specific requirements — networks, wallet addresses, bank details, processing information — only when relevant
Clarity before commitment
Before any action is confirmed, communicate amounts, destinations, rates, fees, and expected outcomes
03
Prioritization Framework
Work was sequenced around the shared transaction framework — establishing the common pattern first, then layering the asset-specific requirements onto it.
NowShared transaction framework & balancesA consistent choose → provide details → review → confirm → track pattern underpins every action
NextAsset-specific deposit & withdrawal detailsNetworks, wallet addresses, and bank details introduced within the shared flow
LaterConversion refinements & transaction detailClearer rates and fees, plus richer status and transaction information
04
Success Criteria
- A user can manage fiat and crypto balances from one place
- Deposit, withdraw, and convert share one familiar interaction model
- Asset-specific requirements appear only when they affect the decision
- Every action is reviewable before it is confirmed
Design Process
Instead of designing fiat deposit, crypto deposit, fiat withdrawal, crypto withdrawal, and conversion as separate features, I looked for the shared structure between them. The common pattern — choose action, choose currency, provide transaction details, review, confirm, track status — became the backbone, with asset-specific information introduced only where required.
- Step 01
Discover
Studied how people manage fiat and crypto today and where the two mental models diverge.
- Talked to people who hold both fiat and crypto about how they move money
- Mapped how users read balances across currencies
- Noted where fiat and crypto expectations genuinely differed
- Reviewed the existing experience for points of hesitation
- Step 02
Define
Reframed the brief from 'add more financial features' to 'make fiat and crypto feel like one coherent experience.'
- Named the four core actions: manage, deposit, withdraw, convert
- Separated real asset differences from inherited complexity
- Set consistency across currencies as a primary goal
- Agreed where asset-specific detail had to remain visible
- Step 03
Ideate
Looked for one reusable transaction pattern that could serve every action.
- Sketched a shared choose → provide details → review → confirm → track flow
- Explored balance hierarchy and deposit/withdraw entry points
- Tested where network, address, and bank details should appear
- Weighed alternative navigation approaches
- Step 04
Prototype
Built the flows at rising fidelity so the shared framework could be felt across currencies.
- Wireframed deposit, withdraw, and convert on the shared pattern
- Designed review screens that summarize amounts, rates, and fees
- Created clear transaction status patterns
- Used realistic currencies, networks, and amounts
- Step 05
Test
Pressure-tested the framework where fiat and crypto requirements differ most.
- Walked users through deposits and withdrawals across assets
- Checked whether network and address steps felt clear
- Probed comprehension of conversion rates and fees
- Compared confidence before and after the review step
- Step 06
Iterate
Refined the moments of doubt and hardened the shared patterns for scale.
- Tightened review and confirmation copy
- Clarified transaction states and details
- Confirmed the pattern held as new currencies were added
- Documented reusable components for future work
User Flow
The product centers on four journeys from a single home — deposit, withdraw, convert, and activity. Each follows the same backbone: choose an action and currency, provide details, review, confirm, and track. The flow branches only where fiat and crypto genuinely differ, then rejoins the shared path.
Home / Balances
Choose Action
Choose Currency
Fiat or crypto?
Fiat
Bank Details
Crypto
Network & Address
Review → Confirm → Track
Key Decision Points
- 01
One home for every balance
Users start from a single view of fiat and crypto balances and enter deposit, withdraw, or convert from the same place.
- 02
Different where necessary
The flow branches only where assets genuinely differ — bank details for fiat, network and wallet address for crypto — then rejoins the shared path.
- 03
Clarity before commitment
Every journey converges on a review step that confirms amounts, rates, and fees before the action is confirmed and tracked in activity.
Final Solution
The shipped app brings fiat and crypto into one consistent framework. Five moments show how the shared model holds across managing balances, depositing, withdrawing, converting, and understanding what happened afterward.
01
One place for every balance
Design Objective
Give users a single starting point for understanding and managing their funds — total balance, individual currencies, fiat and crypto assets, the primary financial actions, and recent activity.
Key UX Decisions
Fiat and crypto balances sit in one view with All / Crypto / Fiat toggles, each currency shows its amount alongside an approximate value, and the primary actions stay reachable from a persistent bottom navigation.
Outcome
Users get one clear place to read what they hold across currencies before choosing to deposit, withdraw, or convert.
02
A consistent way to deposit
Design Objective
Keep the overall deposit journey familiar while the interface adapts to each asset — bank or payment method, account details and payment instructions for fiat; asset, network, wallet address, QR code and network warnings for crypto.
Key UX Decisions
One deposit flow underpins every asset. For crypto it surfaces the asset and network, the wallet address, a QR code, and a network warning; consistency does not mean making fiat and crypto identical — the framework stays familiar while asset-specific information appears when required.
Outcome
Users deposit with confidence across fiat and crypto because the right details show up in context without changing how the flow feels.
03
Withdrawing with confidence
Design Objective
Help users understand exactly where their funds are going and what will happen before they confirm — currency, destination, amount, available balance, fees, and the expected amount received.
Key UX Decisions
The review step leads with what's being sent and received, shows the network fee and the final recipient amount before confirmation rather than after, and keeps asset-specific detail — network and destination — visible so there are no surprises.
Outcome
The review step gives users an opportunity to verify important transaction information before any funds are moved to a bank account or crypto wallet.
04
Making conversion feel straightforward
Design Objective
Make the relationship between what users give and what they receive immediately understandable — the From currency and amount, and the To currency with its expected amount.
Key UX Decisions
Conversion leads with the From and To currencies and amounts, then a review surfaces the amount being converted, the amount received, and the estimated exchange rate before the action is confirmed.
Outcome
The hierarchy lets users quickly answer what they are converting, what they will receive, and at what rate — before they commit to the conversion.
05
Transparency after every transaction
Design Objective
Keep financial actions understandable after users tap Confirm, through an Activity view and transaction details that show what happened to their money after a deposit, withdrawal, or conversion.
Key UX Decisions
Activity groups transactions by date with Status, Type, Currency and Date filters, and each entry carries a state such as processing, completed, failed, or pending; opening a transaction reveals its details — type, currency, amount, status, date and time, fees, destination, and transaction or reference ID.
Outcome
Clear states and accessible detail give users visibility into every transaction across both fiat and crypto once it is underway or complete.
Design System
Creating consistency across complex financial journeys
A reusable component system helped maintain familiar interaction patterns across balances, deposits, withdrawals, conversions, and transaction states while allowing the interface to adapt to the requirements of different fiat and crypto assets.
Core colors
Accent#E96A11
Base#070707
Ink#1A1C21
Secondary#4D5464
Tertiary#858D9D
Positive#12B76A
Error#F04438
Surface#FFFFFF
Type scale — Inter
AgDisplay · 36 / 600
AgHeading · 30 / 600
AgTitle · 18 / 600
AgBody · 16 / 500
AgCaption · 14 / 400
Segmented control
Currency selector
Radio
Switch
Checkbox
SuccessAlertWarningInfoInfo
Home
Wallet
Trades
Activity
User
Send
Receive
Exchange
Swap
Download
Bank
Document
Copy
Scan
QR Code
Search
Notifications
Announce
Fingerprint
PrivacyResults & Impact
Rather than lean on invented metrics, the clearest outcome was structural: previously complex financial actions now share one consistent mobile framework, making it easier to move between fiat and crypto without relearning the product for every transaction type.
Business Outcomes
User Outcomes
- Unified fiat and crypto management from a single home
- A shared transaction pattern across deposit, withdraw, and convert
- Clear review and confirmation before any action
- Greater visibility into processing, completed, failed, and pending states
- 01Deciding where to be consistent and where to stay different mattered more than any single feature.
- 02A stable mental model let the interface flex to each asset's requirements without confusing users.
- 03Clarity before commitment — rates, fees, amounts — was the throughline across every transaction.
- Fiat & crypto managementSeparate flowsOne framework
- Transaction patternsPer-featureReusable across actions
- Pre-confirmation clarityInconsistentReview on every action
- Currency supportFixedExtensible foundation
Reflection
The hardest part wasn't designing individual financial features — it was deciding where fiat and crypto should behave the same and where their differences needed to stay visible.
- Building around four core actions gave fiat and crypto a shared, familiar structure.
- A reusable transaction pattern kept deposits, withdrawals, and conversions consistent.
- Review-before-confirm made complex actions feel safe across currencies.
- I'd further validate how users understand conversion rates and fees, especially first-time crypto users.
- I'd test comprehension of network-specific requirements earlier in the flow.
- I'd instrument transaction states to see where status confusion still occurs.
Challenges & Trade-offs
Consistency vs. difference
Fiat and crypto genuinely behave differently. The work was deciding where a shared pattern helped and where forcing sameness would hide something users needed — networks, addresses, bank details, fees, and processing times.
Simplifying without hiding
Abstracting technical detail risked obscuring things that affect real decisions. The trade-off was to keep asset-specific information available and surface it exactly when it mattered.
- 01Design around a stable user mental model, then let the interface respond to each transaction's requirements.
- 02Consistency reduces relearning; visible difference preserves trust.
- 03The review step is where confidence in a financial action is won or lost.
- Support for additional fiat and crypto currencies on the same framework.
- More transaction methods and richer activity filtering.
- Deeper transaction detail and proactive guidance before asset-specific steps.
