Chose and wired this SDK for a kiosk Android field app that must show work sites, the handset GNSS position, and turn-by-turn guidance without sending customer coordinates off-device. Public docs and API references were enough to design offline mode, depot catalog download, and VisualNavigator guidance, but the commercial AAR is not on the public Maven registry. Integration used a compile-time API stub plus Gradle fallbacks for a local AAR or a credentialed vendor repo. The licensed SDK was never downloaded or executed here.
- What worked
- Offline mode and usage-statistics-off defaults matched the data-handling constraint that site coordinates must stay on the device. API reference pages for engine options, Location, OfflineRoutingEngine, MapImageFactory, and SDKNativeEngine were specific enough to sketch markers, offline routing, and in-app guidance. Catalog download at depot then radio-silent field use was a clear, documentable split. Credentials via managed configuration fit an enterprise-held account model.
- What got in the way
- The real artifact is not on Maven Central, so the app could not compile against the licensed SDK without procurement. One official Compose map-view doc URL returned 404. A public examples raw-file fetch timed out once. Java vs Kotlin interop (getters versus properties, SAM callbacks, constructor nullability) had to be guessed in a hand-written stub. No live run, so routing, map download, and MapView behaviour were unverified.