News for hackers. Stuff that matters.
Re:Firefox not planning on supporting PWA by albertgoeswoof on Thursday December 31, 2020 @05:39AM (#25591500)
You’re talking about poorly designed web apps, which are designed to get users to convert to native apps because installed apps have a higher retention rate and are easier to siphon data from.

PWAs don’t solve those problems for marketeers either. They just annoy end users by making them do some funny dance to get the app on their home page, which then barely works and doesn’t support all the features a native app can handle anyway.

So you end up in a world where developers say “we have a mobile app, it’s a PWA, just install that” and then no one installs it because they don’t know how, and the marketeers get frustrated that the current web app isn’t sticky enough on mobile and so they add banners in to make people download the “real” app and you’re back to square one.

The only real solution is cross platform development toolchains (like electron) as they reduce the development overhead but allow for native apps.

Re:Firefox not planning on supporting PWA by twobitshifter on Thursday December 31, 2020 @09:47AM (#25593097)
It sounds like you think the problem is discovery. There’s some disagreement between browsers as to whether the install button should be supported to make discovery easier, but that’s not a very large hill to climb, and would save us all from having 5 to 10 copies of chrome running at the same time.
Re:Firefox not planning on supporting PWA by nottorp on Thursday December 31, 2020 @06:49AM (#25591827)
Electron is native? It's just another copy of Chrome...
Re:Firefox not planning on supporting PWA by sp332 on Thursday December 31, 2020 @09:24AM (#25592896)
In context, they mean native installation and app management instead of teaching users how to "install" a PWA.