Skip to content
This repository has been archived by the owner on May 27, 2024. It is now read-only.

Drop support for Froyo? #256

Closed
vreixo opened this issue Apr 1, 2014 · 7 comments
Closed

Drop support for Froyo? #256

vreixo opened this issue Apr 1, 2014 · 7 comments

Comments

@vreixo
Copy link
Contributor

vreixo commented Apr 1, 2014

I was working with gradle files, checking Espresso and Robolectric, for better testing support. Doing this, I have noticed that we are not using latest PlayServices 4.+, but the problem to use them is that they have dropped support for Froyo, because the number of users is very reduced now.

http://android-developers.blogspot.com.es/2013/10/google-play-services-40.html

@barbeau
Copy link
Member

barbeau commented Apr 3, 2014

@vreixo This has been intentional so far. But, Froyo numbers keep dwindling, at around 1.1% of Google Play accesses today:
http://developer.android.com/about/dashboards/index.html?utm_source=ausdroid.net

Do we need any Google Play Services features that are only in the newest versions? If so, we could drop Froyo support if needed.

@kasbah
Copy link

kasbah commented Jul 28, 2014

Not relying on Google Play services would be great. I don't have them installed currently and don't really want to. That's why I was looking for an open trip planner in the first place.

@barbeau
Copy link
Member

barbeau commented Jul 29, 2014

@kasbah This issue was actually referencing the fact that Google Play Services is dropping support for Froyo (Android 2.2), and whether or not we should drop support for Froyo in the app as well.

I agree with you though that it would be nice to provide a version of OTP Android that doesn't rely on Google Play Services. I've added an issue for that here - #304.

@barbeau barbeau changed the title Play Services drops support for Froyo Drop support for Froyo? Jul 29, 2014
@barbeau
Copy link
Member

barbeau commented Jul 29, 2014

@vreixo Related to this - I'm ok dropping Froyo support in the next OTP Android release. It's down to .7% of all Android devices on Google Play.

@vreixo
Copy link
Contributor Author

vreixo commented Jul 29, 2014

@barbeau I think that there's no special code for Froyo and not for Gingerbread right now in the app, so we can maintain the support until we need new features not compatible.

@kasbah to use Play Services was a compromise because of it's closed nature but it offers a very appealing and easy solution to display maps. Off course would be interesting to also offer a version without them.

@barbeau
Copy link
Member

barbeau commented Sep 15, 2015

Froyo is down to 0.2% of Google Play users, and there are libraries I'd like to use (like android-maps-util) that require minSdkVersion of 9 or higher, or require newer version of Google Play Services. So, time to drop Froyo support.

barbeau added a commit that referenced this issue Sep 15, 2015
In the process of looking to fix #477, we need to change minSdkVersion to 9 to use the android-maps-util library.  This also means increasing the Google Play Services version to the latest, which means we have to fix #320 to switch from the LocationClient to FusedLocationApi.  Also bumps the Android Gradle Plugin version and support library vresion to match our compileSdkVersion.  Also removes an unused PNG file that was flagged by the Gradle plugin as an invalid name (it includes a ".").
@barbeau
Copy link
Member

barbeau commented Sep 15, 2015

Fixed via 7d6799f.

@barbeau barbeau closed this as completed Sep 15, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants