If the "open web platform" stops requiring an entire Chromium engine in the app, I would agree. Or if Google wasn't the sole effective standards body for it.

> If the "open web platform" stops requiring an entire Chromium engine in the app, I would agree.

PWA. FileSystem API is coming.

> Or if Google wasn't the sole effective standards body for it.

Agreed.

I'm not well versed with PWA topics but as long as Apple doesn't curve around this, we can't expect a wide adaptation of it. Don't get me wrong, PWA can be the future but not without the whole Apple ecosystem missing.

You can use pwabuilder and ship a "native" app to Apple Appstore.

Not anymore. And Apple has been removing many PWA and "app generator" style apps from App Store.

Learn to ignore garbage companies like Apple if you don't want to be treated like garbage by them. They don't matter. If Safari does not support the latest and greatest, Safari is garbage and show this message on your website with big bold letters.

I wish that each web standards would have official implementation subsets.

Sure, but there are still reasons you might prefer a native app. For instance, maybe you're writing an application that's meant to do stuff with the file system. You _can_ just run a local Web server and use the browser, but a local app might be a better experience.