As soon as side loading or their own app stores are allowed, all sorts of companies may require that. Maybe most big companies will stick with Apple's. As an i

As soon as side loading or their own app stores are allowed, all sorts of companies may require that. Maybe most big companies will stick with Apple's. As an iOS developer, hardening the 10k-ish apis that exist in iOS will be mostly impossible to do in a short term given the attack vectors would now be outside of Apple's control, probably resulting in incompatibilities and bugs. Android is a horrible platform already given the myriad of different OS versions that exist (and often are not updated by the users) that you have to support. I also wonder what the law requires as to switchover to the new rules, new OS releases or going back X versions or something? Is there are time frame? Imagine also being an app developer and having to build/test releases for multiple app stores that include different payment gateways. Without a solid and secure API environment in the OS, how do you manage that with screwing up? iOS has always been easy to do since you only have to support one major OS back. A couple jobs (like 7 years) back our Android app was a nightmare to manage, as we had multiple OS release/phone suppliers that rarely got bug fixes in at all and never at the same time, making fixing/testing some things a nightmare. Might be better today, but I remember how much of a pain it was.