Add additional roadmap items MapLibre Native #480
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CommanderStorm
approved these changes
Oct 6, 2025
Member
CommanderStorm
left a comment
CommanderStorm
left a comment
There was a problem hiding this comment.
I have a few rewordings, most of them to make the engineering-heavy text a bit more than one sentence each 😉
|
|
||
| We are 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). |
Member
There was a problem hiding this comment.
Suggested change
| [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. |
Member
Author
There was a problem hiding this comment.
If you put it on a separate line it is not clear what it belongs to. Maybe sections:
Plugin Layers
Plugin Layers allow custom rendering to intergrate with custom style layers.
As of October 2025, available for iOS.
Other Plugin APIs
See #3703 for other suggested plugin APIs.
Cross-Platform Plugins
Meta developed a cross-platform plugin API that allows extending MapLibre Native with plugins written in C++. They have pledged to upstream this work.
Comment on lines
+9
to
+11
| 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). |
Member
There was a problem hiding this comment.
Suggested change
| 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. |
Member
Author
There was a problem hiding this comment.
The memory usage is not the total memory usage but for the glyphs. I think it is a bit misleading that way.
Member
There was a problem hiding this comment.
Fair, thanks
How about:
Suggested change
| 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. |
Comment on lines
+9
to
+11
| 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). |
Member
There was a problem hiding this comment.
again a bit more fluff
Suggested change
| 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). |
Member
Author
There was a problem hiding this comment.
Why 'automatically'? You need to manually control it.
Member
There was a problem hiding this comment.
I mean if I control it, it is automatic.
I can see how it is misleading.
Suggested change
| 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). |
Comment on lines
+9
to
+17
| 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)). |
Member
There was a problem hiding this comment.
Suggested change
| 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). |
Member
Author
There was a problem hiding this comment.
I put the desert bus comment at the bottom because it is less important.
Member
There was a problem hiding this comment.
Is it really less important than when it was implemented by whom?
I'd argue that this is much more interesting marketing wise
Comment on lines
+13
to
+18
| ### iOS | ||
|
|
||
| - [Action Journal Example](https://maplibre.org/maplibre-native/ios/latest/documentation/maplibre-native-for-ios/actionjournalexample/) | ||
|
|
||
| ### Android | ||
|
|
Member
There was a problem hiding this comment.
Suggested change
| ### 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/) |
| status: in-progress | ||
| --- | ||
|
|
||
| Add support for reading vector-tile sources in the [MapLibre Tile Format](https://github.com/maplibre/maplibre-tile-spec) (MLT). |
Member
There was a problem hiding this comment.
more fluff
Suggested change
| 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. |
Member
Author
There was a problem hiding this comment.
Mentioning benchmarks without a link, reproduction or specifics is not useful IMO. I think we should keep this information in the repo where we can keep it up to date.
Member
There was a problem hiding this comment.
Suggested change
| 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. |
| status: in-progress | ||
| --- | ||
|
|
||
| We are experimenting with various ways to add plugins for extending MapLibre Native. |
Member
There was a problem hiding this comment.
Suggested change
| 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. |
Member
Author
There was a problem hiding this comment.
As of October 2025, we are
Maybe
Member
|
@louwers |
Member
Author
|
@CommanderStorm Oh we should prevent merging when there are comments. |
Member
Author
|
@CommanderStorm Left some comments, feel free to make a PR. |
Member
Author
|
Enabled 'require conversations to be resolved for merging'. |
Member
|
Thanks, did not know that this is an option Honestly, it would be intersting to have these settings better synced across repos. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds additional roadmap items, including ones that were delivered this year.