Comment

Comment by troupo

Just as I said: you add a P in front of web apps, suddenly as if by magic all the issues disappear.

> PWAs do not need to be wrapped in a browser engine of their own, they use the installed browser engine.

Ah yes, they don't need a browser engine, they just need a browser engine

> They are not inherently bloated or resource-intensive in any way.

So, let me get it straight. A web app running inside a web browser engine is bloated, slow, and non-performant when it's on desktop. But the moment you put it on mobile it's not?

> There are not many good example of great PWAs precisely because Apple has been crippling web capabilities on iOS by banning other engines

Two notes:

- Which of the features that Apple "crippled" will help web apps not be bloated, non-performant, slow, with bad UI etc.?

Is it the lack of an install banner that makes a web app struggle to display even a static text with any semblance of performance?

Is it the lack of push of notifications that make Google say: okay, we give up, most sites load in over 2.5 seconds now, so we assume anything faster than that is a win [1]?

Is it <the list is frankly endless>...

- Android has been a dominant mobile OS for over a decade with "non-crippled" PWA support. Where are the not inherently bloated non-resource-intensive web apps we've been hearing about? Please say Twitter :))

[1] https://blog.chromium.org/2020/05/the-science-behind-web-vit...

parent troupo 2 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton