[jbstack]

This isn't how I've understood the change. My understanding is that developers will need to have their ID verified before they are authorised to allow their app to be sideloaded. So long as they have done that, why would the user need to have a google account to sideload the app? Wouldn't the whole thing be transparent to the end-user (for those vendors who pass the ID verification) and the only thing they'd notice is that they can no longer install the apps from vendors who haven't passed?

[BHSPitMonkey]

But as you said, the check (and denial) is happening at the time the _user_ is trying to do something _they_ wish to do (e.g. install an APK from a project on GitHub).

Much of the ecosystem of Android apps that are only distributed outside the Play store will be affected by this, as many developers won't be able or willing to submit to this process or waive their privacy (especially young developers or those making apps that are legal but often targeted by litigious companies, e.g. emulators, YouTube clients/downloaders, BitTorrent clients, etc.)

[jbstack]

I don't deny that there will be less apps available to sideload. However, the claim I was responding to was this one:

"After this change you will have to tell Google your real name and home address to install anything on your Android device."

As far as I can tell (and nobody who has replied has contradicted me so far), that isn't true. I won't have to tell Google my real name and home address to sideload [the now smaller selection of] apps.