[Feature Request]: Migrate F-Droid flavor from osmdroid to MapLibre Native #3770
Description
Checklist
-
I have used the search function for OPEN ISSUES to see if someone else has already submitted the same feature request.
-
I have also used the search function for CLOSED ISSUES to see if the feature was already implemented and is just waiting to be released, or if the feature was rejected.
-
I will describe the request with as much detail as possible.
-
This request contains only one single feature, not a list of multiple (related) features.
-
I have read and understood the Contribution Guidelines.
-
I agree to follow this project's Code of Conduct
Contact Details
No response
Feature or improvement you want
Summary
Replace the archived osmdroid SDK with MapLibre Native in the F-Droid flavor to provide a modern, actively maintained mapping solution while maintaining F-Droid compatibility.
Motivation
- osmdroid is archived and no longer maintained
- MapLibre Native is actively developed, fully open-source (BSD-2-Clause), and F-Droid compatible
- Need to maintain feature parity with existing map functionality
Goals
- Replace osmdroid with MapLibre Native (org.maplibre.gl:android-sdk) in F-Droid flavor only
- Maintain core features: node markers, waypoints, tracks, clustering, custom tile overlays, and offline caching
- Keep Google Maps flavor unchanged
- Ensure F-Droid compliance (no proprietary SDKs or API keys required)
Phase 1:
- F-Droid flavor only
Phase 2:
- If rollout goes well, rm gmaps from deps and replace with maplibre
This is already a work in progress; adding to keep milestones up to date.
Why should this be added?
- osmdroid old and abandoned, maplibre new(ish) and shiny.
Screenshots / Drawings / Technical details
No response