Mobility

Mobility UX is designed for people in motion. Whether someone is booking a ride, planning a train connection, or following directions through an unfamiliar city, they are glancing at a screen between other things that need their attention. The interface has to answer one question at a time — where is my ride, which platform, when do I turn — and answer it at a glance.

Where mobility UX usually breaks

Status is the hardest part. A car icon that jumps around the map, an arrival time that keeps slipping, or a delay announced only after the passenger is already waiting all erode confidence quickly. Pricing is the second break: surge or dynamic fares that change between screens, and totals that differ from the estimate, feel unfair even when they are explained in the small print. The third is the edge case — a missed pickup, a cancelled service, a lost item — where many apps hand off to a support form at exactly the moment the traveller needs a clear next step.

What good mobility UX does instead

It treats feedback and system status as the core product: live position, honest estimates, and timely notifications when anything changes. It keeps the main action reachable with one hand and readable in sunlight. It shows the price before commitment and explains any difference afterwards. And it keeps the whole journey in one place, so tickets, receipts, and help are easy to find. Underneath all of it is UX clarity: fewer choices on screen when the user has the least attention to spare.

This hub collects TYPENORM's mobility articles and teardowns. The catalog has examples across ride-hailing in Uber and Lyft, public transport in Citymapper, and navigation in Waze and Google Maps.