- SignalDesk2 hr ago
Original Summary
MapLibre Compose is a Kotlin library for putting interactive vector maps in Compose Multiplatform apps on Android, iOS, desktop, and web. It's part of the MapLibre ecosystem, and isn't tied to any map provider; you point it at any MapLibre style and tile source: commercial, free, or your own.<p>- Docs: <a href="https://maplibre.org/maplibre-compose/" rel="nofollow">https://maplibre.org/maplibre-compose/</a><p>- Code: <a href="https://github.com/maplibre/maplibre-compose" rel="nofollow">https://github.com/maplibre/maplibre-compose</a><p>- Live demo: <a href="https://maplibre.org/maplibre-compose/demo/" rel="nofollow">https://maplibre.org/maplibre-compose/demo/</a><p>About two years ago, I started building a transit tracking app in Compose Multiplatform, and found there was no suitable map library for it with the level of customization I wanted. So, within my "train-tracking-app" repo, I started working on wrapping the MapLibre Android and iOS SDKs behind a common Compose API.<p>Around the same time, the StreetComplete folks and MapLibre Native folks were looking for the same thing: a Compose SDK for MapLibre Native. I spun my wrapper out into a library, and so began my two year yak shaving quest to bring MapLibre maps to Compose Multiplatform.<p>The SDK-wrapping approach got the first releases out quickly, but it didn't age well. I could only expose what both supported, and each had its own slightly different design and API contracts, as they were not designed to be used together. And there was no such sdk at all for desktop. I knew I needed to go a layer down, build on the MapLibre Native C++ core underpinning those Android and iOS SDKs. I first did this with JNI, on desktop only, with the help of GLM-4.5 to navigate some graphics work that I was deeply unfamiliar with. This worked, but JNI was tedious and bug-prone, AWT<>Compose interop was limited, and the work stalled. Around this time, I also onboarded the project into the MapLibre organization.<p>Earlier this year, I rebooted the native core wrapping effort. I designed a C API (<a href="https://github.com/maplibre/maplibre-native-ffi" rel="nofollow">https://github.com/maplibre/maplibre-native-ffi</a>) wrapping the MapLibre Native C++ core, generated safe(ish) language bindings on top for KMP and many other languages (first with LLMs, now working on deterministic codegen), and rebuilt MapLibre Compose for desktop, Android, and iOS on that foundation. This cleared numerous blockers and bugs, and allowed me to bring the library to a feature-complete state.<p>This work shipped in the StreetComplete iOS public beta recently (<a href="https://news.ycombinator.com/item?id=49920160">https://news.ycombinator.com/item?id=49920160</a>). Stadia's Ferrostar navigation SDK builds on it now too (<a href="https://stadiamaps.github.io/ferrostar/" rel="nofollow">https://stadiamaps.github.io/ferrostar/</a>).<p>It's pre-1.0. Android, iOS, and desktop wrap MapLibre Native. Kotlin/JS still wraps MapLibre GL JS, and Kotlin/Wasm support is awaiting Compose v1.13. If you're interested in building map apps with Compose, I encourage you to try this out and share feedback as I'm working on refining the api surface before stabilization.<p>Now, two years later, I'm getting back to working on my transit tracking app, which I hope to share on HN in a couple months.
- 情报分类：商业与市场研究
- 分类依据：内容涉及商业、投资或市场动态
- 信息来源：Hacker News 新项目
- 发布时间：2026/10/5 04:55:40
- No replies yet