maplibre-native-gl-js-parity

MapLibre Native and GL JS Parity

MapLibre GL JS and MapLibre Native read the same style specification but ship features at different times. A style key Native does not know is ignored, and a paint value it cannot parse drops its layer, both without a crash, so the symptom is a map that quietly differs from the browser. The table below names each gap this skill covers, the release that closed it where one has, and what to do on Native instead. Rows were checked against android-v13.7.1 (2026-10-15) and ios-v7.0.0 (2026-10-28).

When to Use This Skill

These are symptoms as you would observe them, before you know the cause:

• The browser shows a globe, the app stays flat: the style sets "projection": {"type": "globe"} and nothing changes on Android or iOS however far the map zooms out (no Native release draws a globe).
• One layer never draws on Android or iOS, no crash, every other layer fine: a paint value uses an expression the installed release does not implement, such as interpolate-hcl before android-v13.7.1 or ios-v7.0.0, so the whole layer is dropped.
• Porting map.setTerrain(...) to Kotlin or Swift: there is nothing to port it to (no Native release has 3D terrain).
• A maplibregl.addProtocol handler needs an Android or iOS equivalent: there is no addProtocol on Native; app code answers the request in each platform's HTTP stack instead.
• Elevation-banded color on a phone without pre-rendered tiles: a color-relief layer, on Native since android-v13.0.0 and ios-v6.24.0.
• A .pmtiles archive in an iOS or Android app: no tile server, conversion, or package; pmtiles:// is built in since android-v11.8.0 and ios-v6.10.0.

Scope. The table's six gaps are the ones where a model answering without this skill gets the API or the release wrong. The renderers differ in other places too. For a feature not in the table, find the release that added it in the Native CHANGELOGs.[5] [6] The js-parity label tracks open gaps,[1] but some open issues there describe shipped features.