Company:
Tapsi
Year:
2022 - 2024
Role:
Product Designer
Imagine you're a ride-hailing driver in Tehran, late for your next shift, and your car suddenly needs engine oil. You open Tapsi Garage, Tapsi's in-app marketplace for car parts and services. Instead of quickly finding what you need, you're met with cluttered screens, inconsistent visuals, and a confusing checkout flow.
Under time pressure, every second counts, yet the app feels like it's working against you. That was the story drivers told us when we started this redesign.
My role was to transform Tapsi Garage into a driver-first, scalable, and accessible product, a platform serving thousands of drivers across multiple cities, while aligning with Tapsi's broader design ecosystem.
Eleven categories, no hierarchy
Before any redesign work, research surfaced three problems that together explained why a functioning storefront was still losing customers.
This research shaped our problem statement, not the other way around.
Sorting it twice before I trusted it
I imported the research data into an affinity map and sorted it into themes twice, the first pass was too broad to
design against, so I converged it into a second, sharper set before touching any screen.
With research insights and workshop outcomes in hand, we moved to restructuring the
experience from the ground up. Three key areas drove the IA work.
The card sort that settled the argument
The navigation had eleven top-level items with no visible hierarchy. The Strategy Lead pushed back on simplifying it. I
ran a card-sorting exercise with eight internal stakeholders instead of arguing the point, the data won the argument.
One structure, three places drivers meet it
Garage isn't a single screen. A driver may start on the responsive web storefront, complete the booking in the native app, and return through a service reminder. The navigation change only holds if it survives all three, so the structure was designed once and the component library carried it across.
Keeping one component library across surfaces is also what made the handoff reduction possible: engineering built each pattern once instead of per platform.
Where I chose the harder path
Two decisions shaped this project more than any interface detail.
The system that carries the product
Three questions, three decisions
What I'd do next
