Idea for the new location stack
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
@mar-v-in
Is it possible to make it hybrid? (by including the most important backends inside but still allow external backends).
- Although backends are limited in new Android versions it is possible to unlock limitations by placing xml files and overlays in the system partition.
- Dropping backends completely waste a lot of works by other developers regarding backends.
- Some backends can never be integrated because they contains less privacy oriented code but still it may be useful for some people.
- The Mozilla backend may not working correctly in some countries, this isn't related to the new code but related to the Mozilla database.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed hybrid location stack and how Android system XML files and overlays could support bundled backends alongside external ones. Compare the privacy and regional concerns raised for existing backends, including the Mozilla database; done would require an agreed design and implementation scope for the hybrid approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100