> least from my superficial impression, libre forks of mapbox legacy code seem to be far more alive in the subset related to the web than in the subset related

> least from my superficial impression, libre forks of mapbox legacy code seem to be far more alive in the subset related to the web than in the subset related to native. Just based on my superficial impression I think normal apps on the play store pay mapbox if they don't have a big budget and consider maplibre (the fork of mapbox's most recent approach) if they're big enough. My surface impression is maplibre is used by companies like Facebook who can afford to hire low level graphics devs and fork mapbox's work rather than pay the new license. For every feature, including offline, I think paying mapbox is the cheapest option with decent quality up to that scale. Of course, there are projects like mine that aren't motivated by profit. (I'm using mapnik, an independent oss project that got significant mapbox investment years back but which they now consider legacy).