I've just released <v0.16.0 of MapLibre Compose>, ...

# feed

[Sargun Vohra]

I've just released v0.16.0 of MapLibre Compose, a library for adding interactive vector maps to your Compose Multiplatform apps.

The last release laid the groundwork for API refinements; this release delivers them. Highlights:
• An imperative styling API for inspecting and modifying sources, layers, and images, including those in the base style
• Unified MapState that can be held in a ViewModel, with reusable composable styling for maps and snapshots
• Map image capture on all platforms, plus Android Surface support for integrations like Android Auto
• Overhauled input configuration, including keyboard and rotary controls, configurable momentum, bearing snapping, and haptics
• Request customization hooks, clearer location and heading APIs, and plenty of fixes
• New Wear OS, Android TV, and Android Auto demos
This release includes substantial breaking API changes. See the release notes for the upgrade guide from v0.15.0, or the Getting Started guide to start fresh. You can also try the live demo in your browser, with 3D buildings, transit route overlays, data visualization, and draggable markers. It's the same shared demo app that runs on Compose for Android, iOS, and desktop.

This is a significant milestone for the project; this is the first release where I can say the full MapLibre Native API surface is now available via the Compose SDK. It's also the first time the open issue count is smaller than it was when I first booted up the project in November of 2024.

There's still some stabilization ahead, and still some smaller gaps to fill, and one more Compose target to support, but in my mind the library has finally graduated out of the "experimental" stage. It is in roughly the same shape it will be in for a future v1.0 release.

[Tgo1014]

Hey! Just want to thank for all the work done into this, that's such a great library!
Do you think the wasm improve even more the performance or should be negligible?

[Sargun Vohra]

Kotlin Wasm won't improve performance of the map itself, that'll use the same underlying MapLibre GL JS renderer.

It will improve performance of the Compose UI app though, and probably some small improvement in how MapLibre Compose orchestrates the map and style composition.

[Michael Paus]

Many thanks also from my side ❤️. We are just in the process of switching from the snapshots to the released version.

[Sargun Vohra]

Thanks for testing the snapshots! v0.16 did a ton of work on the internal map lifecycle and your testing helped build confidence in that

[Nish]

This is super amazing!!!