Meshwarak: One Destination, Every Ride Side by Side
Redesigning a ride-comparison app around one question: pay less, or wait less?
Company
Meshwarak
Role
Product Designer
Expertise
UX Research, Comparison UX, Arabic-first UI, Design System
Timeline
2023

Meshwarak is a ride-comparison app for Saudi Arabia. Instead of opening several ride apps to check prices, riders set a destination once, compare price and waiting time across providers, and continue with the one they choose. The app was already in the market; I redesigned it end to end, from research and user journeys to the design system and developer handoff.
The Starting Point: An App People Used but Did Not Fully Trust
Before redesigning, I looked at three sources: competitor apps such as Obi and RideGuru, Play Store reviews of Meshwarak and its competitors, and interviews with riders. Six problems kept coming up: a complex interface with too many steps, unclear navigation, an imprecise map, support that was hard to reach, a dated visual style and slow, heavy screens. Underneath them was a bigger issue: Meshwarak sends people to another app to pay, so it has to earn their trust first.

Decision 01: Start With Where You Are Going
The home screen is a map with a single destination field. Home and work shortcuts and saved places shorten the trips people repeat, and first-time tooltips explain location and account linking only when they become relevant.

Decision 02: Make the Price and Time Trade-Off Visible
Results can be sorted by cheapest or fastest, which turns a long list into the rider’s real question. Every card puts provider, price, waiting time and seats in the same place, chips narrow the list to standard or premium rides, and a recommended tag gives the eye a starting point. The English version follows the same structure.

Decision 03: Hand Over to the Provider Without Losing Trust
The trip screen states plainly that payment and the ride itself are handled by the provider. Linking a provider account is explained with its benefits before asking, and can be skipped. Provider pages show rating, car types, payment methods and promo codes before the rider leaves the app.

Decision 04: Make Help Easy to Find
Support was one of the most repeated complaints, so Help and Support brings the FAQ, help centre, privacy, terms and contact into one list. Profile completion became a short, guided flow with a clear success state.

Extension: Buses and Trains in the Same App
I also designed a public transport extension. Taxi, bus and train sit side by side on the same home, routes list their stops in order, and intercity bus trips are compared with the same card language as rides.

The System
The redesign kept Meshwarak’s green identity but rebuilt everything around it: Tajawal for Arabic, a consistent size scale, spacing on an 8px grid, and a documented component library so developers could build the screens as designed.

The Outcome
141 screens and states across Arabic, English and public transport, from onboarding to provider handoff, delivered with a design system for development. The plan included usability testing with real riders, to check the redesign against the problems found in research.


