6 ms·

1. Average consumers are not going to install your PWA. I am sorry. Get over it. Geeks and power users maybe, but for the average consumer if you're not in t

1. Average consumers are not going to install your PWA. I am sorry. Get over it. Geeks and power users maybe, but for the average consumer if you're not in the App Store and Google Play then you don't exist. All further discussion is academic/hobbyist. 2. Even as a developer, I reasonably expect to migrate or re-write an app after 5 to 10 years. If I wanted to work on mainframe or AS/400 systems, then I would do that. But not trying to maintain a mobile app for 30 years without any significant evolution is a feature, not a bug. 3. Even if I did crave multi-decade stability, I would feel no envy toward SPA web frameworks on this front.

isatty 4y ago
Even as a power user I dislike PWAs. Give me a native app that is buttery smooth instead of 200m of JavaScript.
- polshaw 4y ago
  You don't get that choice. Except for the biggest apps/companies, economics dictates that you'll probably get a packaged webapp as the alternative. With more tracking etc, less accessibility, and a little more drive space.
- deleted 4y ago
  [deleted]
- miniBill 4y ago
  How about 1.2Mb of JS?
lostgame 4y ago
Does anyone want to install a PWA over a native app? Genuinely curious. Still wondering what the purpose of PWA’s existing is.
- spiffytech 4y ago
  I will for some things. I have a couple web apps I visit throughout the day and it's nice to have a shortcut on my homescreen, and to not have the address bar taking up space. Speaking from a technical perspective, adding a PWA to the home screen is useful for recognizing user intent to have a richer experience with an app. Push notifications, adding an app to the share sheet, etc. - things you don't want just any website to do, but might want to permit for a privileged site.
- fomine3 4y ago
  I don't want to install an native app for every restaurants that I visit every 3 month. I want to use PWA instead.

isatty 4y ago

Even as a power user I dislike PWAs. Give me a native app that is buttery smooth instead of 200m of JavaScript.

polshaw 4y ago
You don't get that choice. Except for the biggest apps/companies, economics dictates that you'll probably get a packaged webapp as the alternative. With more tracking etc, less accessibility, and a little more drive space.
deleted 4y ago
[deleted]
miniBill 4y ago
How about 1.2Mb of JS?

lostgame 4y ago

Does anyone want to install a PWA over a native app? Genuinely curious. Still wondering what the purpose of PWA’s existing is.

spiffytech 4y ago
I will for some things. I have a couple web apps I visit throughout the day and it's nice to have a shortcut on my homescreen, and to not have the address bar taking up space. Speaking from a technical perspective, adding a PWA to the home screen is useful for recognizing user intent to have a richer experience with an app. Push notifications, adding an app to the share sheet, etc. - things you don't want just any website to do, but might want to permit for a privileged site.
fomine3 4y ago
I don't want to install an native app for every restaurants that I visit every 3 month. I want to use PWA instead.