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.
The video first introduces the three services, then compares their simulated operation under low, medium, and high demand. Live measures settle into a small set of passenger and operator outcomes after each run. A final screen highlights which option is most attractive under each illustrated demand level. The important insight is that efficiency has a demand range: the service that fits sparse requests need not remain best as the market thickens. These are scenario-dependent comparisons, not a universal ranking; geography, service frequency, pooling rules, and how traveler time is valued can move the boundaries.
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
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.
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