Skip to main content
Your courier app starts Google Maps (or Waze) for a stop today. The truemetrics standalone navigation app takes the same call, drives the courier to the waypoint and into the parking, shows the walk to the entrance, and switches back to your app on arrival.
Four phones: the courier taps Navigate in the courier app, drives in the truemetrics navigation app with the last meter on the map, arrives and a Back button fills up, and is back in the courier app at the next stop.

The app switch: hand over the stop, drive, back to your app on arrival

What changes in your app

Three lines on the intent you already send. Google Maps ignores everything beyond the coordinate, so the same call works whether or not the truemetrics app is installed.
routeJson builds the tour as in route, from the IDs you send as metadata:

Without native code

Flutter, React Native or a web view can open a plain link instead of building an intent: every field is also a query parameter of the link, URL-encoded.
Shown on several lines for reading; the link itself is one line. Use the truemetrics.navigation:// scheme: it opens only the truemetrics app. google.navigation: may open Google Maps when both are installed.

Install the app

truemetrics provides the app (package io.truemetrics.navigation) for your devices, for example through your MDM. On first start it asks for location and, at the first drive, for notifications (Android 13+). The API key is set up by truemetrics; your courier app needs none.

The handover

The same link a courier app sends to Google Maps, google.navigation:q=<lat>,<lng>&mode=d, with the fields below as intent extras. Or, as a full link with every field a query parameter:
with route decoded:
q must be <lat>,<lng>, optionally followed by (label). An address instead of coordinates is rejected (no geocoding). Every field below except q can be an intent extra or a query parameter of the link (URL-encoded); an extra wins over a parameter of the same name. Extras are strings, except simulate (boolean, or the string "true"/"false").
string
required
The stop: <lat>,<lng> in WGS84 degrees, as for Google Maps. Used for routing and the map when there is no last meter for the stop.
string (JSON)
required
The tour and the stop to drive to. Brings the last meter and the address on the card. See route. Should it be missing or unreadable, the app still drives to q, but without a last meter.
string
Your app’s package name, to switch back to on arrival or Back. Brings your app to the front as a tap on its icon does.
string
A browsable deep link of your app, opened to switch back instead of returnApp, for example to land on the stop’s delivery screen: scanner://stop/2. file:, content:, intent: and android-app: links are ignored.

route

The whole tour (up to 200 stops) and which of its stops comes next:
The stop at next_stop is the one the courier is navigated to; send the whole tour all the same, the other stops are used as well. Other fields are ignored. A route that cannot be read, a next_stop outside the list or a stop with none of these fields counts as no route: the app drives to q without a last meter.

The switch back

With returnUri or returnApp, the app switches back 10 s after arrival, and its Back button does the same at any time. Whether arrival switches back by itself is part of the configuration truemetrics keeps for your key (on by default). The system Back ends the navigation like the Back button: to returnUri or returnApp, else to the app that was in front before. So that your app comes back as the courier left it, its launcher activity should be singleTask or singleTop, or use returnUri to a screen of your choice.

What the courier sees

  1. Route overview. The whole route and a Navigate button, which presses itself after 10 s.
  2. Drive. Turn-by-turn without voice, to the waypoint, then into the parking. Rerouting with real GPS (up to 5 times per drive by default). One card: address, time left, arrival time, Back.
  3. Near the stop. A flat view with parking, entrance, walk path and building; “Arriving” and the street replace the turn banner.
  4. Arrival. Within 30 m of the parking or entrance and slower than 15 km/h for 20 s, the Back button fills up over 10 s, then the app switches back.
The drive goes on with the phone locked or your app in front (a foreground service with a “Navigation is running” notification; a tap leads back). One handover runs at a time: a new one replaces the one before, also for the same stop.

Let an AI agent do it

Integrate the app switch with an AI agent: a copy-paste prompt that finds your app’s Google Maps call, asks you to confirm the mapping, and implements the handover.

For testing and demos

Leave these fields out in production. With them the app drives the route by itself, so a stop can be shown at a desk or in a customer meeting without driving there.
boolean
default:"false"
true: the app drives along the route by itself instead of following GPS, with arrival and the switch back as in a real drive. No rerouting.
string
Where the simulated drive starts: "<lat>,<lng>". Left out, at the device’s position. A few hundred metres before the stop, on the road leading in, shows the approach and the last meter in a minute.
A simulated handover from a computer, as your app would send it (without the simulate and simulationStart options it drives on GPS):
The truemetrics test app (“Scanner (test caller)”) hands over stops exactly like this, with a switch for the simulated drive.