Driver app · Brisbane

Driver app for taxi fleets in Brisbane

Native Android, FCM push, offline-tolerant, ratings + chat built in. Configured for Queensland Department of Transport and Main Roads.

Driver app in Brisbane is the native android, fcm push, offline-tolerant, ratings + chat built in, configured against Queensland Department of Transport and Main Roads and the operating reality of a 3.1k-vehicle market. TaxiCloud's driver app is native Android with iOS variant in beta. Real-time GPS, offer/accept flows, in-app chat, ratings, settlement reports, and offline-tolerant queuing — designed by ex-PHV operators for the operating reality of a working shift. For Brisbane specifically, the feature reads from regulator-aware booking, dispatch, and reporting surfaces — no bolt-on integration, no separate console.

Driver app in Brisbane — the operating reality

Driver app ships against the Queensland operating geography as a structural object. The driver app is the single most-used surface in any dispatch operation. Drivers use it for the entire shift; if it is slow, awkward, or unreliable, drivers stop accepting jobs and operations suffer. TaxiCloud's driver app was designed by ex-PHV operators rather than mobile-first product designers, which shows in the choices: clean offer/accept flow with ETA-based job ranking, large readable text for road conditions, voice-prompt mode for hands-free job acceptance, settlement reports that match what drivers actually want at end-of-shift. In Brisbane, the feature posts cleanly against Queensland Department of Transport and Main Roads quarterly returns, vehicle inspection cycles, and the 3,100-vehicle scale that defines the market. BNE airport flows integrate natively where applicable.

How TaxiCloud delivers driver app in Brisbane

Operators in Brisbane typically run driver app on TaxiCloud after a 6-10 day migration off iCabbi, Autocab, Cordic, or TaxiCaller. Real-time GPS streams to the dispatch board over WebSocket; pin position updates land in the customer-facing app simultaneously so passengers see live driver progress. Offline tolerance is first-class: when drivers lose signal, the app queues GPS pings and job-state events locally; on reconnection, the queue flushes in order to maintain a continuous trail. This matters for areas with unreliable coverage, motorway stretches between cities, and underground stations. The dispatcher impact is highest in the Brisbane operating tempo because Queensland Department of Transport and Main Roads compliance overlays the standard PHV regulatory posture, and driver app surfaces the resulting reports through the same dispatch flow rather than as a separate finance task.

FAQ

Driver app in Brisbane — questions answered.

How does Driver app work in Brisbane?: Driver app in Brisbane reads from the live dispatch board, the customer-facing booking widget, and the Queensland Department of Transport and Main Roads compliance reporting layer in a single tenant. Driver logs in at shift start; status sets available. The Brisbane configuration is preset for the city's 3,100-vehicle market and the Queensland operating geography.
Is Driver app compliant with Queensland Department of Transport and Main Roads?: Yes. Driver app is calibrated for Queensland Department of Transport and Main Roads reporting, audit, and renewal cycles. Vehicle inspection deadlines, driver-licence audits, and the local quarterly return format ship pre-configured. Format updates land in-sprint when the regulator changes requirements.
What does Driver app cost for a Brisbane fleet?: Driver app ships on every TaxiCloud plan — Starter through Pro Ultra. Transparent A$89-A$629/month pricing. Most Brisbane fleets run Pro (£149/€55/$59/A$89 month) or Pro Max (£349/€395/$449/A$629 month). No setup fee on Starter or Pro; month-to-month contracts; driver app configuration in Brisbane is included.

Ready when you are

Dispatch on autopilot.

14-day free trial. No card. Cancel anytime.

47 fleets joined this month · Talk to sales