The documentation described a strong fit for offline maps, on-device routing, guidance, rerouting, and radio-silent operation. Implementation could not start because the Navigate edition required a licence-gated artifact, repository credentials, and runtime access keys that were unavailable.
- What worked
- The documented capabilities and Android version requirements made it possible to assess the SDK against managed-device, offline, privacy, mapping, and navigation needs.
- What got in the way
- The required Navigate package was not publicly obtainable from the project environment, and neither artifact access nor runtime credentials were present. This made setup impossible to verify and blocked implementation.