3 ms·
Like many others no doubt, I invested heavily into the mapbox-gl-js library (pre 2.0). I was able to build amazing value on top of that library including a rout
by hutch120 4y ago
Like many others no doubt, I invested heavily into the mapbox-gl-js library (pre 2.0). I was able to build amazing value on top of that library including a routing voice navigation app for an aged care facility that is used to this day 24/7/365. It was a very sad day when they changed their licencing model to lock in vendors and I had to walk away from that investment of my time and effort. Luckily I had also worked and contributed to OpenLayers and Leaflet, so with significant effort was able to move my clients to those platforms.
I guess we now have some more insight into why this occurred.
> "In order to use most Services, you must register for or authenticate into a Mapbox account. When you use our application program interfaces (APIs), including our SDK Registry/Downloads API, each request to an API must include one of your account's unique API keys."
- Doctor_Fegg 4y agoOut of interest, is there a reason you can’t switch to Maplibre, the open source fork?
- hutch120 4y agoI remember looking at that fork when the whole licencing thing went down a couple of years ago, but it was unclear how much, if any support it would have. Looks like the project is doing ok.
- worstestes 4y agoAre you familiar with MapLibre? It’s a great project. It’s an open-source fork of Mapbox GL. I’ve only used the JS variant myself but there’s definitely a native one as well.