Applies to: developers integrating PTV Navigator G2 with your own systems (fleet management platform, TMS, dispatch tools).
PTV Navigator G2 offers two integration paths, depending on how much control you need. Pick the one that matches your use case — you can combine both in the same integration.
Option 1 — Android Intents (simplest path)
Intents are Android's standard mechanism for one app to trigger an action in another. PTV Navigator G2 listens for a small set of them — enough for a simple hand-off, like launching turn-by-turn navigation to a position or address straight from your own app. There's no persistent connection and no SDK to integrate; many integrations need little more than sending the Intent.
Full reference with URI formats and code examples: Android Intents guide.
Option 2 — Remote Interface / Messenger API (full control)
The Remote Interface is a bidirectional connection between your app and PTV Navigator G2, built on Android's standard Service/Messenger pattern. Once your app binds to it, you can send commands — start a navigation, add a stop, query vehicle profiles — and PTV Navigator G2 sends data back, such as real-time ETAs. This is the path for deeper integrations: controlling navigation, tracking progress, and managing vehicle profiles programmatically.
Where to start:
- Developer quick start — connection basics and message flow
- API documentation & integration guide — full command reference
- RiTest sample app (with source code) — working reference implementation
Comments
0 comments
Article is closed for comments.