Taxi & Private Hire Fleet, Dispatch, Tracking & Booking App

Existing licensed taxi or private hire companies (typically 5-50 vehicles) still dispatching by phone or radio. Best fit: an owner or dispatch office feeling the ceiling of how many bookings one dispatcher can handle manually, or losing bookings to modern ride-app competitors because customers can't see where their driver is.

A rider requests a trip and sees an upfront fare estimate; the system automatically matches the nearest online driver, offering the request to the next-nearest driver if one doesn't respond in time. Once matched, the rider watches their driver's live location on a map, gets clear status updates through pickup and the trip itself, and is charged automatically at completion. The driver gets requests via app alert and SMS backup, navigates using their existing maps app, and updates status with one-tap buttons.

The admin sees the whole fleet live on one map, can manually reassign trips, manage the driver roster, and pull fleet-wide performance analytics. Location tracking runs while the app is open and active, which naturally covers the moments it's actually needed (during a trip); waiting drivers get alerted to new requests via push and SMS rather than needing constant background tracking.

This is the most complex build in the pro-prompt library and should be scoped and priced accordingly, realistically several days of focused build and testing time, not a single afternoon. The three-role architecture (rider/driver/admin sharing one backend) is the right structure, but expect real iteration on the matching and cascading-offer logic, test it with multiple simulated drivers online at once, not just one, to catch bugs in how offers move from one driver to the next. The real-time map updates need testing on an actual mobile device, not just desktop browser, since that's how both riders and drivers will actually use it.

Be direct with the client about the two-stage location-tracking approach: the Lovable build itself tracks live position only while the app is open and active, which is all you need to build and test the full flow. True always-on background tracking gets added at the AppBuild.DIY wrap stage, by enabling the Background Geolocation plugin in its Native Capabilities panel, which also handles the Google Play and Apple compliance steps that capability triggers. Budget time for that extra store review, Google Play in particular wants a background-location declaration and a demo video before approving it.

Common follow-up requests once live: scheduled/advance bookings rather than only on-demand, a simple in-app chat or call-masking between rider and driver, and surge or time-of-day pricing rules layered onto the base fare structure.