Skip to content

[Bug]: Swaps A/B testing reduced interactions #28050

@Prithpal-Sooriya

Description

@Prithpal-Sooriya

Describe the bug

Jira Ticket: https://consensyssoftware.atlassian.net/browse/ASSETS-2972

Overview

Improve the Swap entry experience from Token Detail Page by introducing balance-aware default token selection.

Currently, users navigating to Swap from a token with zero balance are pre-filled with that token as the “from” asset, requiring manual correction before proceeding.

This creates friction and increases time to complete swaps.

Problem

When a user opens Swap from a token they do not hold:

  • “From” token is pre-filled incorrectly

  • User must manually change token before proceeding

  • Swap flow becomes slower and less intuitive

This contradicts expected behavior - Users expect to act immediately after tapping Swap

Hypothesis

If Swap defaults are balance-aware, then:

  • Time to complete swap will decrease

  • Swap success rate will increase

  • User frustration will decrease

Proposed Solution (Phase 1 – MVP)

When user navigates to Swap:

Case 1 — User HAS balance

From = current token
To = default (e.g. mUSD or last used)

Case 2 — User has NO balance

From = best available token (user balance)
To = current token

“Best Available Token” Selection Logic

Priority:

  1. Same chain token with the highest balance

  2. Native token (ETH, POL, etc.)

  3. Last swapped token

  4. Most used token

Success Metrics

Primary:

↓ time to complete swap

↑ swap completion rate

Secondary:

↓ manual token changes

↑ conversion from token page

Jira issue

Expected behavior

No response

Screenshots/Recordings

No response

Steps to reproduce

No response

Error messages or log output

No response

Where was this bug found?

No response

Version

No response

Build number

No response

Build type

No response

Device

No response

Operating system

No response

Additional context

No response

Severity

Sev1

Metadata

Metadata

Assignees

No one assigned

    Labels

    RCA-neededIssue root cause analysis neededSev1-highAn issue that may have caused fund loss or access to wallet in the past & may still be ongoingregression-RC-7.72.0Regression bug that was found in release candidate (RC) for release 7.72.0release-blockerThis bug is blocking the next releaseteam-assetsteam-mctpLabel to test synchronization of Github issues to Jira issues and vice versatype-bugSomething isn't working

    Type

    No fields configured for Bug.

    Projects

    Status
    To be triaged

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions