play vs. location services
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
I noticed that quite some apps are picky. They are not happy with the (gapps-free) location service provided on my phone, but explicitly want "google play services". An example is the German Mail app, but some more as well.
What can I do?
Is it misconfiguration at my phone?
Is it sloppy programming - and should app providers be blamed for that?
Or should / could UnifiedNlp be extended by a component which pretends "I'm google play location services" ?
##
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by clarifying whether the request is for a UnifiedNlp compatibility component that presents Google Play location services, then determine the required Android integration and expected behavior. Done would require an agreed scope and an implementation or documented decision.
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
- 20/100