I feel that too. It's a direct result of Google cutting on FOSS expenditure and attempting to be more like Apple. I don't like that strategy, because it feels like another deviation from their original vision.
If Android is now perceived a burden for Google, the world will need a fork.
Both. So on the one hand you have the "controlled ecosystem" theory that invaded Apple first and Google now (because they make shittons of money on the app stores) and Google is consolidating towards this.
On the other hand, internally AOSP got merged with Chrome and both got massively cut, because in a closed ecosystem, FOSS is a burden. This goes for both Chrome and Android.
So I think there is some cause-and-effect going on here, and assuming that it doesn't correct, I find the long-term outlook bleak without an AOSP fork. A fork will be incredibly expensive though.
No. it is still possible. Seems like it will remain so if using Graphene. But it's unclear if normal Android devices will continue to be able to sideload after Google fully implements its evil scheme.
If people have to use Graphene, that raises the bar considerably for people who just want to run an app via APK.
You go from just changing something in the phone's settings, that you can change back easily, to needing to actually run a different operating system. Yikes.
So wait...no more sideloading an app on Android via APK?
You can still sideload a signed apk. Just not an unsigned one where the cert owner isn't KYC'd by Google - like with Apple.
Yeah, still, feels like the walls are closing in.
I feel that too. It's a direct result of Google cutting on FOSS expenditure and attempting to be more like Apple. I don't like that strategy, because it feels like another deviation from their original vision.
If Android is now perceived a burden for Google, the world will need a fork.
Do you think it's more about FOSS expenditure, or more about increased control?
Both. So on the one hand you have the "controlled ecosystem" theory that invaded Apple first and Google now (because they make shittons of money on the app stores) and Google is consolidating towards this.
On the other hand, internally AOSP got merged with Chrome and both got massively cut, because in a closed ecosystem, FOSS is a burden. This goes for both Chrome and Android.
So I think there is some cause-and-effect going on here, and assuming that it doesn't correct, I find the long-term outlook bleak without an AOSP fork. A fork will be incredibly expensive though.
No. it is still possible. Seems like it will remain so if using Graphene. But it's unclear if normal Android devices will continue to be able to sideload after Google fully implements its evil scheme.
If people have to use Graphene, that raises the bar considerably for people who just want to run an app via APK.
You go from just changing something in the phone's settings, that you can change back easily, to needing to actually run a different operating system. Yikes.
You can use lineageos on most of non-pixel devices.
And works perfectly fine with obtainium zapstore
I see this as GOOD news because will force people to take more measures for their privacy and get rid of spy software.
Bitcoin is a natural selection.
Changes like this quietly reshape who gets to build and share software.