maplibre · louwers · Oct 6, 2025 · Oct 6, 2025 · Oct 6, 2025 · Oct 6, 2025
diff --git a/src/content/roadmap/maplibre-native/action-journal/action-journal.png b/src/content/roadmap/maplibre-native/action-journal/action-journal.png
diff --git a/src/content/roadmap/maplibre-native/action-journal/index.mdx b/src/content/roadmap/maplibre-native/action-journal/index.mdx
@@ -0,0 +1,23 @@
+---
+title: Action Journal
+heroImage: "./action-journal.png"
+project: maplibre-native
+status: released
+released: "April 2025"
+---
+
+The Action Journal provides persistent logging of top-level map events to aid in debugging and observability.
+
+## Documentation
+
+### iOS
+
+- [Action Journal Example](https://maplibre.org/maplibre-native/ios/latest/documentation/maplibre-native-for-ios/actionjournalexample/)
+
+### Android
+
-### iOS
-
- [Action Journal Example](https://maplibre.org/maplibre-native/ios/latest/documentation/maplibre-native-for-ios/actionjournalexample/)
-
-### Android
+
+- [Action Journal Example](https://maplibre.org/maplibre-native/ios/latest/documentation/maplibre-native-for-ios/actionjournalexample/)
-### iOS
-
- [Action Journal Example](https://maplibre.org/maplibre-native/ios/latest/documentation/maplibre-native-for-ios/actionjournalexample/)
-
-### Android
+
+- [Action Journal Example](https://maplibre.org/maplibre-native/ios/latest/documentation/maplibre-native-for-ios/actionjournalexample/)
+- [Action Journal Example](https://maplibre.org/maplibre-native/android/examples/observability/action-journal/)
+
+## Implementation
+
+The Action Journal feature was implemented in [#3409](https://github.com/maplibre/maplibre-native/pull/3409) by Adrian Cojocaru.
diff --git a/...content/roadmap/maplibre-native/dynamic-texture-atlas/dynamic-texture-atlas.png b/...content/roadmap/maplibre-native/dynamic-texture-atlas/dynamic-texture-atlas.png
diff --git a/src/content/roadmap/maplibre-native/dynamic-texture-atlas/index.mdx b/src/content/roadmap/maplibre-native/dynamic-texture-atlas/index.mdx
@@ -0,0 +1,11 @@
+---
+title: Dynamic Texture Atlas
+heroImage: "./dynamic-texture-atlas.png"
+project: maplibre-native
+status: released
+released: "May 2025"
+---
+
+Instead of storing glyphs and icons per tile, store them in a dynamic texture atlas shared between all tiles. This allows for lower memory usage.
+
+This was implemented in [#3198](https://github.com/maplibre/maplibre-native/pull/3198).
-Instead of storing glyphs and icons per tile, store them in a dynamic texture atlas shared between all tiles. This allows for lower memory usage.
-
-This was implemented in [#3198](https://github.com/maplibre/maplibre-native/pull/3198).
+Instead of storing glyphs and icons per tile, we now store them in a dynamic texture atlas shared between all tiles.
+This allows for on average 4,5x lower memory usage in our benchmarks.
+
+This was implemented in [#3198](https://github.com/maplibre/maplibre-native/pull/3198) by Alex Cristici.
-Instead of storing glyphs and icons per tile, store them in a dynamic texture atlas shared between all tiles. This allows for lower memory usage.
-
-This was implemented in [#3198](https://github.com/maplibre/maplibre-native/pull/3198).
+Instead of storing glyphs and icons per tile, we now store them in a dynamic texture atlas shared between all tiles.
+This allows for significantly lower memory usage for glyphs and icons.
+
+This was implemented in [#3198](https://github.com/maplibre/maplibre-native/pull/3198) by Alex Cristici.
-Instead of storing glyphs and icons per tile, store them in a dynamic texture atlas shared between all tiles. This allows for lower memory usage.
-
-This was implemented in [#3198](https://github.com/maplibre/maplibre-native/pull/3198).
+Instead of storing glyphs and icons per tile, we now store them in a dynamic texture atlas shared between all tiles.
+This allows for on average 4,5x lower memory usage in our benchmarks.
+
+This was implemented in [#3198](https://github.com/maplibre/maplibre-native/pull/3198) by Alex Cristici.
-Instead of storing glyphs and icons per tile, store them in a dynamic texture atlas shared between all tiles. This allows for lower memory usage.
-
-This was implemented in [#3198](https://github.com/maplibre/maplibre-native/pull/3198).
+Instead of storing glyphs and icons per tile, we now store them in a dynamic texture atlas shared between all tiles.
+This allows for significantly lower memory usage for glyphs and icons.
+
+This was implemented in [#3198](https://github.com/maplibre/maplibre-native/pull/3198) by Alex Cristici.
diff --git a/src/content/roadmap/maplibre-native/lod/index.mdx b/src/content/roadmap/maplibre-native/lod/index.mdx
@@ -0,0 +1,11 @@
+---
+title: LOD Controls
+heroImage: "./lod.png"
+project: maplibre-native
+status: released
+released: June 2025
+---
+
+Level-of-detail (LOD) controls allow control over what zoom level is rendered for tiles that are further away. This is especially important for navigation use cases where the camera pitch can cause many tiles to be visible.
+
+Implemented in [#2958](https://github.com/maplibre/maplibre-native/pull/2958).
-Level-of-detail (LOD) controls allow control over what zoom level is rendered for tiles that are further away. This is especially important for navigation use cases where the camera pitch can cause many tiles to be visible.
-
-Implemented in [#2958](https://github.com/maplibre/maplibre-native/pull/2958).
+Level-of-detail (LOD) controls allow control over what zoom level is rendered for tiles that are further away.
+This is especially important for navigation use cases where the camera pitch can cause many tiles to be visible.
+
+Developers can now dynamically adjust the zoom level of tiles based on runtime conditions, such as drops in FPS or camera tilt during active navigation.
+For example, tiles farther from the camera can automatically use lower zoom levels when the screen is tilted, ensuring smooth performance on large display infotainment devices without compromising the user experience.
+
+Implemented in [#2958](https://github.com/maplibre/maplibre-native/pull/2958) by [@alasram](https://github.com/alasram).
-Level-of-detail (LOD) controls allow control over what zoom level is rendered for tiles that are further away. This is especially important for navigation use cases where the camera pitch can cause many tiles to be visible.
-
-Implemented in [#2958](https://github.com/maplibre/maplibre-native/pull/2958).
+Level-of-detail (LOD) controls allow control over what zoom level is rendered for tiles that are further away.
+This is especially important for navigation use cases where the camera pitch can cause many tiles to be visible.
+
+Developers can now dynamically adjust the zoom level of tiles based on runtime conditions, such as drops in FPS or camera tilt during active navigation.
+For example, tiles farther from the camera can use lower zoom levels when the screen is tilted, ensuring smooth performance on large display infotainment devices without compromising the user experience.
+
+Implemented in [#2958](https://github.com/maplibre/maplibre-native/pull/2958) by [@alasram](https://github.com/alasram).
-Level-of-detail (LOD) controls allow control over what zoom level is rendered for tiles that are further away. This is especially important for navigation use cases where the camera pitch can cause many tiles to be visible.
-
-Implemented in [#2958](https://github.com/maplibre/maplibre-native/pull/2958).
+Level-of-detail (LOD) controls allow control over what zoom level is rendered for tiles that are further away.
+This is especially important for navigation use cases where the camera pitch can cause many tiles to be visible.
+
+Developers can now dynamically adjust the zoom level of tiles based on runtime conditions, such as drops in FPS or camera tilt during active navigation.
+For example, tiles farther from the camera can automatically use lower zoom levels when the screen is tilted, ensuring smooth performance on large display infotainment devices without compromising the user experience.
+
+Implemented in [#2958](https://github.com/maplibre/maplibre-native/pull/2958) by [@alasram](https://github.com/alasram).
-Level-of-detail (LOD) controls allow control over what zoom level is rendered for tiles that are further away. This is especially important for navigation use cases where the camera pitch can cause many tiles to be visible.
-
-Implemented in [#2958](https://github.com/maplibre/maplibre-native/pull/2958).
+Level-of-detail (LOD) controls allow control over what zoom level is rendered for tiles that are further away.
+This is especially important for navigation use cases where the camera pitch can cause many tiles to be visible.
+
+Developers can now dynamically adjust the zoom level of tiles based on runtime conditions, such as drops in FPS or camera tilt during active navigation.
+For example, tiles farther from the camera can use lower zoom levels when the screen is tilted, ensuring smooth performance on large display infotainment devices without compromising the user experience.
+
+Implemented in [#2958](https://github.com/maplibre/maplibre-native/pull/2958) by [@alasram](https://github.com/alasram).
diff --git a/src/content/roadmap/maplibre-native/lod/lod.png b/src/content/roadmap/maplibre-native/lod/lod.png
diff --git a/src/content/roadmap/maplibre-native/long-running-test/desert-bus.png b/src/content/roadmap/maplibre-native/long-running-test/desert-bus.png
diff --git a/src/content/roadmap/maplibre-native/long-running-test/index.mdx b/src/content/roadmap/maplibre-native/long-running-test/index.mdx
@@ -0,0 +1,17 @@
+---
+title: Long Running Test
+heroImage: "./desert-bus.png"
+project: maplibre-native
+status: released
+released: August 2025
+---
+
+Some of our users run MapLibre Native for many hours, sometimes days on end. To ensure stability, we wanted to develop a long running test. We are distributing this test so that everyone can run it with hardware they have laying around.
+
+Implementation Android in [#3512](https://github.com/maplibre/maplibre-native/pull/3512). See the [latest releases](https://github.com/maplibre/maplibre-native/releases?q=android-testapp&expanded=true) on GitHub.
+
+A similar test for iOS will be available [soon](https://github.com/maplibre/maplibre-native/pull/3592).
+
+---
+
+After a vote by the developers, this ‘long running test’ is was officially called Desert Bus, named after a game from the 90’s where you had to drive a bus from Arizona to Nevada (an exciting 8 hour playthrough can be found on [YouTube](https://www.youtube.com/watch?v=2LtiHla1dNg)).
-Some of our users run MapLibre Native for many hours, sometimes days on end. To ensure stability, we wanted to develop a long running test. We are distributing this test so that everyone can run it with hardware they have laying around.
-
-Implementation Android in [#3512](https://github.com/maplibre/maplibre-native/pull/3512). See the [latest releases](https://github.com/maplibre/maplibre-native/releases?q=android-testapp&expanded=true) on GitHub.
-
-A similar test for iOS will be available [soon](https://github.com/maplibre/maplibre-native/pull/3592).
-
---
-
-After a vote by the developers, this ‘long running test’ is was officially called Desert Bus, named after a game from the 90’s where you had to drive a bus from Arizona to Nevada (an exciting 8 hour playthrough can be found on [YouTube](https://www.youtube.com/watch?v=2LtiHla1dNg)).
+Some of our users run MapLibre Native for many hours, sometimes days on end.
+To ensure stability, we developed a long running test.
+We are distributing this test so that everyone can run it with hardware they have laying around.
+
+After a vote by the developers, this ‘long running test’ is was officially called Desert Bus, named after a game from the 90’s where you had to drive a bus from Arizona to Nevada (an exciting 8 hour playthrough can be found on [YouTube](https://www.youtube.com/watch?v=2LtiHla1dNg)).
+
+Please head over to [our testapp releases on GitHub](https://github.com/maplibre/maplibre-native/releases?q=android-testapp&expanded=true) to help us gain test data.
+
+Implementation Android in [#3512](https://github.com/maplibre/maplibre-native/pull/3512) by Adrian Cojocaru.
+
+A similar test for iOS will be available [soon](https://github.com/maplibre/maplibre-native/pull/3592).
-Some of our users run MapLibre Native for many hours, sometimes days on end. To ensure stability, we wanted to develop a long running test. We are distributing this test so that everyone can run it with hardware they have laying around.
-
-Implementation Android in [#3512](https://github.com/maplibre/maplibre-native/pull/3512). See the [latest releases](https://github.com/maplibre/maplibre-native/releases?q=android-testapp&expanded=true) on GitHub.
-
-A similar test for iOS will be available [soon](https://github.com/maplibre/maplibre-native/pull/3592).
-
---
-
-After a vote by the developers, this ‘long running test’ is was officially called Desert Bus, named after a game from the 90’s where you had to drive a bus from Arizona to Nevada (an exciting 8 hour playthrough can be found on [YouTube](https://www.youtube.com/watch?v=2LtiHla1dNg)).
+Some of our users run MapLibre Native for many hours, sometimes days on end.
+To ensure stability, we developed a long running test.
+We are distributing this test so that everyone can run it with hardware they have laying around.
+
+After a vote by the developers, this ‘long running test’ is was officially called Desert Bus, named after a game from the 90’s where you had to drive a bus from Arizona to Nevada (an exciting 8 hour playthrough can be found on [YouTube](https://www.youtube.com/watch?v=2LtiHla1dNg)).
+
+Please head over to [our testapp releases on GitHub](https://github.com/maplibre/maplibre-native/releases?q=android-testapp&expanded=true) to help us gain test data.
+
+Implementation Android in [#3512](https://github.com/maplibre/maplibre-native/pull/3512) by Adrian Cojocaru.
+
+A similar test for iOS will be available [soon](https://github.com/maplibre/maplibre-native/pull/3592).
diff --git a/src/content/roadmap/maplibre-native/mlt-integration/image.png b/src/content/roadmap/maplibre-native/mlt-integration/image.png
diff --git a/src/content/roadmap/maplibre-native/mlt-integration/index.mdx b/src/content/roadmap/maplibre-native/mlt-integration/index.mdx
@@ -0,0 +1,10 @@
+---
+title: MLT Integration
+heroImage: "./image.png"
+project: maplibre-native
+status: in-progress
+---
+
+Add support for reading vector-tile sources in the [MapLibre Tile Format](https://github.com/maplibre/maplibre-tile-spec) (MLT).
-Add support for reading vector-tile sources in the [MapLibre Tile Format](https://github.com/maplibre/maplibre-tile-spec) (MLT).
+Add support for reading vector-tile sources in the [MapLibre Tile Format](https://github.com/maplibre/maplibre-tile-spec) (MLT).
+MLT is a next-generation tile format and a successor to MVT.
+Our early benchmarks show 2-6x smaller tiles and some decoding benefits.
-Add support for reading vector-tile sources in the [MapLibre Tile Format](https://github.com/maplibre/maplibre-tile-spec) (MLT).
+Add support for reading vector-tile sources in the [MapLibre Tile Format](https://github.com/maplibre/maplibre-tile-spec) (MLT).
+MLT is a next-generation tile format and a successor to MVT.
-Add support for reading vector-tile sources in the [MapLibre Tile Format](https://github.com/maplibre/maplibre-tile-spec) (MLT).
+Add support for reading vector-tile sources in the [MapLibre Tile Format](https://github.com/maplibre/maplibre-tile-spec) (MLT).
+MLT is a next-generation tile format and a successor to MVT.
+Our early benchmarks show 2-6x smaller tiles and some decoding benefits.
-Add support for reading vector-tile sources in the [MapLibre Tile Format](https://github.com/maplibre/maplibre-tile-spec) (MLT).
+Add support for reading vector-tile sources in the [MapLibre Tile Format](https://github.com/maplibre/maplibre-tile-spec) (MLT).
+MLT is a next-generation tile format and a successor to MVT.
+
+As of October 2025, MLT integration is in an advanced stage. See [#3246](https://github.com/maplibre/maplibre-native/pull/3246) for the current status.
diff --git a/src/content/roadmap/maplibre-native/plugin-api/image.jpg b/src/content/roadmap/maplibre-native/plugin-api/image.jpg
diff --git a/src/content/roadmap/maplibre-native/plugin-api/index.mdx b/src/content/roadmap/maplibre-native/plugin-api/index.mdx
@@ -0,0 +1,14 @@
+---
+title: Plugin API
+heroImage: "./image.jpg"
+project: maplibre-native
+status: in-progress
+---
+
+We are experimenting with various ways to add plugins for extending MapLibre Native.
-We are experimenting with various ways to add plugins for extending MapLibre Native.
+We are currently experimenting with various ways to add plugins for extending MapLibre Native.
-We are experimenting with various ways to add plugins for extending MapLibre Native.
+We are currently experimenting with various ways to add plugins for extending MapLibre Native.
+
+[Plugin Layers](https://maplibre.org/maplibre-native/ios/latest/documentation/maplibre-native-for-ios/pluginlayers) allow custom rendering to intergrate with custom style layers (as of October 2025, only available for iOS).
-[Plugin Layers](https://maplibre.org/maplibre-native/ios/latest/documentation/maplibre-native-for-ios/pluginlayers) allow custom rendering to intergrate with custom style layers (as of October 2025, only available for iOS).
+[Plugin Layers](https://maplibre.org/maplibre-native/ios/latest/documentation/maplibre-native-for-ios/pluginlayers) allow custom rendering to intergrate with custom style layers.
+As of October 2025 they are available for iOS.
-[Plugin Layers](https://maplibre.org/maplibre-native/ios/latest/documentation/maplibre-native-for-ios/pluginlayers) allow custom rendering to intergrate with custom style layers (as of October 2025, only available for iOS).
+[Plugin Layers](https://maplibre.org/maplibre-native/ios/latest/documentation/maplibre-native-for-ios/pluginlayers) allow custom rendering to intergrate with custom style layers.
+As of October 2025 they are available for iOS.
+
+See [#3703](https://github.com/maplibre/maplibre-native/pull/3703) for other suggested plugin APIs.
+
+Meta developed a cross-platform plugin API that allows extending MapLibre Native with plugins written in C++. They have pledged to upstream this work.