---
# System prepended metadata

title: Swingby UI/UX Quick Wins
tags: [' ux', swingby]

---

---
title: Swingby UI/UX Quick Wins 
tags: swingby, ux
---
# Swingby UI/UX Quick Wins

## 1. Swingby Network 

### 1.1 Beta Message - Current UI is intrusive and erodes trust in user before proceeding with swap
**Current**
![](https://i.imgur.com/TI7VFmP.png)

**Proposed**
* Remove the yellow pop up 
* Replace "Stake your BTC..." with beta message "Product is in Beta. Use at your own risk"
    > Rationale: We should only give user 1 Call to Action at the right time. If this flow's primary objective is to help the user swap, let's focus on that. The staking can be introduced another time

![](https://i.imgur.com/mp6Mktl.png)


### 1.2 The double direction arrow - Make it clickable (common standard across DeFi apps)
 
**Current**
WHEN users click on the double direction arrow icon (between BTC & WBTC fields) 
THEN nothing happens

**Proposed**
WHEN users click on the double direction arrow icon (between BTC & WBTC fields)
THEN the BTC and WBTC fields should be swapped 

> Rationale: This is pretty standard UX expectations in DeFi. Should reduce bounce rate and increase number of successful swaps 


## 2. SkyBridge Explorer & farm.swingby.network 

### 2.1 Standardise Header CTAs across both websites 

**Current**
![](https://i.imgur.com/iBOOZsg.png)
![](https://i.imgur.com/etRU0qB.png)

**Proposed**
* Move all CTAs to the left 
* Rename CTAs to "Liquidity" (previously `Stake BTC`), "Farm" (previously `Yield Farming`) and "Metanodes"
* Keep language selector & dark/light mode toggle on the right
* On all Skybridge Explorer AND farm.swingbynetwork, the header should display the same CTAs 

![](https://i.imgur.com/R61HQmm.png)

### 2.2 Beta Message - Current UI is intrusive and erodes trust in user before proceeding with swap
**Current**
![](https://i.imgur.com/etRU0qB.png)

**Proposed**
* Remove the yellow pop up 
* Replace "Stake your BTC..." with beta message "Product is in Beta. Use at your own risk"

> Rationale: We should only give user 1 Call to Action at the right time. If this flow's primary objective is to help the user swap, let's focus on that. The staking can be introduced another time
![](https://i.imgur.com/nDcLhTA.png)


