May, 2023

From QA to UX Lead: Rebuilding a Crypto App from the Inside

INTRODUCTION

Designing a crypto remittance app for Central America — under pressure, without research support, and with full UX ownership.

In 2022, I joined a fintech project focused on enabling Bitcoin-based remittances from the U.S. to Central America — primarily Guatemala. It was a small, fast-moving startup building a mobile app that allowed users to buy, sell, convert, and send Bitcoin to local currencies.

Originally hired as a QA tester, I quickly became the sole product designer after the previous designer left. I took over a chaotic Figma file, redesigned the core flows, created a new visual language, and collaborated closely with two developers and a PO to ship key improvements.

The client didn’t want user research, user testing, or discovery. They wanted speed. So I adapted: conducting informal research on my own, working directly with stakeholders, and translating ambiguous requests into structured, testable UX solutions. It was scrappy, intense — and one of the most hands-on learning experiences I’ve had in product design.

⚠️ The name of the product and brand visuals have been anonymized due to client confidentiality.

THE CHALLENGE

Legacy design, missing context, and an impatient roadmap

When I took over the product, there was no clear documentation, no design system, and no research to work from. The app had outdated UI, unclear flows, and features stitched together without structure.

The client wasn’t interested in discovery or validation — just delivery. They wanted screens, fast. My challenge was to bring structure and usability without slowing things down.

This meant:

This meant:

 

  • Untangling a messy Figma file I inherited from the previous designer
  • Reverse-engineering flows like recharge, withdrawal, and crypto conversion
  • Creating a new visual language and style guide on the go
  • Translating stakeholder requests into UX solutions, often without full context

From this

To this

“This project threw me into the deep end — and that’s exactly where I learned to swim as a product designer.”

Wearing every hat: from QA to UX lead in weeks

I started this project as a QA tester — manually checking flows and logging bugs. But when the previous designer left, I was asked to step in. Since I already knew the product inside out, I became the sole UX designer.

From there, I led:

This meant:

 

  • Untangling a messy Figma file I inherited from the previous designer
  • Reverse-engineering flows like recharge, withdrawal, and crypto conversion
  • Creating a new visual language and style guide on the go
  • Translating stakeholder requests into UX solutions, often without full context

With no budget or time for user research, I adapted:

This meant:

 

  • Untangling a messy Figma file I inherited from the previous designer
  • Reverse-engineering flows like recharge, withdrawal, and crypto conversion
  • Creating a new visual language and style guide on the go
  • Translating stakeholder requests into UX solutions, often without full context

It wasn’t always smooth — the client prioritized speed over depth, and feedback was often vague. But that only made me more resourceful.

From busy to intuitive: simplifying the first touchpoint

The original UI was overloaded with competing elements — multiple balance displays, unclear hierarchy, and visual clutter that made core actions harder to spot. While the product offered powerful features, they were buried beneath inconsistent layouts and unnecessary friction.

before

after

In the redesign, I focused on:

 

  • Clarifying visual hierarchy: the balance is now legible and prioritized, with supporting info minimized.
  • Streamlining key actions: deposit, convert, and receive are front and center — no more guessing.
  • Reducing noise: the layout is simplified, white space is used intentionally, and language is more focused.

These small shifts made the homescreen feel more trustworthy and intuitive — especially for users new to crypto.

Designing the Recharge Flow: Turning Intent into Action

If the homescreen was the entry point, the recharge flow was the turning point.

This was the key moment where curiosity turned into commitment — when a user loaded money into their wallet and started their journey.

But the original experience made it hard to commit.

We saw drop-offs in early steps due to too many decisions upfront, unclear next steps, and an overload of information that created hesitation instead of confidence.

What we changed:

 

  • Linear storytelling with overlays: We broke down the recharge process into a series of clear, focused steps using overlay screens. Each one explained a single concept or action, guiding the user naturally through the flow.
  • Progressive disclosure: Instead of overwhelming users with forms and options all at once, we revealed only what was needed at each step — making it feel simpler and less risky.
  • Reassurance through clarity: We rewrote labels, added inline feedback, and removed optional distractions to make each screen feel obvious and safe — even for users new to crypto or banking apps.

 

 

