Despite it being a terrible decision, I don’t think it affects Apple’s bottom line positively at all to support other browser engines: they won’t make any money off it, will create headaches for themselves since they need to expand their security surface and do some technical work to support it, and cede control to competitors. Approximately nobody (weighted by financial impact to Apple - whether Firefox uses WebKit or not is, as far as I can tell, completely irrelevant to Apple’s bottom line) is deciding not to release on iOS because of WebKit.
I'd be surprised if this couldn't be turned towards pushing for greater user choice as it was when MS was bundling internet explorer for years. If memory serves, it was competition law which was used to undo that.
Another example: earlier this year it was revealed that Safari had a huge security hole in its IndexedDB implementation:
There's absolutely nothing that a web browser maker could do about it. They fall victim to the exact same bugs that Safari does because they have to way to avoid it. Again, not real competition. They also broke localStorage in iOS 14.1 and took three months to fix it. Because there's nothing forcing their hand.
> The reasons for this are technical, not arbitrary or business related.
Oh my sweet summer child. Apple has many business incentives to push native solutions over web-based ones. We'll never know exactly what motivates them or why but to totally dismiss any business incentives at work here seems naive.
Apple gain nothing. That precisely why they don't do it. However, we all suffer from a web platform that gets held back by there being zero competition on iOS.