Projects/

MELD (Fintech)

Product design · MELD · 2022 → 2024

MELD started as a non-⁠custodial crypto wallet and grew into a broader financial product, meant to bring on-⁠chain and traditional finance into one place. I was the product designer for its three surfaces, web, native mobile and browser extension, which were built at the same time. I also maintained the design system and mentored two junior designers.

Security that no longer blocks entry

Activation was low. Many people started creating a wallet and never finished. The heaviest task in the product, writing down the 24 word seed phrase and typing it back to verify it, came first, before they had seen anything the product could do. We asked for the most effort at the moment people had the least reason to give it.

Security check screen with two options: go directly to the wallet, or secure the seed phrase
The security check. Going straight to the wallet asks the user to tick an acknowledgement first.

Moving the seed phrase

The seed phrase is a blockchain standard, so removing it was not an option, but moving it was. I redesigned wallet creation around a choice: go straight to the wallet, or secure it now. To skip, the user ticks a box acknowledging that an unsaved seed phrase can mean losing the wallet, so taking the shortcut is a conscious decision.

Original flow: four steps before entering the wallet, the heaviest one first. Seedless flow: three steps and a choice.

Keeping security in view

Letting people in with an unsecured wallet is a real risk, and I did not want to hide it. Until the seed phrase was saved, a banner stayed across the top of the wallet asking for it. It could not be dismissed, and the only way to clear it was to finish the backup. Getting in became easier, and the request to secure the wallet stayed on screen until it was done.

The MELD wallet with a seed phrase banner across the top that cannot be dismissed
The banner stays across the top of the wallet until the seed phrase is saved. It has no close button.

70%

drop in onboarding drop-off

1 icon = 10%. White = gone

3k → 10k

daily active users, same period

+233%. 1 icon = 10%

Figures inferred from the analytics we had at the time.

One language for managing money

Fiat and crypto can look alike in a product, but they run on different rules. Bank transfers, token transfers, swaps and exchanges each bring their own networks, recipients, fees, timing and validation.

The principle was that people should not have to relearn the product every time the rail underneath changes. The interaction stays predictable, and complexity shows up only when it changes what the user needs to know or decide.

A rule for new features

As MELD grew, the principle became a way to judge new product decisions. When a new asset, transaction type or technical constraint came up, I started by asking what was really different about it and what could stay familiar, before drawing another flow. That gave me a concrete argument for consistency as the product expanded.

Exchange across four rails. Assets, fees, networks and execution rules differ, and the steps stay the same: amount, details, review.

Sending crypto and withdrawing fiat run on different infrastructure and follow the same order: amount, destination, review, confirm.

Gamification workshop

The workshop set out to define a game mechanic tied to the business goals of that period. We used Octalysis as a loose reference, and every proposal had to name the goal it served and the story it told the user.

Each participant got a fixed budget to spread across the ideas on the table. Nobody could fund everything, and explaining where the money went showed which mechanics mattered to whom. The ideas that kept their funding went to a vote. The result was a set of named badges, each tied to a concrete benefit, in place of a running points counter.

Under the badges we proposed a logarithmic progression instead of linear points. On a linear scale the most active users reach the top almost at once, and the scale has to be extended each time someone outgrows it. On a logarithmic curve the first actions move you up quickly and each tier asks for a multiple of the activity of the one before, so there is always a next tier within reach.

The curve set the pace. The actions it counted were weighted by the business goal they served, so climbing meant doing more of what the product needed. Once each single action counted for less, a badge with a real benefit at the next threshold gave the most active users a reason to keep going. The proposal was ready when the company closed, and it never shipped.

Workshop board with business goals, mechanics, prizes and storytelling notes, next to three tiers of badges with their rewards
The workshop board: goals, mechanics, prizes and story on the left, and the badge tiers that came out of it on the right.

Extras

Two and a half years of product work does not fit into ten stories. These are the pieces that carried real weight without getting a section of their own.

  • Streamlined the KYC flow alongside wallet creation.
  • Standardised swap, exchange and transaction patterns across crypto and fiat.
  • Defined clear and consistent asset nomenclature across the product.
  • Standardised transaction receipts and a shared transaction detail model, so different asset types and outcomes read through one structure.
  • Designed the promotional surfaces for premium benefits.
  • Defined a mobile specific visual style, detached from the web app while staying aligned with the brand.
  • Maintained the design system across three surfaces and two build environments.
  • Mentored two junior designers.
  • Analysed blockchain flows end to end, from input to output, identifying error checkpoints and keeping them legible to developers.
  • Oversaw branding and web side projects, including the bridge and the node operator platform.

Where it ended

The native mobile app was finished and released to early beta users before the company closed. Their feedback was positive and went straight back into the interaction work.

What I took from it is that security and friction are easy to confuse. The seed phrase had to exist, but where it sat in the experience was a design decision. Most of the activation problem came from the distance between what really needed protecting and what we had assumed had to come first.