Google will require all Android app developers to verify their identity with the organization before their apps can run on certified Android devices. The requirement applies to apps distributed through the Google Play Store and to sideloaded apps installed via APKs from GitHub or project websites. Developers must provide personal information to Google regardless of distribution channel. The policy enables Google to prevent apps it disfavors—on policy, political, or economic grounds—from running on certified devices. The change tightens control over applications and developers and threatens users' ability to run independent software on their devices.
What this means is that, if there is an application that Google does not like, be it because it does not conform to its policies, politics or economic incentives, they can simply keep you from running that application on your own device. They are locking down Android devices from running applications not with their purview. The ask? All developers, whether submitting their apps through the Play store or not, need to give their personal information to Google.
While this might sound like a common-sense policy by Google, this new standard is not just going to be applied to apps downloaded from Google Play store, but all apps, even those "side-loaded" - installed directly into devices by side-stepping the Google Play store. Apps of the sort can be found online in Github repositories or on project websites and installed on Android devices directly by downloading the installation files (known as APKs).
The decision begs the question, if you can not run whatever app you want on your device without the permission of Google, then is it really your device? How would you respond if Windows decided you could only install programs from the Microsoft app store?The move has of course made news in tech and cybersecurity media and caused quite a stir as it has profound consequences for the free and open web.
Collection
[
|
...
]