We weren’t just redesigning screens — we were building trust into every tap.

This shift had a measurable impact: fewer drop-offs, faster completions, and a clearer path to conversion.

Bringing Clarity Across the Whole Money Journey

While the recharge flow was the most critical entry point, I also redesigned the key money movement flows across the app — including withdrawal, conversion, and auto-conversion.

Each of these followed the same design principles:

This meant:

 

  • Untangling a messy Figma file I inherited from the previous designer
  • Reverse-engineering flows like recharge, withdrawal, and crypto conversion
  • Creating a new visual language and style guide on the go
  • Translating stakeholder requests into UX solutions, often without full context

The goal was to make every interaction — from cashing out to converting currencies — feel easy, safe, and trustworthy.

When I joined the project, the product had just launched and was still figuring out how to meet users where they were — in a region where crypto adoption was rising, but financial literacy was still low.

Our goal wasn’t just usability. It was translation. We were translating:

This meant:

 

  • Untangling a messy Figma file I inherited from the previous designer
  • Reverse-engineering flows like recharge, withdrawal, and crypto conversion
  • Creating a new visual language and style guide on the go
  • Translating stakeholder requests into UX solutions, often without full context

The design needed to feel like a conversation — not a challenge. We used simple language, progressive steps, and clear visual cues to turn intimidating financial actions into approachable ones.

In a space that often feels overwhelming, we aimed to make crypto feel almost playful — like something you could understand with just a few taps. And for many users, that was the difference between bouncing… and buying in.

What I Learned

This project tested more than just my design skills — it challenged how I think about building products when the ideal conditions aren’t there.

Here’s what I took away:

  • Design isn’t always glamorous — but it still has to deliver. I stepped into a chaotic file, tight deadlines, and no formal research or analytics. Instead of waiting for perfect conditions, I created structure, simplified flows, and made sure users had a clear path through the product.
  • Lack of data isn’t an excuse — but a signal to be scrappy and resourceful. Ideally, we’d have had usage metrics, formal interviews, and time for deep exploration. We didn’t. So I observed patterns, mapped edge cases manually, and validated decisions through conversation, not dashboards.
  • Ownership is about stepping up, not being asked. I wasn’t originally hired as the UX designer — I was QA. But I knew the product inside out, so when the time came, I led the redesign, organized the design system, managed handoffs, and aligned the team around clearer flows.

This wasn’t a textbook case study. It taught me how to move fast, stay clear, and take ownership even in the messiest moments.

🧰 Tools Used

  • Figma – UI design, prototyping, style guide creation
  • Flutter – Understanding interface structure and developer handoff
  • Miro – Mapping flows and internal logic
  • Notion – Documenting decisions and collaborating with the team

Let’s work together

May, 2023

From QA to UX Lead: Rebuilding a Crypto App from the Inside

INTRODUCTION

Designing a crypto remittance app for Central America — under pressure, without research support, and with full UX ownership.

Designing a crypto remittance app for Central America — under pressure, without research support, and with full UX ownership.

 

In 2022, I joined a fintech project focused on enabling Bitcoin-based remittances from the U.S. to Central America — primarily Guatemala. It was a small, fast-moving startup building a mobile app that allowed users to buy, sell, convert, and send Bitcoin to local currencies.

 

Originally hired as a QA tester, I quickly became the sole product designer after the previous designer left. I took over a chaotic Figma file, redesigned the core flows, created a new visual language, and collaborated closely with two developers and a PO to ship key improvements.

 

The client didn’t want user research, testing, or discovery. They wanted speed. So I adapted: conducting informal research on my own, working directly with stakeholders, and translating ambiguous requests into structured, testable UX solutions. It was scrappy, intense — and one of the most hands-on learning experiences I’ve had in product design.

⚠️ The name of the product and brand visuals have been anonymized due to client confidentiality.

THE CHALLENGE

Legacy design, missing context, and an impatient roadmap

When I took over the product, there was no clear documentation, no design system, and no research to work from. The app had outdated UI, unclear flows, and features stitched together without structure.

