5 ms·
The consumer doesn't care which method is used to serve an application. PWAs could easily be presented to the end user like a native App. The problem is rather
by rickdeckard 1y ago
The consumer doesn't care which method is used to serve an application. PWAs could easily be presented to the end user like a native App.
The problem is rather that PWAs would prove a viable path for universal cross-platform applications, taking away the gatekeeper role the OS-vendors have.
Paradoxically PWA-support is also part of the "we're no gatekeeper" narrative, so it's in the OS-vendor interest to keep it maintained as a hampered alternative to native apps.
- shuckles 1y ago> The consumer doesn't care which method is used to serve an application. PWAs could easily be presented to the end user like a native App. No it can't. The web will never support what's necessary for parity with native apps. Imagine trying to implement Liquid Glass in CSS.
- rickdeckard 1y agoFirst, you're mixing up capabilities of PWA vs native apps (no one stated they're equal) and how an OS presents Apps differently from PWAs (which was my point). Second (even though it's completely beside the point), especially Liquid Glass could be implemented in PWA, because it's a rendering effect the OS could put on top of appropriately tagged elements of the application. And voila, the same webapp could render in Liquid Glass in IOS26 and in less-gaudy Liquid Glass in IOS28, and meanwhile in no Liquid Glass at all on devices that don't have it...