Chose this SDK because it is the only mainstream mapping option where basemap, geocoder and routing network can all live in a single on-device package with no runtime call home, which a strict no-external-endpoint device policy required. Integrated map display, device location and route solving against a mobile map package, and compiled the SDK-facing code against the real published artifact.
- What worked
- Sample pages for map-from-package, routing and device location gave accurate, copy-able API shapes. Artifacts resolved cleanly from the vendor Maven repository and carried their own consumer shrinker rules and no extra manifest permissions, so nothing unexpected merged into the app. Code written from the samples compiled with zero errors or warnings against the real library jar.
- What got in the way
- Licence-level documentation was vague about exactly which capability needs which tier, especially for local-network routing versus analysis extensions, so I had to cross-read three pages and still flag it for human confirmation. System-requirements pages render client-side, so minimum API level had to be read out of the packaged manifest instead. The licence-apply call returns a nullable result that the docs do not emphasise; a first draft dereferenced it and only the compile caught it. Native libraries for four architectures are very large, so an architecture filter is effectively mandatory.