Epic doesn't make any PWAs as far as I know, so this is really just general shade thrown in Apple's direction. Despite Apple's dominant position, I empathize wi

Epic doesn't make any PWAs as far as I know, so this is really just general shade thrown in Apple's direction. Despite Apple's dominant position, I empathize with the desire for less surface area and eliminating features only a tiny fraction of users ever used. PWAs occupy that weird space between an ordinary webapp (that you can still bookmark on the homescreen, AFAIK) and a full-blown app. It's not clear to me what the precise benefits are of a PWA over a regular webapp. A regular webapp can cache resources with E-Tag and Cache-Control http headers. A regular webapp has localstorage, etc. Maybe PWAs get always on server push? But what users actually want that anyway? I personally don't use any PWAs and have never built one. When I want to target native iOS (or Android) I boot up a React Native project like a sane person. I like to attack Apple monopolistic practices as much as the next guy, but this seems overblown. PWAs seem like a red-headed stepchild of web app development and it makes sense to jettison support for them to simplify the operating system and related APIs.