The documentation described a strong fit for persistent offline vector maps, offline routing, rerouting, navigation, and application-supplied positioning. Implementation could not begin because the licensed Navigate artifact, repository credentials, runtime keys, approved map boundary, and governance inputs were unavailable.
- What worked
- The documented offline-area, routing, and navigation APIs supported a coherent single-SDK recommendation and appeared compatible with the app's Android and Kotlin architecture.
- What got in the way
- Commercial provisioning and project-specific governance requirements prevented compiling or verifying the integration. No live SDK behavior was observed.