onebusaway-android
onebusaway-android copied to clipboard
OneBusAway
Dependency on Google Service
Curious what the lift for this would be? Love the app being open source but it's dependent on Google ecosystem. Making it unsuitable for degoogle phones.
Do you mean supporting Huawei devices for example without depending on Google play services ?
@aaronbrethorst @amrhossamdev We can consume another open-source library for maps like open street maps for devices that don't support Google play services.
I would love to use this app on my degoogled phone! How can I pitch in for rebasing to consume a non-Google maps api?
FWIW, here's an example of using Gradle build flavors to support two separate builds of an app, one using Google Maps and one using OSMDroid:
- https://github.com/barbeau/gpstest/blob/master/GPSTest/build.gradle
The catch is that the last time I checked, OSMDroid doesn't have the same API as Google maps. So you're basically talking about reimplementing all of the code that interacts directly with the Maps API. I did that in the above project so two different map Fragments are implemented, one for each build flavor.
- https://github.com/barbeau/gpstest/blob/master/GPSTest/src/google/java/com/android/gpstest/ui/MapFragment.kt
- https://github.com/barbeau/gpstest/blob/master/GPSTest/src/osmdroid/java/com/android/gpstest/ui/MapFragment.kt
There might be a better way to do it today- maybe there's a new library wrapper for osm tiles that matches the Google Maps API.
@aaronbrethorst @amrhossamdev i would like to work on this issue please assign it to me
@amrhossamdev Give me some time to analyse the code base more deeply and what sections of Google API are consumed and what open source alternatives we have here