Re:Betting on the Web – Why I Build PWAs
by criddell on Monday September 11, 2017 @12:24PM
(#15219686)
The author also points out (correctly) that web apps are smaller than their equivalent native app. That's nice, but I'm not terribly constrained as far as storage goes on my phone. I am constrained by battery life and data consumption.
[ Parent
| on HN ]
Re:Betting on the Web – Why I Build PWAs
by maxsilver on Monday September 11, 2017 @12:37PM
(#15219815)
> The author also points out (correctly) that web apps are smaller than their equivalent native app.
Well, the author straw-mans that web apps are smaller. Yes, web apps are lighter than equivalent native apps. But not to anywhere near the degree described in the article.
There's no legitimate reason for the Starbucks app to be 100MB. None. A native Android app equivalent to the PWA in the article would come in at about about 2MB, for instance.
Starbucks app is huge because they stuffed it with something (same for Twitter, Facebook, etc). Starbucks new PWA is clean and light because it hasn't (yet) been stuffed with the equivalent junk. It's not a technology difference, it's a political/corporate one.
Re:Betting on the Web – Why I Build PWAs
by Brakenshire on Monday September 11, 2017 @01:10PM
(#15220149)
Google will punish badly made web apps though, whereas the same apparently doesn't apply to native apps.
Re:Betting on the Web – Why I Build PWAs
by WoodenChair on Monday September 11, 2017 @01:58PM
(#15220577)
Even worse every time you go to Starbucks.com you might re-download all of the junk. If you use it multiple times a day, that's a lot of wasted bandwidth compared to a slim (unusual in these days) native app.