You still haven't. The whole point of my comment is that you haven't, and I brought up specific points that remain un-addressed by any of your comments in your thread, despite your insistence. Linking to comments that largely consist of the next layer of "I already addressed your points elsewhere!" is not a response. The world exists beyond Apple, and "Apple decrees it" is not a sufficient to explain much of your claims.

If you don't care to engage with the substance of my points, fine, nobody is owed discussion, but this style of conversation is deeply unproductive and I believe even you are losing track of what you have and haven't said.

>You have points, I agree that web technology is well suited in 2025 to make interactive applications. I agree that web apps are being held back from expressing their true potential. And while Electron is largely skewered for being bloated and heavy, the web can be fast and fluid.

The main topic originated through OP's "why some users demand a 'native' app when the web app should be enough" for which I provided explanations as to why web apps haven't lived up to their potential i.e. conflict of interest and the corresponding sabotage by a gatekeeper in contrast to the manufactured narrative of "they are unpopular because they suck". That's a false narrative which I've explained in many comments:

- "A Progressive Web App, if allowed to reach its full, un-sabotaged potential, is the technological manifestation of the Digital Markets Act's goals. So it would be utterly absurd for Apple to pour hundreds of millions of dollars into fighting the DMA, just to let PWAs pass which achieves the exact same goals."

- "The reason I focused on Apple is because its actions are one of a profit-maximizing gatekeeper actively defending its most lucrative business against an existential threat that is PWA. Every bug, every delayed feature, and every artificial limitation imposed on PWAs on iOS is a calculated strategic move in this defense of its walled garden that makes maximum taxation possible."

Since you've stated that "I agree that web apps are being held back from expressing their true potential" you confirmed my thesis. That's why I stated: "I already responded to any of your points that are RELEVANT to the CORE DISCUSSION"

>But you haven't proven that web apps don't feel janky, fragile, and out of place.

That's not even part of the core issue and it has still been explained in my post anyway, which you even confirmed by saying "I agree that web apps are being held back from expressing their true potential" and is also expressed here:

- Apple's ban of third party browsers on iOS is deeply anti-competitive, STARVES the Safari/WebKit team of funding and has STALLED innovation for the past 10 YEARS and PREVENTED Web Apps from taking off on mobile. (https://open-web-advocacy.org/blog/apples-browser-engine-ban...)

-Deep System Integration

Web Apps need to become just Apps. Apps built with the free and open web need equal treatment and integration. Closed and heavily taxed proprietary ecosystems should not receive any preference.

- Web App Equality

All artificial barriers placed by gatekeepers must be removed. Web Apps if allowed can offer equivalent functionality with greater privacy and security for demanding use-cases.

These are all factors that have already been mentioned and they fix all the real issues that are not the product of active sabotage.

Furthermore, I'm using many web apps like Discord and Visual Studio Code and they do not feel janky, fragile or out of place, that's your subjective perception. And even if that were an objective fact, which they are not, it would still not be relevant to the core discussion since they are not inherent to the technology but product-management related trade-offs that can be improved and fixed.

>The web's internet-native status means a bad internet connection or a brief crossing through a dead zone will kill almost any web app. Yes, there's strategies around this with web workers nowadays, but those are quite complex to implement for even simple applications and often aren't worth the effort to do anything more than pop up a branded "you're offline" page.

Your first claim is just factually wrong, but you admit that in the following statement which contains another claim that is also wrong. Those are exactly the kind of problems that PWAs solve and the user experience in that regard has been steadily improving (see also https://www.inkandswitch.com/essay/local-first )

>An app can be completely cut off from the internet, it doesn't have that base assumption of network connectivity and isn't built from the ground up from network-based parts.

That's just straight up nonsense. Any native or web app that relies on internet connectivity will be equally affected. Any native or web app developed with a local-first or local-only approach will work perfectly fine without internet. You clearly have outdated knowledge on the matter. (see https://whatpwacando.today)

So I really had addressed your points that were relevant to the core issue, but you just wanted to nitpick details that had already been partially or fully addressed and are also insignificant in the bigger picture of the topic and technological progress in general. Those ones you listed are based on your subjective experience, your outdated knowledge on the tech or simply a transitory state of software that can be easily improved since they are not an inherent technological limitation.