Tldr for those who are confused, since Android already does support side loading and even seamless updates for third-party app stores (like Droid-ify, etc), these are mostly legal changes.
Basically Google can't force Google IAP as the only method of payment in apps anymore, can't block companies from advertising how to find them on non-Play Store android app stores. So good changes overall.
Also when you download third party apks, on Android, while it's still relatively easy to do, it does give bit of a scary warning saying security issues are on the user for doing so. This creates the assumption that Play Store is the only secure way to get apps on Android, and the OS gives all sorts of special security exceptions to the Play Store for that. Obviously other secure app stores can exist, so this can be seen as an anti-competitive method since Google is exempt from their own scary apk install message.
Apple produces hardware for their walled garden, whereas Google imposes their terms on third parties. I can't speak to how this works legally, but thats the main difference as far as I understand.
It’s no longer an excuse for Apple. Since the EU’s ruling they now have to allow third party stores there: https://support.apple.com/en-us/118110 and of course they’ll fight tooth and nail against it here, the infrastructure exists so many of their previous arguments around not doing it are moot
Google forces conditions onto other OEMs. They have to include a bunch of Google stuff on their phones if they want the play store and play services, which they realistically need, that's just a market reality. They have no real choice but to do whatever Google says. Google is abusing their market dominance to push their ecosystem, and the OEMs have no real choice but to play ball.
Apple doesn't force anybody else to use their products. They make their own ecosystem for their own phone. If iOS was available on non-Apple devices, and Apple was forcing stuff onto those OEMs knowing they have little other choice, Apple would be getting the same treatment.
Google will have to distribute rival third-party app stores within Google Play, and it must give rival third-party app stores access to the full catalog of Google Play apps, unless developers opt out individually.
It's both, and honestly a pretty genius move on the judge's part. "Oh you keep finding ways of leveraging this gate to uncompetitively make money, well how about I just mandate that you give access to both sides of the gate to everyone else."
Mostly fair, but I'll push back on the security issue.
Side loading an apk is extremely dangerous, and an easy attack vector.
While there are plenty of malicious apps that make it on the Google store, they do attempt to do some automated and even manual curation. This is fact.
I think it's wholly appropriate to warn the user that they're bypassing that standard, if imperfect, Google security coverage. And granting extensive app permissions is done at your own risk.
3rd party app stores may do their own security curation as well, and it's up to them to communicate that and educate their users on why they still get the Google warning.
You could make exactly the same argument for installing software onto your computer, it is an attack vector and going through microsoft's store or your distro's repos gives a level of curation. So should desktop users be prevented/scared off from installing what software they want because it's a security issue?
You mean that warning that they all give when you're installing a 3rd party app? And the warning is more aggressive when it's an unregistered (licensed?) App.
They all do it. Windows, MacOS for sure. I don't remember seeing it on Linux, but I'm usually not installing sketchy binaries on Linux.
If malicious apps can make it way to Play Store, this means it is not 100% safe and make it subject to the same security warnings is reasonable, and not give it exceptions and makes it like the only safe option.