Guadalupe Miró

Ripio

Crypto's biggest problem was never the technology. It was trust.

Role
Lead Product Designer
Timeline
Oct 2018 – Mar 2019
Team
Me (lead), 1 Product Designer, 1 Project Manager
Tools
Sketch, InVision, Mural, Whimsical

Problem

Crypto could help Argentinians protect their savings, but nobody had made it easy to use or to trust.

What I did

Led design end to end for 6 months. Rebuilt the web wallet, onboarding, credits, catalog and marketplace, plus the UI kit behind them.

Outcome

Everything shipped.

Ripio dashboard and crypto catalog

01 — Overview

Overview

Project summary

Team

Me (lead), 1 Product Designer, 1 Project Manager

Duration

6 months

Deliverables

Discovery definitions, UX architecture, hi-fi prototypes, motion & illustrations

Project type

Product discovery · Product design

Applied methodologies

Competitive benchmarking, user & product discovery, user interviews, usability testing, low-fi & high-fi prototyping

This didn't start as a redesign. It started as a one-month discovery to prototype a small MVP. But discovery showed that a wallet disconnected from everything else wouldn't solve the real problem. Ripio needed a connected ecosystem, not just a better wallet. We made the case, Ripio agreed, and the project grew into rebuilding the entire web wallet: every transactional flow, onboarding and identity verification, credits, the crypto catalog and marketplace, and the UI kit it all ran on.

My role

I led the design end to end, from discovery to final UI. I ran the process, designed every flow in this case study, and facilitated workshops with Ripio's CEO to define the personas, prioritize the flows and make the key product decisions together.

02 — The Product

The Product

In Argentina, with constant inflation, crypto was a real way for ordinary people to protect their savings. But nobody was solving the obvious problem: most people had no idea how to use it. Digital wallets were still new, and people didn't trust them. The bar we set was simple: using Ripio should feel as familiar as using your home banking.

The problem wasn't a lack of features. Buying, selling, credits, services, exchange: it was all there. But nothing told people what to do first, each section worked on its own, and the whole experience assumed you already understood crypto. For the people Ripio wanted to reach, that was the real barrier. Not the technology, but trusting something they didn't understand.

Old Ripio web wallet — sidebar nav and Rapipago top-up flow

03 — Goals

Goals

Business goals

  • Gain new users
  • Innovate ahead of competitors
  • Increase loyalty of current users

Product goals

“Make Ripio the link between people and cryptocurrencies”

  • Democratize access to knowledge
  • Provide information in a targeted manner
  • Offer relevant functionality for each user segment

04 — Users

Users

Benchmark table and competitor UI comparison grid
Sticky-note research wall

We segmented users with Jobs to Be Done, crossing three parameters: motivation for money transactions, type of crypto transactions, and level of crypto knowledge.

JTBD survey screenshot

Proto-personas

Phase 01

Newbies

Get familiar with the product

Consumers

Perform daily actions

Financers

Make small investments

Phase 02

Curious

Be able to capture them

Business negotiators

Make great investments

Phase 03

Anarcho-Capitalist

Have autonomy

What we discovered

People shouldn't have to become crypto experts to reach their goals. Our job was to shorten the learning curve and lower the cognitive effort at every step.

The MVP focused on phase 1: Newbies, Consumers and Financers. The more expert profiles came in later phases. The self-rated knowledge question (low, intermediate, high) became part of onboarding, so the product could adapt to each level from the first session.

The personas also shaped the roadmap. Each part of the ecosystem was built for a different profile: buying and saving crypto for Newbies and Consumers, the core of the MVP. Credits for Financers, offering something many people couldn't get from a regular bank. And the marketplace for the niche that already used crypto wallets, like the Curious and the Anarcho-capitalists. That's why the marketplace came later. It mattered, but it wasn't the main focus.

Full persona sticky-note board

05 — Process / Discovery

Process / Discovery

We started with an audit of the wallet and community, looking at primary actions, onboarding, cross-device navigation and architecture. We also benchmarked competitors like Xapo, which targeted specific products at specific segments and translated familiar money habits into digital ones.

We rebuilt the information architecture from scratch, mapping every section for users with and without an account, so the product logic was clear before any screen was drawn.

Hand-drawn onboarding sketch
Hand-drawn onboarding sketchHand-drawn onboarding sketch

From there we sketched the key screens by hand, moved to lo-fi wireframes to test the flows, and only then went to high fidelity.

What testing showed

People didn't know how to load crypto, where to load it from, or even why they would. The new flows answer those three questions up front, and when we tested them with users, they found them clearly easier to use.

Three principles

  • Integral: every Ripio product in one place, organically and with sense.
  • Flexible: a modular design system that adapts to different platforms and products.
  • Scalable: a permeable structure that lets the product grow at different levels.

06 — What We Built

What We Built

Existing → redesigned

Site navigation

Architecture and sitemap rework for logged in/out users.

Existing → redesigned

Login / Signup / Validation

New UX for higher conversion.

Existing → redesigned

Wallet

Complete core refactor.

New

Dashboard

Portal to the crypto world.

New

Crypto catalog

Discovery section per currency.

New

Crypto landing

Currency-specific landing pages.

Existing → redesigned

Ripio credit redesign

New request-and-manage flow.

New

Marketplace / Discovery

Buy/sell collectibles in pesos.

08 — Design System

Design System

Everything above ran on the same system.

The UI kit covered primary and alternative CTAs with all their states, inputs with icon-based validation (active, typing, error, complete, disabled), a type scale for desktop and mobile, and a palette anchored in Ripio's purple.

With this many flows redesigned in parallel, consistency couldn't depend on memory. We defined the base components and their states first, so every new screen was built from the same parts.

Component and UI kit sheet

09 — Reflection / Outcome

Reflection / Outcome

Outcome. Everything shipped: the new dashboard, wallet, onboarding and validation, credits, crypto catalog and marketplace.

What I'd do differently

Measure. I handed the project off at launch, so I never saw how the new flows actually performed. Today I'd define success metrics from day one, like activation, validation completion and first purchase, and stay close enough to the launch to learn from them.

Let discovery change the brief. We were hired to prototype a small MVP. Discovery showed that wouldn't solve the real problem, so we made the case for a bigger scope. The most valuable thing I did on this project happened before any screen was designed.

Ripio didn't need another feature for crypto insiders. It needed to feel trustworthy to people who had never bought crypto. That was the bar for every screen I designed.

Ripio on a MacBook