Home About Contact
Lisbon, Portugal
Case study · Payments

AppCoins Wallet

Designing the three seconds after someone spends real money.

RoleUX/UI Designer (end-to-end)
ScopeResearch · Flows · Wireframes · UI · Prototyping
ProductDigital wallet for payments and rewards
On Google Play ↗
AppCoins Wallet — home

The wallet home prioritises clarity and next actions, reducing cognitive load from the first interaction.

1M+
Installations on Google Play
430K
Active users
−32%
Drop-off during payments
The problem

Tap confirm. Screen loads. Did that just work?

That question — asked by a player, mid-game, seconds after spending real money — was the whole product problem. The transaction almost always went through. But the confirmation didn't show value, the reward appeared somewhere else later (or seemingly never), and the balance changed without explanation.

Unlike a B2B tool, there's no onboarding call and no second chance: a consumer who doubts one payment simply doesn't make another. The wallet ran on crypto rails, but that was irrelevant to users — what they were buying was certainty, and the interface wasn't selling it. Every ambiguous moment trained them to expect unreliability, even when everything worked.

Trust isn't built at registration. It's built at the first payment.
Onboarding

The onboarding sells what the wallet does for you. The word "blockchain" never appears.

Design decisions

Make the right actions obvious.

I wasn't trying to explain how the system works. I was trying to make the next step obvious and every state readable at a glance.

Hide the plumbing

Blockchain terminology removed from the primary flow entirely. Users see what they paid and what they got. How it was processed is my problem, not theirs.

Prioritise forward motion

Every screen designed for the next action, not to document the current state. Progress drives trust faster than explanation.

Reduce load at the payment moment

Payment screens stripped to essentials: amount, bonus, confirm. Fewer choices, faster decisions, less doubt.

Make every state legible

Loading, processing, success and failure each got distinct visuals with plain-language labels. Users stopped assuming the worst.

Consistent patterns everywhere

A shared component language across all integrated apps removed the "is this real?" moment when switching contexts.

Payment flow

Where trust is earned or lost.

Price, bonus, promo codes, rewards — the original experience put all of it in front of users at once and asked them to figure out the value themselves. They didn't. They hesitated. And hesitation became drop-off.

Trade-off: advanced controls were reduced in the primary flow. Power users could find them — but most users never needed them, and removing them lowered hesitation for everyone.
Result: users understand what they're committing to before they tap confirm. That single change accounts for most of the 32% drop-off reduction.
Payment screen 1
Payment screen 2
Payment screen 3
Rewards

Users earned rewards with every purchase. Most didn't know.

The rewards system existed — promo codes, campaigns, referral bonuses — but it had no center of gravity. Users found rewards by accident or not at all. We redesigned rewards as a progression model: one place, visible progress, clear stakes.

Decision: shift from scattered incentives to a loop that reinforces itself with every transaction. Rewards had to feel earned, not stumbled upon.
Result: users stopped reacting to promotions and started anticipating them. At that point retention does its own work.
Rewards hub

One hub, visible progress, clear stakes. People come back just to check on it.

Key insight

Users don't evaluate wallets. They evaluate moments.

The purchase confirmation screen isn't just a receipt — it's where trust is earned or lost. Design for that moment, and the whole system benefits.

Learnings

What this project taught me.

Clarity beats capability at the decision moment.

Users chose wallets they understood over wallets with more features. When the system communicated clearly, conversion followed.

The first payment defines the relationship.

First-time transactions had outsized influence on retention. A confident first experience set the pattern users repeated.

Removing options made the product better.

Stripping the flow to essentials felt like a sacrifice at the time. It wasn't. People moved faster, doubted less, came back more.

Next project
StoryPath →