The main idea
Most navigation apps can only navigate to a generic coordinate. They do not know where couriers really park, which door they really use, or how they walk from one to the other. That is the last meter, and it is where couriers lose time searching. truemetrics learns the last meter from your couriers’ own deliveries (recorded by the truemetrics SDK, keyed by the address IDs you send as metadata). For every stop it knows:- Waypoint: where the approach leaves the street. A navigation should route here, not to the address pin.
- Parking: where couriers really park, reached from the waypoint.
- Entrance: the door that is really used.
- Walk path: the way on foot from the parking to the entrance.
- Building: the building the entrance belongs to.
Five ways to use it
You decide how the last meter reaches the courier: as data in your own map (option 1), or with the truemetrics last meter module inside your app, which brings the map, the routing and the best practices with it (option 2), or with the truemetrics standalone navigation app instead of Google Maps or Waze (option 3).Where the last meter comes from, and who draws it
1A · Your map, data from your backend
truemetrics exports parking places, entrances, waypoints and walk paths to your backend. Your
backend hands them to the courier app with the tour, your map draws them.
1B · Your map, data from the REST API
Your app asks the truemetrics REST API per stop and gets ready-styled GeoJSON (or a PNG) for
your own map.
2 · Module in your app
The truemetrics module shows the stop’s last meter and the courier’s position inside your app.
Point-to-point navigation can be off (your navigation stays as it is) or on (turn-by-turn to the
waypoint, into the parking, arrival at the door): one flag,
routing.3 · Standalone navigation app
The truemetrics standalone navigation app replaces Google Maps or Waze. Your courier app sends
the stop as it does to Google Maps and gets the courier back on arrival.
Comparison
| 1A own map, own backend | 1B own map, REST API | 2 module in your app | 3 standalone app | |
|---|---|---|---|---|
| Integration effort | ●●●●● | ●●●●○ | ●●○○○ | ●○○○○ |
| You build | Import, delivery to devices, map, styling | Map, styling, one request per stop | A place in your screen | Extras on your Google Maps call |
| Best practices | Yours to implement | Yours to implement; styling hints included | Built in; with navigation on, plus routing to the parking | Built in, plus the way back |
| Routing | Your own | Your own | Off: your own On: truemetrics routing* | truemetrics routing* |
| Flexibility | Full | Full | Your screen, truemetrics map | None |
| Control | ●●●●● | ●●●●○ | Off: ●●●○○ On: ●●○○○ | ●●○○○ |
| Platforms | Any | Any | Android | Android |
Which one fits
- You keep your navigation (Google Maps, HERE, your own) and your own map, with full control over data and design: 1A, if your backend already distributes tours to the devices; 1B, if the app may ask truemetrics directly.
- You want the last meter shown the way couriers read it best, inside your own app, with little work: 2. Point-to-point navigation off, next to the navigation you have; on, navigation made for the last meter inside your app.
- Your couriers drive with Google Maps or Waze today: 3. The fewest changes, and the courier gets routing to the parking, the walk to the entrance and the way back to your app.
What every option needs
1
truemetrics SDK in your courier app
The last meter is learned from your own deliveries: record with the truemetrics SDK and send one
metadata event per delivery with a stable
address_id. See Integrate with an AI agent.2
An API key
Your truemetrics contact issues it and enables it for the options you use. It scopes all data to
your account.
3
Your stop identifiers
Each stop is looked up by the
address_id you send as metadata: typically your address
identifier or route point identifier.