PTEN
← All case studies
Product DesignUX/UIMobileAcademic project

Fan2Fan

From fan to fan, with the security to buy and sell tickets.

My role
Research, architecture, flows, UI, prototype and brand identity
Type
Capstone project · mobile app
Tool
Figma
Home screen: search, categories and tickets from verified sellers near the user
Event page with a verified seller, protected purchase and ticket linked to the seller's ID
Checkout with a summary, protection fee and a note that payment is held until the transfer
02 — Problem

When tickets sell out, where can you safely find another one?

When I tried to buy a ticket for a sold-out event, I had to turn to third parties. Talking to other people, the same pattern kept showing up: the ticket was there, the trust wasn't.

Fake ticket

Does this ticket even exist?

Unknown seller

Does this person really have the ticket?

Unsafe payment

What if I pay and never get it?

No follow-up

What happens after I pay?

03 — Research

Discovery on three fronts

01

Personal experience

The problem came from a real purchase of a sold-out ticket.

02

Exploratory conversations

People aged 25 to 35 who had bought or sold tickets from third parties.

03

Benchmark

Ticketing platforms and peer-to-peer marketplaces.

SymplaEventimTicketmasterOLXMercado Livre

Insight. The fewer steps between users and their goal, the better, as long as security isn't compromised.

04 — Opportunity

How do you turn a deal between strangers into a trustworthy experience between fans?

05 — Users

Two users, two goals

Buyer

Lucas

Looking for a ticket to a sold-out event. Needs to find it fast, know it's legitimate and follow the transfer.

Seller

Mariana

Has a ticket she won't use. Wants to list it easily, prove it's valid and get paid safely.

06 — Journeys

Short journeys, end to end

Buying · Lucas

Sign-up→Feed→Event→Checkout→Transfer→My tickets

No tickets available? The user gets notified when a new one is listed.

Selling · Mariana

Sign-up→List ticket→Validation→Sale→Transfer→Payout

Payment is released after the buyer checks in, or 2 days after the event.

07 — Solution

Security as a system, not as a feature

Each mechanism answers one of the frictions in the problem.

ID (CPF)

Identifies the user and links the ticket to them.

Validation

Tickets are verified before going on sale.

Payment held

Released only when the transaction is completed.

Step-by-step feedback

Status visible throughout the deal.

Notifications

In the app and by email.

Wallet

Balances, payments and status in one place.

Limit per ID

Curbs scalping and keeps it fan to fan.

Ticket listing screen with notes that the sale is linked to the seller's ID and limited to one deal at a time
Listing: the ID and one-deal-at-a-time notes appear before publishing.
08 — Architecture

Product map

Fan2Fan

Home / Feed

Nearby events · geolocation

Search

Price · date · location

List a ticket

Selling journey

My tickets

Purchased · in transfer

Wallet

Balances · status

Profile

Account · notifications

09 — UI foundations

Young, digital and trustworthy

Name

The “2” in Fan2Fan stands for the two sides of the deal and sounds like “to”: fan to fan.

Colors

BlueTrust
PurpleTechnology
GradientBrand
AccentSell CTA

Typography

Aa
Inter, an organic sans serif: technological, yet human.

Buttons

Primary · gradientSecondary · whiteTertiary · outline
Onboarding screen with the Fan2Fan brand: from fan to fan
Login screen with access protected by ID verification
10 — Key screens

Decisions on screen

01 · Discovery

A geolocated feed with familiar event cards. Decision: clear CTAs to reduce navigation effort.

Home with events available near the user
Home / Feed
Favorite events list
Favorites
Event page with seller details
Event
Notification center for purchases and sales
Notifications

02 · Buying and selling

One main action per screen. Decision: fewer steps without hiding important information.

Checkout: purchase summary
Buy · summary
Checkout: payment
Buy · payment
Purchase confirmation awaiting transfer
Buy · confirmation
Ticket transferred successfully
Buy · ticket arrived
List a ticket: file upload and details
Sell · listing
Ticket being validated with the issuer
Sell · validation
Ticket published in the catalog
Sell · published
Ticket sold and amount to receive
Sell · sold

03 · Wallet and My tickets

Control after payment: balances, status, amounts to receive and tickets in transfer. The thinking goes beyond the checkout screen.

Wallet with available balance, amounts to receive and transactions
Wallet
My tickets with the status of each purchase
My tickets
Ticket ready to download
Ticket
Profile with verified identity and history
Profile
11 — Testing and iteration

What testing showed

Test

Usability testing with users aged 25 to 60: buy and sell a ticket.

Result

Everyone completed both journeys.

Insight

Older users took longer to find the sell action.

Iteration

A bigger button, an accent color outside the palette and more prominence, with no new steps.

12 — Metrics and business

How we would measure success

The product wasn't launched, so these are proposed indicators, not results.

Sign-ups

User acquisition

Listings

Supply on the platform

Purchases

Actual marketplace use

Business model

A 10% fee per transaction, split transparently.

5%buyer+5%seller
13 — Learnings

What I'd do differently today

Research

A larger, more diverse sample, with stronger insights before prioritizing.

Design system

Turn the visual patterns into a Figma library: components, variants and states.

A good interface is only part of the solution: every decision has to remove a real friction.