Case Study · UX/UI · E-commerce · Feature Design

Aftersale · Referrals

Transforming an existing referral mechanism into a trackable, visible, continuous experience, integrated into the daily flow of the product.

Company

Aftersale

Role

UX/UI Designer

Platform

iOS · Android

Year

2021

01 · The program

A growth strategy users couldn't see

Aftersale already had a functioning referral program. Users could invite new customers and earn credits from each conversion. The mechanics existed, but lived at the margins of the main experience.

Referring was a one-time action. What happened next — which invites were accepted, which converted, how much was earned — remained uncertain. Without visible feedback, the program lost traction as an active growth channel.

The user referred. What happened after remained uncertain.

02 · The unanswered questions

The program existed. The answers didn't.

Even while participating in the program, users couldn't easily answer three basic questions. Without those answers, referring stopped being a strategy and became an act of faith.

"How much have I earned in credits?"

The total was scattered across the account, with no clear number easy to find within the main experience

"Which referrals actually converted?"

Accepted and converted invites coexisted without distinction: impossible to know the real impact of each invite sent

"How far am I from the earning limit?"

The credit cap existed in the program rules, but no visual reference indicated how far away it was

03 · The feature structure

Three connected elements that answer the three questions

The referrals screen was built as a tracking area, not an isolated menu. The organization is not arbitrary: each section directly answers one of the questions users couldn't answer before.

Accumulated value front and center

The total credits earned occupies the primary position and immediately answers the most important question with no additional navigation. The large number is the answer.

Progress bar toward the limit

Turns the absolute number into a directional reference. Users don't just see how much they earned — they see how much they can still earn, which changes their relationship with the program.

History with visible status per invite

Each referral has a clear status: Converted, Accepted, Expired. Users see the real impact of each action without needing to calculate, infer, or remember.

04 · The screens

The tracking flow

From the overview of results to sharing the link, including the detailed history of each referral. The screens cover the full journey users follow within the program. The Aftersale app includes other areas that are outside the scope of this case.

Drag to explore →

Referrals

Invites

Detail

How It Works

05 · How the screen organizes reading

Hierarchy before layout

The central decision in this project was not about layout, it was about hierarchy. Before defining where each element would go, it was necessary to define what users should see first, second, and when they wanted to dig deeper. The layout followed that order, not the other way around.

Primary

Total accumulated value

Answers the most important question with no effort. The main number defines the "was it worth it?" before any other reading. It's what users come to check on most visits.

Secondary

Progress bar + recent referrals

Creates direction and continuity. Users see how far they are from the limit and the most recent activity, enough context for most visits, without needing to navigate anywhere else.

Tertiary

Full history with status filters

Available for those who want more detail, without occupying attention for those who don't. Access is deliberate — users arrive when they intend to audit their conversions.

06 · Reflection

Visible results drive continuity

The central challenge of this project was not creating something new — the referral mechanism already existed. It was finding the structure that would make that mechanism understandable and motivating in the daily use of the product.

A feature users don't track is a feature users forget. Visibility of results is what turns a feature into a habit.

The feature doesn't change the program. It changes the user's relationship with it. When the result is visible, referring stops being a passive possibility and becomes an active strategy, something users choose to repeat because they understand the return.