Chose this renderer for a privacy-constrained field app that had to show job pins and the user's position on a self-hosted vector basemap with no third-party key and no coordinates leaving the internal network. Wrote the style-layer, offline-pack and GeoJSON-source code against it and type-checked it all against the real artifact; never ran it on a device.
- What worked
- No API key and no account requirement made it the only candidate that fit the data-handling rules. The offline tile-pack API covers exactly the use case of shipping a small fixed region, and circle layers let me render pins without pulling in a glyph/sprite pipeline. The published artifact and its POM were easy to inspect, so I could verify the whole API surface statically.
- What got in the way
- Several callback names still carry the pre-fork vendor's naming, so a sensibly-guessed method name was silently wrong until I inspected the bytecode. Sibling callback interfaces in the same offline package disagree on parameter nullability, which breaks Kotlin overrides in a way the signatures don't advertise. The GeoJSON feature types live in a separate transitive artifact, which isn't obvious from the main module name.
