3 ms·
Are PWAs alive enough to have something to “kill” in the first place? One still has the feeling that the driving force behind “let’s make the web work like nat
by isodev 3y ago
Are PWAs alive enough to have something to “kill” in the first place?
One still has the feeling that the driving force behind “let’s make the web work like native apps” comes from FAANGs who generate revenue by having people engage even more with web content.
Why on earth would we replace one set of walled gardens with another? PWAs are not an improvement, just a different take on the same system (only one would be enslaved to their browser maker and OS maker and not just OS maker like native apps).
- samlinnfer 3y agoThey are not just killing PWAs, they are salting the earth to prevent new ones. Just some advantages of PWAs * No need to develop a separate android and iOS app - just use open web standards * Native apps features such push notifications, badges etc * Literally not a walled garden PWAs are an actually open platform very far removed from what you are describing.
- shuckles 3y agoA lot of this is fantastical thinking where “Chromium features” are referred to as “open web standards”.
- isodev 3y ago> No need to develop a separate android and iOS app - just use open web standards PWAs is just a name for cached documents the browser shows a bit differently. Notifications and badges do not make "an app". > Literally not a walled garden Literally demonstrated by Google recently (doing whatever they want in Chrome/imums) and Apple as per the topic of this post - PWAs are entirely dependent on the grace of the MFAANG developing your browser of choice. So yes, walled not only on device/OS level but also in user land.