And Apple puts a damper on the web. [1] No web engine but their own: > 2.5.6 Apps that browse the web must use the appropriate WebKit framework and WebKit Jav

And Apple puts a damper on the web. [1] No web engine but their own: > 2.5.6 Apps that browse the web must use the appropriate WebKit framework and WebKit Javascript. > 4.7.1 [...] only use capabilities available in a standard WebKit view (e.g. it must open and run natively in Safari without modifications or additional software); and use WebKit and JavaScript Core to run third-party software and should not attempt to extend or expose native platform APIs to third-party software; No apps allowed to stream content not individually reviewed by the App Store, despite the lack of security risk that comes with streaming instead of installing outside apps: > 4.9.1 Each streaming game must be submitted to the App Store as an individual app so that it has an App Store product page, appears in charts and search, has user ratings and review, can be managed with ScreenTime and other parental control apps, appears on the user’s device, etc. > 4.9.2 Streaming game services may offer a catalog app on the App Store to help users sign up for the service and find the games on the App Store, provided that the app adheres to all guidelines, including offering users the option to pay for a subscription with in-app purchase and use Sign in with Apple. All the games included in the catalog app must link to an individual App Store product page. Blocking "side loading" of apps from the web, forcing streaming of apps to be shoehorned into the App Store individually, locking down all web functionality to Apple's implementation ... Apple is not a fan of old and new web capabilities that compete with its App Store. This is a problem for general computing innovation. [1] https://developer.apple.com/app-store/review/guidelines/ https://developer.apple.com/app-store/review/guidelines/