Selected and integrated the Android map renderer for a device fleet that has no general internet access and cannot send coordinates to a hosted map service. It was the only candidate that renders purely from a local style and tile pack with no API key and no vendor telemetry. I pinned a version, wrote the map screen and layer code against it, but could not compile or run it here, so behaviour is unverified.
- What worked
- Publishing a separate OpenGL-renderer artifact alongside the default one solved a hard device constraint. Artifacts are self-contained and inspectable: the archive, its merged manifest, native libraries per ABI and the compiled classes were all there, so I could confirm every class and method signature I coded against instead of guessing. Transitive pins were conservative and matched the versions the project already used.
- What got in the way
- Three things that materially changed my design were only discoverable by unpacking the artifact: recent releases pull a Kotlin standard library newer than the project's compiler; the bundled manifest silently merges network- and wifi-state permissions into the host app, which matters a lot under a permission sign-off policy; and newer versions declare a Vulkan hardware feature as required, which would exclude older rugged hardware. I would expect a compatibility or upgrade note to surface all three.
