Not sure which integration path fits your situation? See if one of these sounds familiar:
| Use case | Option |
|---|---|
| "We just want routes optimised, fast, with minimal engineering effort." | → Driver App. Install the Bettermile Driver App, connect your Data Gateway connector, and you're done, no backend integration beyond that. |
| "Our drivers already carry a handheld scanner for parcel scanning, and we want a second screen rather than a second device." | → Run the Bettermile Driver App alongside your existing scanner or loading app on the same device, with the App-to-App Library keeping them in sync. |
| "We have our own driver app and want full control over the experience, or just want to enhance our own sequence optimisation." | → Deep Integration. Call the Better Route API directly from your backend, and build (or keep) the driver-facing UI yourself. |
| "We also need in-house turn-by-turn navigation and multi-country address handling." | → Add the Navigation SDK and Address Formatter Kotlin on top of a Deep Integration. See further extension options; add either, both, or neither. |
| "We want the tool to fit real driver habits, not the other way around." | → Extended use cases for the Better Route API: choose the first waypoint, set custom timeframes and stop times, add your own jobs, and define custom destinations and waypoints. |
| "We want reliable consignee ETAs." | → Feed Better Tracking - Live with actual and predicted sequences in real time, narrowing ETA windows accurately. |
| "We need routing that factors in OOH infrastructure, lockers and pickup points built into the sequence." | → Driver App. Install the Bettermile Driver App, and you're done, we support this out of the box. |
See Integration Options for the full side-by-side comparison, or the FAQ for quick answers.