And by what mechanism can you prevent google from disabling adb? Or implementing a situation like iOS where sideloaded dev apps only last for a week and are signed with your personal developer key tied to your credit card?
There's nothing to stop them, and absolutely no reason to think they won't take away adb sideloading in the near future.
Google have full control to do this on their Pixel devices by rolling out new firmware with further restrictions - though there is no evidence they plan to do so.
However other vendors that build upon AOSP, such as Samsung, can make their own decisions on this.
> However other vendors that build upon AOSP, such as Samsung, can make their own decisions on this.
Pure AOSP devices are only some chinese knockoffs without play store. If your device needs play store/device integrity verification, there are lots are requirements by goog that needs to be met. Goog can add new requirement to disable installing unverified apps from adb.
Sure, that's going really well for Graphene. What happens when AOSP is abandoned and google close-sources everything they can get away with? Do you expect users to start compiling years-old AOSP and rolling device trees themselves?
Do you see the direction they're heading? They're now making it so maybe .5% of android users know how to sideload. They're clearly chipping away at it, even though they might not be making all the changes at once.
What fraction of users do you think have a legitimate need to sideload apps on Android? I would imagine it's much less than 0.5%. Developers and technically-minded power users must be a tiny minority amongst Android users given that it has an install base in the billions.
Right now, not many. My point is that they aren't flipping a giant switch from an open platform to a closed platform. They're boiling the frog -- slowly removing features until all choice is gone.
A few more years in this direction and Android can be as locked down as iPhone before Apple was forced to allow sideloading
On Android you can both install and run apps over adb. The linked article explains:
> Participating in developer verification will not affect your experience in Android Studio, the official IDE for Android app development. You will continue to be able to build and run an app even if your identity is not verified. Android Studio is unaffected because deployments performed with adb, which Android Studio uses behind the scenes to push builds to devices, is unaffected. You can continue to develop, debug, and test your app locally by deploying to both emulators and physical devices, just as you do now.
Which is a clear roadblock for third-party appstores adoption, notably F-Droid which compiles and signs the apps it distributes.
What if F-Droid distributes an app Google or its US overlords deems dangerous or illegal? Will they block and/or revoke that signature, thus taking down F-Droid in its entirety?
This isn't so bad. Unlike other mobile OSes (namely iOS and HarmonyOS), you will still be able to install whatever you like on Android over a USB debugging connection (adb) without any developer verification.
It doesn't take much effort to enable Developer Options, plug into a laptop and run "adb install whatever.apk". It's kind of like the floppy disk era again, having to physically insert things into one's computer to install software. Not a big deal.
At least as far as I understand, this would be a huge issue for F-Droid, to the extent that it isn't clear if it can continue at all. Half of my apps come from there, and gets automatically updated. Starting to download APKs manually and install them with ADB isn't impossible, but a huge downside.
This might open up a market opportunity for an "F-Droid box" that one would plug into an Android phone over USB, to install and update F-Droid apps over adb. Or the equivalent software for a laptop.
They've made their intentions clear. As soon as third-parties start to use adb for sideloading there's a very good chance they start to lock that down as well.
