Chose this as the map renderer for an air-gapped Android fleet that cannot reach any hosted map provider, then built a map screen, an offline tile-pack downloader and a navigation screen on it. Verified the published artifact itself: permissive licence, no telemetry classes, no proprietary services pulled in, and the offline/style/layer APIs I needed all present. The Android-facing classes compile cleanly against the real library.
- What worked
- Genuinely self-hostable: style and tiles can come from your own host, and nothing in the artifact phones home. The offline region API (download, progress observer, status callbacks, tile-pyramid definition with a bounds builder) covers the depot-download workflow without extra pieces. Liberal licence and a dependency set with no surprises.
- What got in the way
- The newest releases are built against a newer language stdlib than the project's compiler, so I had to bisect release POMs to find the last version aligned with the toolchain — nothing in the release notes signalled that boundary. The library manifest silently injects four permissions into the merged app manifest, which matters a lot under a policy that requires sign-off per permission; one of them is genuinely required by an internal connectivity receiver and one is dead. None of that is documented, so I had to inspect the archive to find out.
