5 ms·
Very interesting article that talks about the progression of Google's closed source app alternatives: https://arstechnica.com/gadgets/2018/07/googles-iron-grip-
by tripdout 3y ago
Very interesting article that talks about the progression of Google's closed source app alternatives: https://arstechnica.com/gadgets/2018/07/googles-iron-grip-on-android-controlling-open-source-by-any-means-necessary/ https://arstechnica.com/gadgets/2018/07/googles-iron-grip-on...
I always thought that sure, they're deprecating old apps for the closed source Google version, which sucks, but at least AOSP still comes with barebones versions.
But now AOSP, a mobile phone operating system, will come without calling and texting ability? How can Google even do that? These apps, old as they may be, can also still serve as useful reference points for making your own OEM-branded app.
- jeroenhd 3y agoThey're just saying they've stopped maintaining it, I'm pretty sure that puts these apps in the same situation as the Android 2 style music player that's still part of AOSP.
- luca020400 3y agoTheir plan is to remove them altogether. Still those apps have not been maintained in years, that's the normal course of action for apps in AOSP.
- hedora 3y agoI think the big question is whether they “improve” the APIs these apps require at the same time. That would break the alternative implementations.
- luca020400 3y agoAndroid APIs are stable and an app will keep working until Google decides to bump the min SDK version in Android itself. The APIs a Google app uses are the same as any other app. Unless the app is privileged ( = can use system APIs ) there's no difference in capabilities.
- tentacleuno 3y agoActually there are a few APIs you can't use when the app isn't signed by a system key.
- surajrmal 3y agoAll oems or rom makers are able to make whatever apps they want system apps. So even if this is being done, Google dialer isn't getting access to something others cannot.
- hedora 3y agoYes. That is the problem I am referring to. They can bump the api version, removing the non-privileged APIs the AOSP stuff used, and move the implementation of the new privileged API into a proprietary blob. This is how location services work. Location has an obvious local-only fallback, but it is broken in practice. I imagine they can break phone calls/sms/rcs equally badly using the same technique.
- tripdout 3y agoOh wow, you're one of the guys from LineageOS right?
- luca020400 3y agoThere's many of us :)