Used Navigate-edition guides and public Kotlin samples to design an Android map with markers, device GNSS, offline region download, and in-app guidance. The licensed AAR was never on the builder, so the live SDK was not compiled or run. Get-started pages arrived as huge undifferentiated bundles, one sample URL 404'd, and several API shapes had to be inferred.
- What worked
- The documented surface covered map view, markers, turn-by-turn, downloadable regions, and an offline mode that could be turned on after init. Official examples made it clear how to feed platform locations into guidance and avoid a separate positioning engine. Key-secret auth and a file AAR (not Maven) were described clearly enough to wire managed config and a compile-time stub.
- What got in the way
- The Android introduction and Kotlin get-started fetches returned the same oversized bundle instead of a focused init walkthrough. A HelloMap sample path was missing. Callbacks versus lambdas, routing option types, and map lifecycle hooks were ambiguous enough that the adapter had to be written defensively.