The client wasn’t interested in discovery or validation — just delivery. They wanted screens, fast. My challenge was to bring structure and usability without slowing things down.

This meant:

This meant:

 

  • Untangling a messy Figma file I inherited from the previous designer
  • Reverse-engineering flows like recharge, withdrawal, and crypto conversion
  • Creating a new visual language and style guide on the go
  • Translating stakeholder requests into UX solutions, often without full context

From this

To this

“This project threw me into the deep end — and that’s exactly where I learned to swim as a product designer.”

Wearing every hat: from QA to UX lead in weeks

I started this project as a QA tester — manually checking flows and logging bugs. But when the previous designer left, I was asked to step in. Since I already knew the product inside out, I became the sole UX designer.

From there, I led:

This meant:

 

  • Untangling a messy Figma file I inherited from the previous designer
  • Reverse-engineering flows like recharge, withdrawal, and crypto conversion
  • Creating a new visual language and style guide on the go
  • Translating stakeholder requests into UX solutions, often without full context

With no budget or time for user research, I adapted:

This meant:

 

  • Untangling a messy Figma file I inherited from the previous designer
  • Reverse-engineering flows like recharge, withdrawal, and crypto conversion
  • Creating a new visual language and style guide on the go
  • Translating stakeholder requests into UX solutions, often without full context

It wasn’t always smooth — the client prioritized speed over depth, and feedback was often vague. But that only made me more resourceful.

From busy to intuitive: simplifying the first touchpoint

The original UI was overloaded with competing elements — multiple balance displays, unclear hierarchy, and visual clutter that made core actions harder to spot. While the product offered powerful features, they were buried beneath inconsistent layouts and unnecessary friction.

before

after

In the redesign, I focused on:

 

  • Clarifying visual hierarchy: the balance is now legible and prioritized, with supporting info minimized.
  • Streamlining key actions: deposit, convert, and receive are front and center — no more guessing.
  • Reducing noise: the layout is simplified, white space is used intentionally, and language is more focused.

These small shifts made the homescreen feel more trustworthy and intuitive — especially for users new to crypto.

Designing the Recharge Flow: Turning Intent into Action

If the homescreen was the entry point, the recharge flow was the turning point.

 

This was the moment when a curious user became an active one — loading money into their wallet and beginning their journey with the app.

But the original experience made it hard to commit.

We saw drop-offs in early steps due to too many decisions upfront, unclear next steps, and an overload of information that created hesitation instead of confidence.

What we changed:

 

  • Linear storytelling with overlays: We broke down the recharge process into a series of clear, focused steps using overlay screens. Each one explained a single concept or action, guiding the user naturally through the flow.
  • Progressive disclosure: Instead of overwhelming users with forms and options all at once, we revealed only what was needed at each step — making it feel simpler and less risky.
  • Reassurance through clarity: We rewrote labels, added inline feedback, and removed optional distractions to make each screen feel obvious and safe — even for users new to crypto or banking apps.

 

 

We weren’t just redesigning screens — we were building trust into every tap.

This shift had a measurable impact: fewer drop-offs, faster completions, and a clearer path to conversion.

Bringing Clarity Across the Whole Money Journey

While the recharge flow was the most critical entry point, I also redesigned the key money movement flows across the app — including withdrawal, conversion, and auto-conversion.

Each of these followed the same design principles:

This meant:

 

  • Untangling a messy Figma file I inherited from the previous designer
  • Reverse-engineering flows like recharge, withdrawal, and crypto conversion
  • Creating a new visual language and style guide on the go
  • Translating stakeholder requests into UX solutions, often without full context

The goal was to make every interaction — from cashing out to converting currencies — feel easy, safe, and trustworthy.

When I joined the project, the product had just launched and was still figuring out how to meet users where they were — in a region where crypto adoption was rising, but financial literacy was still low.

Our goal wasn’t just usability. It was translation. We were translating:

This meant:

 

  • Untangling a messy Figma file I inherited from the previous designer
  • Reverse-engineering flows like recharge, withdrawal, and crypto conversion
  • Creating a new visual language and style guide on the go
  • Translating stakeholder requests into UX solutions, often without full context

