Floki Launchpad

The original investment flow was a mess of 7 steps: connect wallet, find the asset, open the page, click invest, get redirected to a separate transaction page, fill out details, and finally confirm.

Advanced investors were losing valuable seconds during frantic launch windows, while new users kept landing on a standalone checkout page with no context on what they were buying.

Every competitor we looked at made the same mistake, splitting their experience into separate tracks for beginners and pros that didn't work well for either.

I proposed shortening the whole flow to 3 steps: connect wallet, pick an asset, and buy. The purchase action would live right on the asset page instead of taking users to a separate transaction screen. That proposal was where we hit our main design disagreement.

Our design lead came from a traditional fintech background, so her instinct was to keep the transaction on a separate page. That's a classic Web2 pattern meant to add weight to financial actions and prevent user error.

I pushed back based on two clear research insights. First, advanced Web3 traders need maximum execution speed during launch windows, where seconds directly impact price. Second, new users actually get better context when the purchase form sits right next to the asset info, instead of being isolated on a blank checkout page.

We debated it for a few days, so we brought in a third designer to review both options independently. They agreed with the single-page approach, the lead signed off, and we shipped it to production.

I turned the staking concept into an explicit UX pattern, building a tier leaderboard so users can see exactly where they rank against everyone else staking FLOKI. The traditional Web2 move would be hiding that complexity behind collapsible menus or progressive disclosure. In Web3 though, hiding how the mechanics work just makes people suspicious, so we put the tier competition right out in the open.