iOS Safari has been years behind Chrome and/or Firefox on graphics, compute (WASM, threading), user input, etc for a long time. If you're trying to ship a PWA t

iOS Safari has been years behind Chrome and/or Firefox on graphics, compute (WASM, threading), user input, etc for a long time. If you're trying to ship a PWA there is also a lot of stuff for that use case which is either missing or intentionally busted. A really obvious example: Fullscreen for webpages and PWAs on iOS is broken on purpose - the browser can do it, but won't allow you to stay in full-screen for anything except a <video> tag. Apparently they changed this on iPad? In any case, fullscreen is an absolutely ancient, uncontroversial web API they've chosen not to support that is essential for things like games and multimedia. There are other browser APIs that require fullscreen too, like pointer lock (if for some reason you've plugged a mouse into your iDevice... maybe that's why fullscreen is enabled on iPad.) So in practice, if you want to watch videos or play a game fullscreen on your iPhone, you have to go to the app store. Which is an intentional choice, because Apple gets to siphon 30% of all game transactions over there.