Chrome for Android builds are now dependent on the Google Play Services
codereview.chromium.org
Chrome for Android builds are now dependent on the Google Play Services
1–6 of 6 posts
Re: Chrome for Android builds are now dependent on the Google Play Services
#2I guess this is bad, somehow, but eh...if you've got an Android phone you're already updating Play Services pretty frequently anyway, so, I'm not sure what the ramifications here are one way or the other?
Re: Chrome for Android builds are now dependent on the Google Play Services
#3I'm really not a fan of Google's direction as of late.
Re: Chrome for Android builds are now dependent on the Google Play Services
#4I guess this is bad, somehow, but eh...if you've got an Android phone you're already updating Play Services pretty frequently anyway, so, I'm not sure what the ramifications here are one way or the other?
[deleted]
Re: Chrome for Android builds are now dependent on the Google Play Services
#5This looks like they expect HTML5 mobile games to become more popular in the future. This means browser games will be able to access the same features as native ones.
It will be interesting to see how it plays out.
Re: Chrome for Android builds are now dependent on the Google Play Services
#6I guess this is bad, somehow, but eh...if you've got an Android phone you're already updating Play Services pretty frequently anyway, so, I'm not sure what the ramifications here are one way or the other?
Several other vendors build on that code, including some that don't ship Play Services. See http://www.quirksmode.org/blog/archives/2015/02/counting_chr...
Anecdata alert: On my main test phone, Play Services consumed more network/battery than anything else. (Admittedly, I never use that phone for games, phoning or really anything except testing a single app). So I deleted Play Services and its relations, so I could measure my own stuff better.
Battery lifetime improved greatly.