| I think by now it is common knowledge in anyone interested in this subject. A good place to start is this ArsTechnica post from 2013 (updated in 2018) [1]. One nice user on Reddit made a list [2] of AOSP apps replaced by Google: Google Services Framework removed in 1.1, replaced by Google Play Services Search removed in 1.5, replaced by Google Music removed in 2.3, replaced by Play Music Browser removed in 4.2, replaced by Chrome. Calendar removed in 4.4, replaced by Calendar (G) PinyinIME removed in 4.4, replaced by Google Pinyin IME Gallery removed in 5.0, replaced by Photos (G) Messaging removed in 6.0, replaced by Messages (G) Camera removed in 6.0, replaced by Camera (G) LatinIME removed in 6.0, replaced by GBoard. Contacts removed in 7.0, replaced by Contacts (G) Phone removed in 7.1, replaced by Dialer (G) Clock removed in 8.1, replaced by Clock (G) Calculator removed in 9.0, replaced by Calculator (G). This extends to APIs too. For example, Android Location API [3] has a very nice warning on the documentation page: > This API is not the recommended method for accessing Android location.
The Google Location Services API, part of Google Play services, is the preferred way to add location-awareness to your app. It offers a simpler API, higher accuracy, low-power geofencing, and more. If you are currently using the android.location API, you are strongly encouraged to switch to the Google Location Services API as soon as possible. To learn more about the Google Location Services API, see the Location API overview. Hope I removed some vagueness left by my previous comment. [1]: https://arstechnica.com/gadgets/2018/07/googles-iron-grip-on... [2]: https://www.reddit.com/r/fossdroid/comments/c332yr/what_impe... [3]: https://developer.android.com/reference/android/location/pac... |