Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to OSM or Mapsforge #3

Open
carlphilipp opened this issue Jan 26, 2022 · 1 comment
Open

Migrate to OSM or Mapsforge #3

carlphilipp opened this issue Jan 26, 2022 · 1 comment
Assignees

Comments

@carlphilipp
Copy link
Owner

carlphilipp commented Jan 26, 2022

Context
The F-Droid flavor of the app is using Mapbox right now (while the google-play version uses Google Map).
Mapbox switched their license to be proprietary.
While the current Mapbox SDK used in the app is allowed in F-Droid as it has an open source license, migrating to the latest SDK version will not be allowed.

Description
The app needs to go away from Mapbox:

  • I don't know how long the old SDK is going to be maintained.
  • I would like to migrate away from jcenter() as it became deprecated last year, but right now it's not possible because Mapbox old SDK is not available in Maven central.

After a quick research in F-Droid forums, it seems like there are two options to replace Mapbox:

I have not done more research than that, so I don't really know if any of those 2 SDKs contains the features needed/used in the app. I hope so.

@boriguen
Copy link
Collaborator

boriguen commented Feb 8, 2022

Sounds good, I'll have deeper look shortly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants