Designing a Best-in-Class Swap Feature for Leap Wallet

Redesigned Leap Wallet's token swapping for mobile, extension, and web dashboard into a seamless, transparent experience driving in-app swaps post-launch, reducing first-time user drop-off, and sparking the adoption of Leap's Swap SDK by partners across the Cosmos ecosystem.

My Role

Product Designer, UI/UX Designer

Led research, end-to-end UX for swaps, and SDK design coordination

Team

Aditya
Khush

Timeline

4 Months

Skills

User Research

Product Strategy
Problem Solving

Visual Design

The Challenge

A Fragmented Journey

Swapping tokens in Cosmos wallets was fragmented and intimidating.

Confusing
flows

Users had to navigate multiple dApps, causing drop-offs and costly mistakes.

Unclear
fees

Hidden costs eroded trust and led to high support ticket volumes.

Fragmented
UX

No visibility into swap progress; transactions felt like tokens had “disappeared.

Diverse
segments

Beginners were overwhelmed by jargon, while power users demanded speed and advanced features.

The lack of an integrated, trustworthy swap solution directly hurt Leap’s user retention, engagement, and ecosystem credibility.

Impact highlights

The redesign directly addressed these user frustrations, leading to measurable improvements in user success, trust, and ecosystem-wide adoption.

Reduced Drop-off to <10%

The simplified and transparent flow dramatically improved the swap completion rate, ensuring new users could transact successfully and confidently.

10+ SDK Adoptions

The consumer-facing UX was so successful it was packaged into an SDK and adopted by over 10 other wallets, making my design the new benchmark in the Cosmos ecosystem.

Decreased Support Load

By clarifying fees and improving error handling, we saw a major reduction in support tickets related to swap confusion and failed transactions.

Research foundation
Validation
Usability testing (5 participants)

Confirmed clarity improvements; feedback led to explicit network labels and a step-by-step progress tracker.

A/B testing

“Review Swap” CTA outperformed “Swap Now” in perceived safety.

Launch telemetry

Validated adoption, reduced support tickets, and increased retention.

Solution overview

Simplifying Swaps, Building Trust

I reframed the challenge from "add a swap feature" to "make swapping feel as simple as sending a message and as trustworthy as online banking." My solution was built on three key interventions, designed and tested to address the core user frustrations:

Iteration & Refinements

Safety Alerts

Implemented real-time warnings for high price impact trades

Added slippage tolerance alerts based on security team's thresholds

Transformed UI into active protection, not just a passive interface

Error Prevention

Blocked same-token swaps with clear explanations

Added network mismatch detection and correction prompts

Collaborated with engineers to surface alerts at critical moments

Transaction Feedback

Created step-by-step progress indicators with checkmarks

Provided clear success/failure messages with next steps

Reduced user anxiety and prevented panic-driven multiple attempts

Network clarity

Early testers confused chain vs. token swaps. Dropdowns were updated with explicit network labels (e.g., “JUNO (Cosmos Hub)” vs. “JUNO (Juno Network)”).

Progress feedback

Users thought swaps were instant; subtle loaders were replaced with a clear 3-step progress tracker (sending confirmation complete).

Content design

CTAs iterated from “Swap Now” “Confirm Swap,” improving user confidence.

Error handling

Swaps failures reframed with plain-language guidance (e.g., “Your tokens are safe try again later”).

Implementation & Handoff
Detailed specs

Delivered redlines, interactive prototypes, and annotated Figma files for all 3 platforms.

Design/engineering syncs

Daily stand-ups + twice-weekly reviews ensured fidelity and quick pivots around constraints.

Design Audits and QA

Stress-tested swaps with varied tokens, amounts, and connection speeds before launch.

Edge Cases
Liquidity failures

Clear error states guided retries without user anxiety.

Slow networks

Visual feedback prevented users from assuming tokens were lost.

Uncommon flows

Guardrails for retry attempts, abandoned swaps, and same-token selections.

Learnings
Strategy before pixels

Framing the challenge around *trust and simplicity* aligned stakeholders and guided design trade-offs.

Inclusive design

One interface, adaptive for both beginners and advanced users, avoided fragmenting the experience.

Security as UX

Built-in safeguards reassured users and reduced panic-driven retries.

Collaboration mattered

Continuous alignment with PMs and engineers ensured feasibility and polish.