The design needed to feel like a conversation — not a challenge. We used simple language, progressive steps, and clear visual cues to turn intimidating financial actions into approachable ones.

In a space that often feels overwhelming, we aimed to make crypto feel almost playful — like something you could understand with just a few taps. And for many users, that was the difference between bouncing… and buying in.

What I Learned

This project tested more than just my design skills — it challenged how I think about building products when the ideal conditions aren’t there.

Here’s what I took away:

  • Design isn’t always glamorous — but it still has to deliver. I stepped into a chaotic file, tight deadlines, and no formal research or analytics. Instead of waiting for perfect conditions, I created structure, simplified flows, and made sure users had a clear path through the product.
  • Lack of data isn’t an excuse — but a signal to be scrappy and resourceful. Ideally, we’d have had usage metrics, formal interviews, and time for deep exploration. We didn’t. So I observed patterns, mapped edge cases manually, and validated decisions through conversation, not dashboards.
  • Ownership is about stepping up, not being asked. I wasn’t originally hired as the UX designer — I was QA. But I knew the product inside out, so when the time came, I led the redesign, organized the design system, managed handoffs, and aligned the team around clearer flows.

This wasn’t a textbook case study. It taught me how to move fast, stay clear, and take ownership even in the messiest moments.

🧰 Tools Used

  • Figma – UI design, prototyping, style guide creation
  • Flutter – Understanding interface structure and developer handoff
  • Miro – Mapping flows and internal logic
  • Notion – Documenting decisions and collaborating with the team

Let’s work together

May, 2023

From QA to UX Lead: Rebuilding a Crypto App from the Inside

INTRODUCTION

Designing a crypto remittance app for Central America — under pressure, without research support, and with full UX ownership.

In 2022, I joined a fintech project focused on enabling Bitcoin-based remittances from the U.S. to Central America — primarily Guatemala. It was a small, fast-moving startup building a mobile app that allowed users to buy, sell, convert, and send Bitcoin to local currencies.

Originally hired as a QA tester, I quickly became the sole product designer after the previous designer left. I took over a chaotic Figma file, redesigned the core flows, created a new visual language, and collaborated closely with two developers and a PO to ship key improvements.

The client didn’t want user research, user testing, or discovery. They wanted speed. So I adapted: conducting informal research on my own, working directly with stakeholders, and translating ambiguous requests into structured, testable UX solutions. It was scrappy, intense — and one of the most hands-on learning experiences I’ve had in product design.

⚠️ The name of the product and brand visuals have been anonymized due to client confidentiality.

THE CHALLENGE

Legacy design, missing context, and an impatient roadmap

When I took over the product, there was no clear documentation, no design system, and no research to work from. The app had outdated UI, unclear flows, and features stitched together without structure.

The client wasn’t interested in discovery or validation — just delivery. They wanted screens, fast. My challenge was to bring structure and usability without slowing things down.

This meant:

  • Untangling a messy Figma file I inherited from the previous designer
  • Reverse-engineering flows like recharge, withdrawal, and crypto conversion
  • Creating a new visual language and style guide on the go
  • Translating stakeholder requests into UX solutions, often without full context

From this

To this

“This project threw me into the deep end — and that’s exactly where I learned to swim as a product designer.”

Wearing every hat: from QA to UX lead in weeks

I started this project as a QA tester — manually checking flows and logging bugs. But when the previous designer left, I was asked to step in. Since I already knew the product inside out, I became the sole UX designer.

From there, I led:

  • End-to-end UX design for core flows like recharge, withdrawal, crypto conversion, and auto-conversion
  • Redesign of the homescreen, simplifying the interface and prioritizing clarity for everyday users
  • Creation of a style guide, cleaning up legacy styles and establishing visual consistency
  • Developer handoffs and QA, supporting implementation and making sure what we shipped matched the vision

With no budget or time for user research, I adapted:

  • I ran informal research on my own (benchmarking, heuristics, user behavior patterns)
  • I simplified flows based on logic and clarity
  • I validated design decisions directly with developers and stakeholders in weekly calls

