Replies: 7 comments 12 replies
-
hey @maxammann, would you kindly point to some documentation about
Thanks |
Beta Was this translation helpful? Give feedback.
-
Is this not covered by §3.1? Doesn't sound like this would be an issue for users from the EU. |
Beta Was this translation helpful? Give feedback.
-
I think a discussion about supporting the MapLibre versions of the SDKs is warranted. At first I wasn't too concerned about the changes to the license and prices, until I noticed (many weeks later...not sure if something has changed since the original announcements) that there is now a Map Seats fee for any app that isnt "open to the public". The free tier is 3 monthly active users. That means if you develop an app (such as an internal app for employees, or anything not open to the public for free) you need to pay $4.00 per month per active user. I have a few apps in production for small to medium buisnesses and non profits, and we are potentially looking at a few thousand to tens of thousands a month in Mapbox fees, which is pretty much a non-starter. The fees apply even if not using the Mapbox service at all (ie: custom tile servers, etc) like we are. I wonder if forking this project under the MapLibre banner would be the way to go if there isn't an appetite to support MapLibre? Any thoughts? edit |
Beta Was this translation helpful? Give feedback.
-
If (or when) MapLibre has cocoa pods support then we should be able to support it in current master branch. This could be enabled via Cocoapods/gradle variables the same way we support newer non OSS Mapbox releases (iOS, Andorid) like 6.3.0 at the moment. I don't think maintainers of this repo has strong opinion about either MapLibre or new Mapbox going forward. It assume it could be either or both depending on community support. |
Beta Was this translation helpful? Give feedback.
-
FWIW PR #1311 allows one to use RNMBGL with MapLibre on iOS |
Beta Was this translation helpful? Give feedback.
-
Unfortunately they have not replied (yet? It’s been two weeks so I’m not
holding my breath ). I’ve tried their online chat system as well as
emailing their sales team.
…On Wed, Apr 21, 2021 at 4:00 PM Jonas ***@***.***> wrote:
@mfazekas <https://github.com/mfazekas> I'll admit it is very anecdotal
and based on reddit comments as they are the only place I can find "map
seats" mentioned on the web outside of Mapbox's pricing page
<https://www.mapbox.com/pricing/>. I have reached out to Mapbox's sales
team to try and get a better idea of what this all means. I've edited my
comment above to make it clear that no one really knows what a map seat is.
@gorbypark <https://github.com/gorbypark> did you get a response from
Mapbox's sales team what a seat means?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/react-native-mapbox-gl/maps/discussions/1274#discussioncomment-640157>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEVJWPJ5RV3IIDEVBHEZLUTTJ3K7VANCNFSM4ZD36ECA>
.
|
Beta Was this translation helpful? Give feedback.
-
Curious: has anyone already used MapLibre? |
Beta Was this translation helpful? Give feedback.
-
Hello community!
I recently implemented a maps feature and found out that Mapbox switched to a proprietary license with Mapbox 10. Afaik you are bound to there TOS now and have to pay their cloud fees even if you do not use them.
Mapbox is very quiet about their license change and what it means for contributors and users of the library.
It all starts here with a non-free proprietary, but open-source license. . I'm not a lawer, nor very experienced with licenses. Just using my guessing here.
That means you are only allowed to use it if you have an active Mapbox Account. In fact the latest JS library of mapbox no longer works without an active mapbox account. This is also expected for Mapbox Native SDK 10.
You are not allowed to change Billing related code of the new versions. Also you aggree to these terms: https://www.mapbox.com/legal/tos/
A lot of famous people grouped and founded the MapLibre project. Their gl-native fork can be found here: https://github.com/maplibre/maplibre-gl-native
I will soon use react-native-mapbox-gl in an upcoming project. That means we need to have a plan what happens if this repository bumps the Mapbox version to 10. What do the main contributors of this repository think about this? Is this library focused on people who use the Mapbox cloud products?
More information: https://wptavern.com/maplibre-launches-as-official-open-source-successor-to-mapbox-gl-js
Beta Was this translation helpful? Give feedback.
All reactions