- Nov 12, 2013
- 1,049
- 1,340
- 113
But it is. Googles document got leaked.That’s not how Android sideloading currently works and there hasn’t been any announcement that it will work that way.
On Android, APKs just need to be signed with the developer’s own signing key. The OS doesn’t check a Google “whitelist” of developers before allowing installation. You only need to register with Google if you want to distribute through the Play Store.
Even today you can install apps from places like F-Droid, GitHub releases, enterprise distribution, or direct developer downloads without the developer submitting ID or source code to Google.
Google has added things like Play Protect scans and stronger permission warnings for security, but that’s malware scanning — not a system that blocks installs unless the developer is registered.
If Android required developer registration with Google just to install an APK, it would break open-source distribution, enterprise apps, and third-party stores, which are all things Android has supported for years.
https://forums.androidcentral.com/t...ou-sticking-with-android.1082173/post-7286005
Thats their age old public mask of deception.There would most likely be lawsuits followed if Google tried to completely control all this.
It would undermine Googles defense that Android is an open platform
Android is open, you are correct.
Google/Gapps is not.
Every OEM follows Google guidelines for comparibility and user experience. A large chunk of Android doesn't work without it.
Take that away and you have open Android and where custom ROMs snd tweaking fill the void.