It wasn’t always smooth — the client prioritized speed over depth, and feedback was often vague. But that only made me more resourceful.

From busy to intuitive: simplifying the first touchpoint

The original UI was overloaded with competing elements — multiple balance displays, unclear hierarchy, and visual clutter that made core actions harder to spot. While the product offered powerful features, they were buried beneath inconsistent layouts and unnecessary friction.

before

after

In the redesign, I focused on:

 

  • Clarifying visual hierarchy: the balance is now legible and prioritized, with supporting info minimized.
  • Streamlining key actions: deposit, convert, and receive are front and center — no more guessing.
  • Reducing noise: the layout is simplified, white space is used intentionally, and language is more focused.

These small shifts made the homescreen feel more trustworthy and intuitive — especially for users new to crypto.

Designing the Recharge Flow: Turning Intent into Action

If the homescreen was the entry point, the recharge flow was the turning point.

This was the key moment where curiosity turned into commitment — when a user loaded money into their wallet and started their journey.

But the original experience made it hard to commit.

We saw drop-offs in early steps due to too many decisions upfront, unclear next steps, and an overload of information that created hesitation instead of confidence.

What we changed:

 

  • Linear storytelling with overlays: We broke down the recharge process into a series of clear, focused steps using overlay screens. Each one explained a single concept or action, guiding the user naturally through the flow.
  • Progressive disclosure: Instead of overwhelming users with forms and options all at once, we revealed only what was needed at each step — making it feel simpler and less risky.
  • Reassurance through clarity: We rewrote labels, added inline feedback, and removed optional distractions to make each screen feel obvious and safe — even for users new to crypto or banking apps.

 

 

We weren’t just redesigning screens — we were building trust into every tap.

This shift had a measurable impact: fewer drop-offs, faster completions, and a clearer path to conversion.

Bringing Clarity Across the Whole Money Journey

While the recharge flow was the most critical entry point, I also redesigned the key money movement flows across the app — including withdrawal, conversion, and auto-conversion.

Each of these followed the same design principles:

  • Clear hierarchy and structure
  • Simpler, progressive steps
  • Language tailored for users unfamiliar with finance or crypto

The goal was to make every interaction — from cashing out to converting currencies — feel easy, safe, and trustworthy.

When I joined the project, the product had just launched and was still figuring out how to meet users where they were — in a region where crypto adoption was rising, but financial literacy was still low.

Our goal wasn’t just usability. It was translation. We were translating:

  • crypto into real-world value
  • friction into trust
  • steps into stories

The design needed to feel like a conversation — not a challenge. We used simple language, progressive steps, and clear visual cues to turn intimidating financial actions into approachable ones.

In a space that often feels overwhelming, we aimed to make crypto feel almost playful — like something you could understand with just a few taps. And for many users, that was the difference between bouncing… and buying in.

What I Learned

This project tested more than just my design skills — it challenged how I think about building products when the ideal conditions aren’t there.

Here’s what I took away:

  • Design isn’t always glamorous — but it still has to deliver. I stepped into a chaotic file, tight deadlines, and no formal research or analytics. Instead of waiting for perfect conditions, I created structure, simplified flows, and made sure users had a clear path through the product.
  • Lack of data isn’t an excuse — but a signal to be scrappy and resourceful. Ideally, we’d have had usage metrics, formal interviews, and time for deep exploration. We didn’t. So I observed patterns, mapped edge cases manually, and validated decisions through conversation, not dashboards.
  • Ownership is about stepping up, not being asked. I wasn’t originally hired as the UX designer — I was QA. But I knew the product inside out, so when the time came, I led the redesign, organized the design system, managed handoffs, and aligned the team around clearer flows.

This wasn’t a textbook case study. It taught me how to move fast, stay clear, and take ownership even in the messiest moments.

🧰 Tools Used

  • Figma – UI design, prototyping, style guide creation
  • Flutter – Understanding interface structure and developer handoff
  • Miro – Mapping flows and internal logic
  • Notion – Documenting decisions and collaborating with the team