In-Car Delivery App: Running Delivery Routes From the Car Browser
Most couriers already have a screen in front of them that is bigger, brighter and better mounted than their phone: the car's own display. EfiRoute Drive is a delivery dashboard built for that screen — standard HTML5, no vendor SDK, no app store. The driver opens efiroute.com/driver/drive in the car browser, signs in once, and sees the live route on one half of the screen and the map on the other. Deliveries, cash collection, failure reasons and ETA all run through the same EfiRoute backend the phone app uses.
Phones are a compromise in a delivery vehicle. They sit in a cheap cradle, they overheat in summer, they ring while you are reversing, and the one screen you actually want to glance at — the car's own display — sits there showing the radio. Since 2020, most new vehicles ship with a full Chromium-based web browser on that display. That is enough to run a real delivery dashboard, and that is exactly what EfiRoute Drive does.
EfiRoute Drive at a glance.
What is an in-car delivery app?
An in-car delivery app is a driver dashboard that runs inside the web browser already built into the vehicle, instead of on a phone or a dedicated handheld. There is no installation and no vendor partnership: if the browser can render a modern web page, it can render the dashboard. Everything the driver needs — the ordered stop list, the map, the next address, the ETA, the buttons to mark a delivery done — is served over HTTPS from the same platform the dispatcher uses.
Crucially, it is not a second delivery system. EfiRoute Drive talks to the same courier API as the Android, iOS, Wear OS and Apple Watch apps, so a stop marked delivered in the car instantly shows as delivered in the office, in the customer's tracking link and in the reports. A driver can start the day on the car screen and finish it on the phone without anything being out of sync.
Who actually benefits from this?
The car screen is not automatically better than a phone. It wins in a few specific situations — and those situations cover a large share of real delivery work:
A 40-stop day means 40 glances at the next address. A 10-inch dashboard screen at eye level beats a phone in a cradle every time, and it is never in the wrong pocket.
No MDM, no app rollout, no "which version are you running?". The driver opens a URL in the vehicle that is already assigned to them and signs in with the credentials they already have.
Drivers change shift, vehicles stay. Because there is nothing installed, signing out is enough — the next driver signs in with their own account and sees their own route.
Routes optimized in the office with the Google Cloud engine appear on the car screen without any extra setup, licence or per-seat fee.
How the screen is laid out
Car displays are wide and short, and they are touched by someone whose attention belongs on the road. So the layout is deliberately boring: the left third is the work (the active stop as a large card, then the remaining stops), the right two thirds are the map with the real route line, the pins and the driver position. A top bar carries only what you might need to glance at — connection state, GPS state, how many stops are left, how many are done, and the time.
Buttons are large, high-contrast and few. The dashboard switches automatically between vehicle, tablet and desktop layouts based on the screen it finds itself on, and the driver can pin a layout manually if the automatic guess is wrong for their car. On narrow screens the two panels become two tabs instead of shrinking into uselessness.
How a driver gets started
The whole setup is a URL and a login, once per driver and vehicle:
- 1Open the browser in the car
On most vehicles the browser is in the app drawer or the media screen. Open efiroute.com/driver/drive and bookmark it — on Tesla you can pin it to the launcher.
- 2Sign in as a courier
The same courier e-mail, project number and password used in the mobile app. The session lasts 30 days, so this is a once-a-month action, not a daily one.
- 3Allow location once
The dashboard asks twice on purpose: once for the browser permission to read GPS, once for your consent to share it with dispatch. Decline and the route, map and delivery buttons still work.
- 4Drive the route
Tap “Start driving” on a stop and the customer gets a tracking link automatically. Navigation hands off to the car navigation or Google Maps; if the browser blocks that, the in-app map takes over.
- 5Close out each stop
Delivered, with payment method and the amount collected on a big keypad — or a failure reason from a list. Both land on the stop record in the office immediately.
Nothing is stored on the car beyond the login session and two preferences (voice on/off, chosen layout). Signing out of the driver menu removes them, which matters on a vehicle used by several people.
Driving safety: what the dashboard refuses to do
A delivery screen that demands typing at 80 km/h is a hazard, and no amount of product polish fixes that. EfiRoute Drive handles it with a few hard rules:
Above roughly 10 km/h the detailed actions lock themselves and the screen reduces to the next stop, its ETA and a navigation button.
A GPS speed of zero is not treated as proof that the vehicle is parked — a red light reads the same as a parking space. The lock only opens when the driver confirms it.
When the vehicle moves again, the lock comes back on its own; one confirmation does not cover a whole shift.
The dashboard never tries to work around the manufacturer's own restrictions on what a car browser may do while driving.
Voice announcements exist for the same reason: a new delivery, an approaching stop or a cancelled order is spoken aloud with a short chime, so the driver can keep their eyes up. They use the browser speech synthesis and can be switched off in one tap.
What car browsers cannot do (and how the dashboard copes)
An honest in-car app has to be built around the limits of the platform rather than pretending they are not there:
Close the browser tab and nothing runs. Live location only flows while the dashboard is open, so a fleet that needs all-day tracking should keep the phone app running in parallel.
A car browser cannot wake itself up. New stops appear through a realtime connection while the screen is open, with polling as a fallback — but a driver with the tab closed learns about a new delivery from the phone.
Some vehicles suspend the browser when the car is locked or the trip ends. The session survives, so reopening the page restores the route exactly where it was.
Most car browsers have no camera access, so photo proof of delivery stays a phone job. Calling and SMS links work on tablets and phones, and are simply ignored where the platform has no dialler.
Car browser vs phone app vs the classic web view
EfiRoute gives couriers three front ends. They are complementary, not competing — and the honest comparison looks like this:
| Capability | Car browser (Drive) | Phone app | Classic web view |
|---|---|---|---|
| Large, glanceable layout for driving | ✓ | ~ | ✕ |
| Background location all day | ✕ | ✓ | ✕ |
| Live route, ETA and status updates | ✓ | ✓ | ✓ |
| Voice announcements | ✓ | ~ | ✕ |
| Photo proof of delivery | ✕ | ✓ | ✕ |
| Works with nothing installed | ✓ | ✕ | ✓ |
✓ full support · ~ partial or device-dependent · ✕ not available.
Frequently asked questions
Which cars does EfiRoute Drive work in?
Any vehicle whose built-in browser is reasonably modern — in practice the Chromium-based browsers in Tesla, Mercedes-Benz MBUX, BMW iDrive 8/9, Volkswagen, Volvo and Polestar. There is no vendor integration and no certification, so the answer is simply "does the browser open the page?". The same dashboard also runs on tablets and desktops.
Is this a Tesla app?
No. Tesla happens to have the best-known car browser, but nothing in EfiRoute Drive is Tesla-specific and no Tesla API is used. It is a standard web page and it is tested across screen sizes rather than across brands.
Does the driver need to install anything?
No. There is nothing in any app store for the car, and no software is side-loaded. A bookmark in the car browser is the whole installation.
What happens when the car loses mobile data?
The dashboard tells the driver that the connection dropped and keeps showing the route it already has. When data returns it resyncs with the server automatically, and repeated taps cannot send the same delivery twice.
Can the driver still take cash in the car?
Yes. Payment method and collected amount are entered on a large on-screen keypad and recorded against the stop, in the currencies the company has enabled. The money side is calculated by the backend, exactly as it is for the phone app.
Does it cost extra?
No. EfiRoute Drive is part of the platform: it is included on the free plan and on Pro, with no per-driver or per-screen fee.