2 ms·

> Can you not install a native app one day, and uninstall it the next day? Or does it not count as "temporary"? "Don't you guys have phones?" > Or are PWAs un

> Can you not install a native app one day, and uninstall it the next day? Or does it not count as "temporary"? "Don't you guys have phones?" > Or are PWAs uninstalling automatically somehow? They don't weigh 100MBs. I feel extremely privileged to have access to super fast networks, but it doesn't mean that lazy developers get right to hog it all.

palata 3y ago
If you can't make a native app that doesn't weigh 100MBs, then you may need to question your work.
- wiseowise 3y ago
  You want me to make other developers make their apps less than 100MBs?
  - palata 3y ago
    My point is that if you write a native app and can't make it smaller than 100s of MB, then you're maybe not a really good mobile dev. Are you implying that web developers are better than mobile developers? Because let me tell you that there are plenty of bad apps on both sides. It's not like PWAs are solving the problem that most software is extremely bad. On the contrary, cross-platform frameworks often lower the bar.
  - szasamasa 3y ago
    I agree that the main difference is developer skill, not whether an app is native or website. One little advantage for web apps: the app (js code) can be downloaded just in time (not that 99,9999% ever make use of this). If you have a game with 100 levels where a map of one level is 1mb, and 50% of visitors do not like your app and leave at the first level, they may have downloaded some fix code and 1mb, but 99mb stay on server... Js has modules and dynamic imports for quite some time. Even app logic can be built with dynamic loading in mind. Again, not that a news site like cnn will not make 300 request and 20mb download on first visit, showing one image and less than 1kb text :) Just checked. A web app, in theory, is perfect for dynamically loading things but not inherently more lightweight. As always, it depends. On the task, on the programmer.

palata 3y ago

If you can't make a native app that doesn't weigh 100MBs, then you may need to question your work.

wiseowise 3y ago
You want me to make other developers make their apps less than 100MBs?
- palata 3y ago
  My point is that if you write a native app and can't make it smaller than 100s of MB, then you're maybe not a really good mobile dev. Are you implying that web developers are better than mobile developers? Because let me tell you that there are plenty of bad apps on both sides. It's not like PWAs are solving the problem that most software is extremely bad. On the contrary, cross-platform frameworks often lower the bar.
- szasamasa 3y ago
  I agree that the main difference is developer skill, not whether an app is native or website. One little advantage for web apps: the app (js code) can be downloaded just in time (not that 99,9999% ever make use of this). If you have a game with 100 levels where a map of one level is 1mb, and 50% of visitors do not like your app and leave at the first level, they may have downloaded some fix code and 1mb, but 99mb stay on server... Js has modules and dynamic imports for quite some time. Even app logic can be built with dynamic loading in mind. Again, not that a news site like cnn will not make 300 request and 20mb download on first visit, showing one image and less than 1kb text :) Just checked. A web app, in theory, is perfect for dynamically loading things but not inherently more lightweight. As always, it depends. On the task, on the programmer.