One ride has two different clocks. For the passenger, the trip begins with a request and includes waiting to be matched, waiting for the assigned car to arrive, and riding to the destination. For the driver, the service cycle begins while available, continues through pickup and transport, and ends only when the car is ready for another match.
Passenger and driver viewpoints follow the same kind of journey in turn. Animated emphasis moves from one stage to the next, and each completed act groups its time components. The comparison clarifies why a platform cannot evaluate performance using in-vehicle travel time alone. A shorter passenger wait may require more drivers spending time available but unpaid, while a long pickup consumes driver capacity before any passenger is transported. The basic sequence is the foundation for later models of matching, pricing, pooling, and fleet supply.
An available taxi is useful to passengers even while it is carrying nobody. More idle vehicles spread through a service area make pickup faster, reducing the delay between requesting a ride and entering a car. Keeping those vehicles available, however, costs driver time and money.
Watch film
An on-demand car, a shared ride, and a fixed-route bus use vehicles very differently. An exclusive car offers direct travel but spends substantial time and distance on each passenger. Pooling shares some of that work at the cost of detours and coordination. A bus gains scale when enough people use a common corridor, but offers less flexible access.
Watch film
Private autonomous vehicles may sit unused for much of the day while other people cannot find a ride. A platform could recruit some of those vehicles, pay their owners for availability or service, and charge passengers for completed trips. Supply would then come partly from assets already owned by households.
Watch film