RideXpress Case Study
A fragmented ride-booking flow untangled from twelve steps into three decisions.
01 THE PROBLEM
RideXpress offered useful local and intercity services, but the mobile website made them difficult to trust. A login popup could freeze, icons did not behave as expected, vehicle imagery was missing, and pricing arrived too late. Travellers on limited connectivity had to fight the interface before they could judge the service.
02 THE REFRAME
Twelve steps became three decisions. Where, when and which vehicle are the decisions that move a booking forward. Everything else became progressive detail or a sensible default. The project stayed on the responsive web instead of forcing an app download, making speed and transparent pricing the product strategy rather than surface polish.
03 THE FLOW
The end-to-end map turns the booking into six visible stages: location, service, schedule, vehicle, live price and confirmation. Each state answers one question and exposes cost before commitment. That sequence removes the hidden branches and dead interactions that made the original experience feel longer than the service itself.
04 IN MOTION
The final motion study shows the redesigned experience as one continuous journey rather than isolated mockups. Navigation, vehicle selection, pricing and confirmation share the same rhythm and visual hierarchy, so the interface feels predictable even as the task changes.
05 THE PRODUCT
The finished mobile system carries the same decisions through discovery, vehicle comparison and booking confirmation. Real vehicle imagery makes the choice legible, pricing stays visible, and the final state closes the loop with a clear summary instead of leaving the user to infer whether the booking worked.
06 THE OUTCOME
The four-week redesign replaced a brittle mobile site with a complete responsive booking proposal. In simulated testing, average booking time moved from five minutes to two-and-a-half, projected drop-off moved from 30% to 8%, and the mobile usability score reached 90/100. These are concept-validation results, not production outcomes.