Twenty-eight drops and a phone on the dashboard
Driving for a living puts three demands on a phone that ordinary navigation does not. The route has many stops rather than one, so the order matters more than the turns. It runs for ten hours, so heat and battery decide what is usable. And it produces a record that somebody will want later, whether that is a mileage figure at the end of the year or a video of the vehicle that pulled out without looking.
The platform app handles the job list and nothing else well. Everything below is the layer around it.
What actually breaks over a long shift
| Problem | What happens | What helps |
|---|---|---|
| Many stops, poor order | An hour of avoidable driving | A route planner that reorders the list |
| Phone overheating on the windscreen | Throttling, then the camera stops | A vent mount out of the sun, and less screen brightness |
| Battery | Flat by mid-afternoon | A proper car charger, not a spare cable |
| No signal in a rural dead zone | Navigation stops mid-route | Offline maps downloaded the night before |
| Nowhere to stop at the drop | Circling, or a ticket | Parking data, checked before you arrive |
| No record of what happened | Your word against theirs | A dashcam app that loops and locks clips |
Advertisement
The apps worth the space on the dashboard
Google Maps. The most accurate address data and live traffic, and it takes a handful of extra stops per route. It will not reorder twenty of them, which is where it stops being the right tool.
Waze. Better at the things drivers warn each other about: closures, hazards, speed cameras. Poor for multi-drop work, good for the long leg to the first job.
Route4Me. Built for exactly this: paste in the addresses and it produces an order that saves real time. The free tier is limited on stops per route, so check the number before relying on it.
RoadWarrior. The same job with a generous enough free allowance for a typical round, and it hands the optimised route to whichever navigation app you prefer.
HERE WeGo. Full offline maps by region including turn-by-turn, which is the fallback when the data drops out halfway down a lane.
Organic Maps. Small, fast, no account and no tracking, with house numbers on the map. The lightweight offline option, and a good second opinion on an address the main app cannot find.
OsmAnd. The most detailed offline maps available, including tracks, gates and building entrances. Fiddly to configure and unmatched once it is.
Sygic. Offline turn-by-turn with a large initial download. Worth it for anyone regularly working where coverage is unreliable.
TomTom GO. The one that takes vehicle dimensions and weight into account, so a van or a lorry is not routed under a low bridge or down a restricted street.
Parkopedia. Where to leave the vehicle near the drop, with prices and height restrictions. Data quality varies by city, so treat it as a shortlist rather than a guarantee.
Android Auto. If the vehicle supports it, this is the safety improvement rather than the convenience one: the phone stays in the mount and the next drop reads itself out.
Droid Dashcam. Turns the phone into a loop-recording dashcam with impact detection. Needs a mount, permanent power and a lot of free storage, and it has settled more disputes than any insurance document.
AutoBoy Dash Cam. The long-standing alternative, lighter on resources, with a background mode that keeps recording while you use navigation.
DailyRoads Voyager. Designed for long recordings: it manages storage by overwriting the oldest footage automatically, which is what makes a ten-hour shift practical.
Fuelio. A fuel log with consumption over time and community-entered prices. The consumption trend is the part that pays for itself, because it shows a problem developing before the vehicle does.
Drivvo. Mileage and running costs per vehicle, with reports that export. This is the app that makes the paperwork at the end of the year a half-hour job rather than a weekend.
Torque Lite. With a cheap plug-in adapter it reads the engine's own fault codes, so a warning light becomes a specific known problem before it becomes a breakdown on a shift.
Google Podcasts. Ten hours is a long time alone. Download episodes overnight rather than streaming them through a patchy signal.
Setting the cab up once
- Mount the phone on a vent, not the windscreen in the sun Heat is what stops a phone mid-shift. A vent mount in the shade, with the air on, keeps it working through an afternoon.
- Fit a charger that can outpace navigation and recording Navigation with the screen on and a dashcam recording will drain a phone faster than a weak charger can fill it. This surprises people in the second hour.
- Download every offline region you cover, once County or metropolitan level. Refresh every few months, from the house, on wifi.
- Put the day's stops into a route planner before setting off Five minutes in the yard is routinely half an hour saved on the road, and the order you would have guessed is rarely the good one.
- Turn off everything that speaks over the navigation Notification sounds from a dozen apps during a complicated junction is how mistakes happen. One voice at a time.
- Check the dashcam is still recording, weekly Silent failure is the normal failure mode: a full card, a permission revoked by an update, a mount that has worked loose. Check the last file plays.
- Offline maps for the whole patch
- A route planner for anything over ten stops
- A dashcam with automatic overwriting
- A running fuel and mileage log
- Three navigation apps talking at once
- Streaming music through a weak signal all day
- A phone flat on the windscreen in July
- Trusting parking data without looking
The record, and the year end
Whatever the arrangement with the platform or the employer, the mileage record is worth keeping yourself. An app that logs journeys and fuel takes a few seconds a day and produces an exportable file, and that file is what makes an accountant's questions easy to answer.
Dashcam footage is the same argument in a different form. Keep the card large enough that a full shift fits, know how the app locks a clip after an incident, and copy anything that matters off the phone the same evening. Loop recording will overwrite it otherwise, usually the following morning.
Offline maps for the patch, a planner for the order of the stops, a vent mount and a real charger, and a log you keep yourself. The platform app is the job list, nothing more.
Frequently asked questions
Can the main mapping app handle a round of twenty drops?
Not properly. It takes a limited number of additional stops and does not reorder them into a sensible route. For rounds beyond about ten stops a dedicated planner that hands off the route is a genuine time saving.
Is a phone good enough as a dashcam?
For a record of an incident, usually yes, provided it is powered, mounted where it does not overheat, and set to loop with automatic overwriting. A dedicated camera handles heat and parking mode better and does not stop when a call comes in.
How much storage does a shift of dashcam footage need?
It depends on the resolution, but a long shift at a moderate setting will fill several gigabytes an hour. Set the app to manage storage by overwriting the oldest files and give it a dedicated folder or card.
What is the fix for a phone that overheats every afternoon?
Shade first, then brightness, then resolution. Move it off the windscreen, point a vent at it, drop the screen brightness and reduce the dashcam recording quality. Cases come off too; they hold heat in.
Do fuel logging apps work out running costs automatically?
They calculate consumption and cost per distance from the entries you make, so the figures are only as good as the discipline of entering every fill. The useful output is the trend rather than any single number.
Read next
Nothing has infected your phone. Something you installed has permission, and the fix is a list in settings.
A phone will happily run a keyboard, a mouse and a memory stick. It will not power a desktop hard drive.
Hard and fast are different things. Almost every game confuses them, and these do not.
