Passenger requests a trip
Pickup, destination, vehicle class and estimated fare are confirmed.
Concept project — not a real client
CityRide
A connected taxi ecosystem that moves a phone-heavy operation toward digital booking, driver workflows and live dispatch visibility.
Business typeLocal taxi operation
Product scopePassenger + Driver + Dispatch
StatusDesign concept
Concept objective
Demonstrate how the same trip can move through customer booking, driver acceptance and dispatcher oversight without relying on phone calls or scattered messages.
Thursday · Live operations46 online
Active trips18
Upcoming34
Available21
◆
◆
◆
◆
◆
Active trips18
Ahmed M. · Airport T2
Sarah K. · Marina
The challenge
One trip, too many disconnected conversations.
The concept assumes an operation where customers call to book, dispatch manually finds drivers, and passengers call again for updates.
The design goal is not “make a taxi app.” It is to create a shared trip state that customer, driver and operator can each understand from their own interface.
User journey
Follow the trip across four surfaces.
The important design work happens in the handoff between booking, assignment, pickup and completion.
Dispatch sees the request
Availability and proximity help the operator understand capacity.
Driver receives work
Pickup, destination, expected earning and navigation context are clear.
Everyone sees status
The passenger gets ETA while dispatch retains operational visibility.
Passenger app
Booking without a phone call.
Clear destinations, vehicle options and trip status give the passenger the information they would otherwise request from dispatch.
✓
Vehicle choiceEconomy, business or van with ETA and price context.
✓
Live trip stateDriver, vehicle, plate, ETA and route updates.
Current location
Airport Terminal 2
Driver arriving
Mohamed R. · 4 min
Toyota Corolla · ABC 2481
Good afternoon● Online
New trip request
Airport pickup
Terminal 2 · Arrivals
Downtown · Riverside Hotel
Accept trip
HomeTripsEarnings
Driver app
Enough information to decide and move.
The driver sees the assignment, location context and expected earning without searching through chat messages.
✓
Online / offline stateAvailability is visible to both the driver and dispatch.
✓
Trip request clarityPickup, destination, timing and relevant earning context before acceptance.
Booking website
Capture demand outside the app.
Not every customer will install an app. A browser booking flow gives occasional users and business customers a direct path into the same operation.
Important functionality
Designed beyond the happy path.
✓
Scheduled and immediate bookingsDifferent timing models without separate experiences.
✓
ReassignmentDispatch can react when the originally assigned driver becomes unavailable.
✓
Cancellation statesPassenger, driver and operator receive consistent status changes.
✓
Role permissionsDispatch, managers and support staff can receive different levels of control.
Concept complete
Need a connected passenger, driver and dispatch product for your own operation?
We can map your real workflow instead of copying this demo.
Discuss your project ↗