Blocto Wallet’s native staking, rebuilt from a web page into part of the wallet. Support tickets fell 82%.
Lead Product Designer
Web-to-native revamp
82% fewer support tickets
Blocto was the largest wallet on Flow, and staking was one of the things its users wanted most. The first version shipped fast: a web page wrapped inside the app. It worked, but for most people staking was unfamiliar to begin with, and the page put all of Flow’s machinery on screen with nowhere to start.
The old page showed
everything at once.
Enough to confuse anyone.
Problem · Users kept asking
These weren’t edge cases. The page made staking feel hard to use, and with money on the line, that’s enough to make people hold back.
The old page · 2022
The new one shows only
what’s true right now.
Approach
Three principles shaped every screen.
Show lessReveal only the state the user is in, and the one action that fits it.
Speak humanSwap the protocol jargon for plain words, and let the timing show.
Reward the waitGive the payout a moment worth waiting for.
01
The page leads with the token and its APY, so the reason to stake is clear up front. Stake only appears once there’s a balance behind it.
02
Timing trips people up, since a stake only goes live next epoch. So we made the epoch a readable bar, with the next start time right beside it.
03
Dressed as a treasure chest, the reward feels like a prize you’ve earned. Auto-restake then rolls it into the next stake, the habit we were designing for.
Takeaways
Native staking shipped on Flow. What the redesign changed: