Redesign Unsupported Assets UX
Open
Nobody has claimed this yet.
design
improvement
p2
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Current Behavior
- when you search (by name or address) for an unsupported asset like mTSLA, it appears in search results and is clickable (import)
- you can click on it and it populates in the swap box
- the swap button is disabled reading "Unsupported asset"
- below that is a card that says "read more about unsupported assets"
We should improve this UX by surfacing the 'unsupported' message much earlier in the flow.
Proposed Behavior
- when you search (by name or address) for an unsupported asset like mTSLA, it should appear in the search results as a disabled entry. It should not have an import button.
- it should be labeled 'unsupported'
- clicking on the unsupported token should open the unsupported modal (below)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the asset search flow that handles name or address results, then inspect how unsupported assets currently expose the import action and open the unsupported-assets modal. Done means unsupported assets appear disabled, are labeled “unsupported,” have no import button, and clicking one opens the modal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100