App Redesignfor Mercuryo

Unified visual language for a family of crypto apps, created and preference tested on existing and new users
12M
users on the platform
12→22%
conversion, year over year

Role: Head of Product Design

Mercuryo's app had drifted from the company it belonged to. The marketing site had just been refreshed and everyone loved it; the product told a different story — most marketing assets showed the web service, functional and plain, a world away from the brand it was meant to sell.

An earlier redesign had stalled. The CPO handed me the mandate: realign the product with the brand, and ship it this time. The work ran on three fronts at once.

On Ramp

Let us walk you through the tool that engages users like nothing else

App redesign

Better usability, with the product team

The app rests on one structural idea: float the things that matter. The deal — amount, rate and fees — and the primary action sit in a panel the screen scrolls under, so what the user is agreeing to never leaves the view. The profile floats the same way, and modals built for the web read as native.

In parallel with the visual work — and together with the product managers — we used the redesign to push usability: simplifying the user flow, cutting steps, and tilting the product a little more toward UX. Each change below lowers cognitive load and shortens the path to a successful transaction.

Over the year this work ran, conversion to purchase went from 12% to 22%.

Float the things that matter

Payment details and the primary action live in a floating panel. It expands in place, and the screen scrolls under it.

A floating action bar

The amount and the primary button live in a bar that never leaves the screen — keeping the user in context even across several payment-setup steps.

The method that last worked is already chosen

The list opens only to change it — or after a failure.

The method that last worked is already chosen

The list opens only to change it — or after a failure.

A decline with a way out

The charge fails where the method was chosen, the reason is written under it, and the list opens with a method that works.

A decline with a way out

The charge fails where the method was chosen, the reason is written under it, and the list opens with a method that works.

Screen flow

The app originally shipped light-only. The system now carries a second layer of tokens, so the dark theme is a mode away — same components, same rules.

WalletComplete paymentPayment methodsOrder completePayment detailEdit card
WalletComplete paymentPayment methodsOrder completePayment detailEdit card

The long story: a new visual language

The visual language is the part of this redesign with the longest run-up: it had to be argued, tested and chosen by users before anything could ship. The rest of this case is that story.

A product's interface is a brand asset: it rides on almost every banner and deck, so a screen that drifts from the brand undermines the marketing it anchors.

UI as a key brand asset

How far had the product drifted? Far enough that marketing stopped showing it. When a campaign needed the product on screen, the marketing designer drew a conceptual mock-up — an idealised, on-brand product that existed only in the artwork. The real interface had become a liability the brand worked around, and that was the signal to change it fast.

Visual language — let the users decide

Taste in a design review is loud and unreliable, so we settled the direction with evidence: two rounds of preference testing, around three hundred participants each. We asked what matters for a crypto wallet — which feels clearest, which feels most modern, which reads as a crypto product.

The first round compared four directions; the winner went into a second round against fresh iterations and won again — a stable preference across roughly six hundred people.

One of the four directions in the first round was the product's existing native interface, and every new candidate beat it. That was our clearest signal that the redesign moved the visual language decisively forward.

★ Winner

Clean, modern, trustworthy

Strong Positive · rated 4.0 / 5 · won on clarity

4.0 / 5
“Feels like a classical wallet — I’d trust it with money. The abstract art was pretty but got in the way.”

Vibrant & eye-catching, but busy

Mixed Positive · rated 3.7 / 5

3.7 / 5

Familiar, but uninspired

Neutral · rated 3.5 / 5 — the existing design

3.5 / 5

Artistic, yet confusing

Polarized · rated 3.1 / 5

3.1 / 5

How we proved the direction

~300
participants per round
2
rounds — winner stable across both
3
axes tested

We shipped the variant that performed. Several of us preferred other directions; the users chose this one.

One system, every partner

The same payment flow, restyled to each partner's identity — Mercuryo's violet, Trust Wallet's green, Bybit's gold. Tokens swap, the structure holds: one design system that bends to partner needs.

WalletComplete paymentPayment methods
AmountPayment methodsComplete payment
ExplorePayment methodsComplete payment

A visual language earns its place by being preferred, by shipping, and by turning many languages into one. This one did.

What's the right metric for a visual language?

A visual language has no revenue number. Its honest measures are three.

Preference: do users prefer it, and does it read as the right kind of product? Two tests answered yes.

Shippability: does it reach users? The earlier attempt stalled; this one shipped incrementally, alongside the roadmap.

Coherence: did it reduce the chaos? Many drifting systems became one.

Those are the numbers I'll stand behind.

From a winning concept to a design system

Once stakeholders signed off, I ported the winning dark concept into a light theme — matching every colour by hand — and brought in a second product designer to detail the system against real screens.

The detailing hardened into a UI kit, and the kit into a full design system: the durable artifact the whole product keeps building on.

In progress...

Shipped in parallel with the roadmap

What made this attempt ship comes down to how it reached production. I ran the visual language in parallel with the product roadmap, applying the emerging concepts to real features as I built them.

By the time the language was chosen — a strategic decision — the key screens were already assembled on the new components and handed to engineering. The language arrived de-risked: proven on real screens and real use cases, riding along with product work.

Mercuryo is now implementing the visual language across its products — the first results are live on my.mercuryo.io. Feel free to try it. Hope you like the style.

Kudos to Dmitry Melov & Aydar Shakirov for their contribution.