Today in "nonsense", we have...
(The recent example of the performance of LibreOffice ported to WASM was a pretty stark example of how efficient those technologies aren't).
Moreover, there's no access to the native UI toolkit from these applications (no, HTML forms elements are *not* an application user interface toolkit). You need to construct everything from scratch. If you're lucky, you might be able to use a native form button and maybe an input field - but photo pickers, toolbars, popups, map views, tabs, master-detail views, navigation overlays, all of the animated transitions...
Your device's global settings offer a *built-in* native toolkit dark mode? Text size options? Bold-text-everywhere? High contrast mode? Distinguish-without-colour? Button shape settings? On-off labels? Transparency reduction? Motion reduction? Numerous accessibility options for navigation like switch control or audio descriptions that just work out-of-box on native elements? Tough. Reimplement it all again, from scratch, different every time, limited by at-best the comparatively meagre attribute decorations that HTML offers for accessibility *and* only if your devs know to use them (and use them everywhere at, again, great cost in time, testing and maintenance).
Even something as basic as proper scrolling mechanics often have to be coded from scratch, depending on what you're trying to scroll inside your giant tower of DIVs.
The whole debate is asinine. If you want a web page, write a web page. If you want a "web app", fine, you don't want to pay fees except your own hosting. Live with the fact that you're either going to produce a sub-par user experience on the lowest of lowest common denominator cross-platform options, or you're going to burn a truly vast amount of money on extra engineering resource to try and reimplement all the things that native code would've given out-of-box on Android or iOS - right up until next year, at least, when a new iOS or Android version changes how things looks, or introduces new features that all the already-written native framework apps just 'get', but your web app doesn't.
Want free of the "walled garden"? Good news! Android exists, and has a *huge* market share compared to iOS. Deploy off-store. Don't want to be limited by Safari on macOS? Good news! Windows and Linux exist and have an even *more* huge market share compared to macOS. I mean, who cares if you need to tell your users to bugger off and download the latest Chrome or Firefox or whatever because we all just *loved* it in the 1990s when web sites would tell us that our browsers weren't good enough, right? So knock yourselves out, use all those shiny new APIs that evil Apple isn't giving you.
But what if you wanted that juicy income from those rich iOS folks but don't wanna bother writing a native app because hosting it on the App Store (or Google Play Store, for that matter) means 30%? Well then yeah, it's not about your users, is it? It's about the money. The users have to accept something slower, of unknown security, of unknown privacy and with no control over when updates happen.
If any web app was worth beans then it'd be popular AF on Android, with people clamouring for a version on their Apple device, making Apple look bad until they did something about it. Ever heard of that for a web app? Even once? Nah, me neither.
As for when Google is pushing the latest new web API? Be afraid - or did you think somehow that Google were any less evil, or any less self-interested, than Apple?