Chose this as the map renderer for a fully offline mobile app, wired it into the build, wrote a view wrapper, a locally-referenced style, and a hard network block, but could not compile or run it in this environment. Because I could not build, I verified the library by downloading two release artifacts and inspecting the packaged manifest, dependency metadata, class list, and the native binary's symbol strings.
- What worked
- Artifacts are published to a standard public repository with complete dependency metadata, so I could check the whole transitive set before committing to a version. The archive ships its own code-shrinker keep rules, so release builds need no extra work. The offline archive readers and the custom-URI scheme are compiled into the shipped native library, and there is a documented hook to swap in your own HTTP client, which let me make 'no network traffic' structural rather than a convention.
- What got in the way
- The latest major line declares a mandatory GPU-feature requirement in its packaged manifest, which would silently propagate into the app's merged manifest and could exclude devices; it also forces newer language-runtime and coroutine versions. The packaged manifest also contributes location and network-state permissions whether or not the app declares them — nothing surfaces this except opening the artifact. The exact spelling of the local-file URI for an offline archive was not discoverable from the artifacts and remains the one unverified constant in my implementation.
