TOP: APP DE MOBILIDADE

TOP: APP DE
MOBILIDADE

TOP: APP DE
MOBILIDADE

Redesigning São Paulo’s Transit App Faster Access and Less Friction

Redesigning São Paulo’s Transit App Faster Access and Less Friction

SUMMARY

SUMMARY

I worked with Autopass on redesigning their mobile experience
for São Paulo’s public transportation system, improving the experience for over 4 million users. With zero research and tight deadlines, I rebuilt the key flows (recharge, QR, balance) to reduce friction, scan fast, and keep things scalable. No fluff. Just clarity and decisions that mattered.

I worked with Autopass on redesigning their mobile experience for São Paulo’s public transportation system, improving the experience for over
4 million users. With zero research
and tight deadlines, I rebuilt the key flows (recharge, QR, balance) to reduce friction, scan fast, and keep things scalable. No fluff. Just clarity
and decisions that mattered.

CLIENT

CLIENT

AUTOPASS

AUTOPASS

ROLE

ROLE

UI/UX DESIGNER

UI/UX DESIGNER

challenge

challenge

The previous app wasn’t confusing or cluttered, it just needed
an updated structure and identity to support new features.
Key actions like requesting a card or recharging were buried in unclear flows. I was brought in to restructure the navigation and redesign the QR section so users could see active, used, or shared cards without guessing. No new features would land well without fixing the basics.

The previous app wasn’t confusing

or cluttered, it just needed an updated structure and identity to support new features. Key actions like requesting
a card or recharging were buried
in unclear flows. I was brought
in to restructure the navigation and redesign the QR section so users
could see active, used, or shared
cards without guessing. No new features would land well without
fixing the basics.

DELIVERABLES

DELIVERABLES

WIREFRAMES

WIREFRAMES

PROTOTYPES

PROTOTYPES

DOCUMENTATION

DOCUMENTATION

MOCKUPS

MOCKUPS

deadline

deadline

13 WEEKS

13 WEEKS

industry

industry

TRANSPORTATION

TRANSPORTATION

FINANCE

FINANCE

technology

technology

tools

tools

FIGMA

FIGMA

MIRO

MIRO

VIEW LIVE APP

Button Text

VIEW LIVE APP

Button Text

VIEW LIVE APP

Button Text

my role

my role

I was responsible for redesigning the full interface and navigation logic for the app. Beyond screens, I mapped and restructured flows for key operations like balance checking, card requests, recharges, and QR Code access. I also wrote detailed handoff documentation with logic, edge cases, error messaging, and business rules, making sure devs could build fast without back-and-forth. My focus was clarity, edge coverage, and delivering a system that could scale.

Image above: Full app structure and flows mapped, including onboarding, QR logic, balance and recharge rules, edge cases, and card management.

I was responsible for redesigning
the full interface and navigation logic
for the app. Beyond screens,
I mapped and restructured flows for key operations like balance checking,
card requests, recharges, and QR Code access. I also wrote detailed handoff documentation with logic, edge cases, error messaging,
and business rules, making sure devs could build fast without back-and-forth. My focus was clarity, edge coverage, and delivering a system that
could scale.

Image above: Full app structure and flows mapped, including onboarding, QR logic, balance and recharge rules, edge cases, and card management.

What I Focused On

What I Focused On

I focused on simplifying core flows like QR ticketing, recharge, and balance checking while accounting for edge cases like failed payments, shared tickets, and card reusability. Onboarding was added for new users, and I wrote detailed documentation to guide development without ambiguity.

I focused on simplifying core flows like QR ticketing, recharge, and balance checking while accounting for edge cases like failed payments, shared tickets, and card reusability. Onboarding was added for new users, and I wrote detailed documentation to guide development without ambiguity.

QR Code and Ticket Management

QR Code and Ticket Management

  • Separated active, used, and shared tickets to avoid
    ambiguity

  • Added visual indicators and context-aware messaging to reinforce usability

  • Prevented confusion on expiration and sharing through color and status tags

  • Designed quick access to each ticket state without deep navigation

  • Separated active, used,
    and shared tickets to avoid ambiguity

  • Added visual indicators and context-aware messaging
    to reinforce usability

  • Prevented confusion on expiration and sharing through
    color and status tags

  • Designed quick access to each ticket state without
    deep navigation

What I Focused On

Buying QR Tickets

Buying QR Tickets

  • Streamlined the full purchase flow into just 3 steps with real-time feedback

  • Designed onboarding for subway and bus users to explain how QR access works

  • Handled Pix/credit/debit card failures with retry paths and clear messaging to reduce support load

  • Built fallback scenarios for card conflicts, expired credits, or exceeded limits

  • Ensured every purchase ends with confirmation and recovery options

PIX Ticket Purchase

PIX Ticket Purchase

A full demo of how users buy QR tickets for metro and train rides using Pix, from selection to confirmation, with clear steps, real-time feedback, and built-in fallback for failed payments.

A full demo of how users buy QR tickets for metro and train rides using Pix,
from selection to confirmation,
with clear steps, real-time feedback,
and built-in fallback for failed payments.

What I Would Measure

What I Would Measure

Even though I didn’t have access to analytics or user testing during this project, here’s what I would track to validate decisions and identify areas to improve:

  • Completion time for QR ticket purchases

  • Drop-off rate during Pix payments

  • Error rate when using shared or expired tickets

  • Clarity score on balance and card status comprehension

  • User retention in the recharge flow after onboarding

Even though I didn’t have access
to analytics or user testing during this project, here’s what I would track
to validate decisions and identify
areas to improve:

  • Completion time for QR ticket purchases

  • Drop-off rate during Pix payments

  • Error rate when using shared
    or expired tickets

  • Clarity score on balance
    and card status comprehension

  • User retention in the recharge
    flow after onboarding

What I Learned

What I Learned

This project reinforced something simple but critical: if users have to think too much to do something basic, the system has failed. Even without research or testing, designing for clarity and assuming nothing became the most valuable principle.
It also reminded me that edge cases are not “extra work”, they’re part of designing something real.

This project reinforced something simple but critical: if users have to
think too much to do something basic,
the system has failed. Even without research or testing, designing for clarity and assuming nothing
became the most valuable principle.
It also reminded me that edge cases are not “extra work”, they’re part
of designing something real.

This project reinforced something simple but critical: if users have
to think too much to do something basic, the system has failed.
Even without research or testing, designing for clarity and assuming nothing became the most valuable principle. It also reminded me
that edge cases are not “extra work”, they’re part of designing something real.