A driver app built for the dashboard — turn-by-turn, landscape, and ride requests you answer by voice
Give your drivers an app made for a phone on a mount: a dark, glanceable look that works on its side, the next turn on screen, and ride requests that are read out and answered by voice.
Four days on from the last update, this one is about a single app. The driver app has had 43 changes in that time, and they all point the same way. It was designed for a phone held in the hand, and your drivers use it on a dashboard mount, at arm's length, a glance at a time. Every screen a driver works from has been redrawn for that — and the app now gives directions, speaks, and listens.
Built to be read at a glance
The screens your drivers spend a shift on — waiting for a ride, a request, the way to the pickup, the trip, the fare — have a new look, closer to a car's own display than to a phone app. The fare, the minutes and the distance lead each screen in type that reads from the driver's seat, and every button is big enough to hit without aiming.
The app is dark all day now, map included, so it reads the same through a windscreen at noon as it does at midnight — still in your brand's colours. Accepting a ride is a single tap. The steps that should never happen by accident — arrived, start trip, end trip — take a short hold instead.
On its side, for the dash mount
Plenty of mounts hold a phone sideways, and until now the app only worked upright. Turn the phone and the home screen turns with it.
On its side the layout is the one a car display uses: the ride and its actions in a card on the left, the map in a panel of its own on the right, and nothing sitting on top of anything else. It holds for the whole shift — waiting, a request, the trip, the fare and rating the rider.
The next turn, where your drivers are already looking
A banner over the map shows the next turn and counts down the distance to it, on the way to the pickup as well as on the trip, in the driver's own language. A roundabout shows the number of the exit to take.
The map follows the car. It faces the way the car is travelling, keeps the road ahead in view, and closes in as a turn comes up. A driver who leaves the route is told so and given a new one. Handing off to another navigation app is still one tap away — it is no longer the only way to know where to turn.
A request that shows the ride
A ride request used to be a card of text over a map that had not moved. Now the map draws the ride being offered — pickup, stops and drop-off, with the route between them — alongside where the driver is.
The card carries what a driver needs to decide: what the ride pays, how far away the pickup is, how long the trip is, the rider's rating, and the seconds left to answer. A yes becomes a decision rather than a guess.
A request your drivers can hear
A new request has a tone of its own now, distinct from a chat message. It repeats, with a vibration, until the request is answered or runs out — so a driver watching the road no longer misses a ride because the phone made one short sound.
Then the phone reads the request out: how far the pickup is, how long the trip is, and what it pays, in the app's language and your units. Each step of the trip is said back as the driver confirms it. The sound button silences all of it.
Accept without touching the phone
Your drivers can answer a request by voice. With the switch beside the sound button turned on, the phone listens once it has finished reading the request out. Say "accept" or "decline" and it is done, and the phone says back which one it heard.
Speech is recognised on the phone itself, so nothing said in the car is sent anywhere. The phone listens through its own microphone, so music playing through the car keeps playing. It stays off until a driver turns it on.
Around the driver app
- End of the ride — a metered fare is keyed in on a keypad built into the card, so the phone's keyboard never covers it, and the settlement and the rider rating share the new look.
- Motion — the card stays where it is while what it shows changes, so a driver's eye never has to find it again.
- Today's numbers — the day's rides and earnings sit on the waiting screen and move as each ride finishes.
- Your vehicle on the radar — while a driver waits, the search radar shows the vehicle of their own service class.
- A failed accept — when a ride cannot be accepted, the driver is told, on screen and aloud, instead of watching the request disappear.
- Getting around — a menu button when the phone is upright, and Rides, Earnings, History and More as tabs when it is on its side.