I don’t necessarily disagree, but the fact they walked back the original policy because it was so unpopular leads me to believe they are trying to save face by implementing a PITA way of enabling unknown sources, such as through ADB.
The reason why I suspect that is because even with the original policy change, they were still going to allow unsigned apps to be installed via ADB.
But I guess we’ll just have to wait and find out.
They reversed course, so it’s not an immediate issue.
But to answer your question, they would have provided an OS update to only allows app installations from verified developers, no matter the source.
To get verified developers have to submit identification to Google and go through a Google process.
So it wouldn’t matter if the install source was a third-party repo, or Google Play, the system would not have installed any applications not signed by a Google authorized certificate.
That becomes very problematic because it gives Google the ability to restrict applications outside of the Google Play Store ecosystem.
They were copying Apple’s playbook from the EU wherein Apple was legally mandated to allow third-party app stores, and in response Apple required all apps to be signed by an Apple verified developer certificate, no matter the repo.
And wouldn’t you know it, Apple either revoked or would not provide certificates to developers of apps Apple didn’t like, such as BitTorrent clients.
Once or twice a week?
Uh…