So native apps live in a world of negative externality: force users to be sysadmins about expensive resource on the *dev's* behalf.
-
-
Replying to @slightlylate
We can talk all day about how slow and bad and abusive adtech is (and oh boy do I have opinions)...but a bit of perspective is in order.
1 reply 0 retweets 8 likes -
Replying to @slightlylate
Native apps tend to be _terrible_ citizens of constrained devices because native devs only feel size/weight as trailing adoption factor
6 replies 1 retweet 5 likes -
Replying to @slightlylate
the data that a native app consumes is probably less over time than hitting a website over and over
1 reply 0 retweets 1 like -
Replying to @sebbean
: this is they key question I'm trying to work on right now. It isn't clear to me that this is true.
1 reply 0 retweets 2 likes -
Replying to @slightlylate
: so, lets say you download the WaPo or NYT apps: https://play.google.com/store/apps/details?id=com.washingtonpost.rainbow&hl=en …
1 reply 0 retweets 0 likes -
Replying to @slightlylate
: how many sites/pages do you need to visit before cost to fetching fresh content in both cases (assuming web is larger) meets?
1 reply 0 retweets 0 likes -
Replying to @slightlylate
: In the case of WaPo, the answer is NEVER. See: http://wapo.com/pwa Trends never meet. Web always lighter.
2 replies 0 retweets 0 likes -
Replying to @slightlylate
yea but I'd argue downloading an app once and putting that load time behind you is kind of nice
2 replies 0 retweets 1 like -
Replying to @sebbean
: yes! But note the term you used: "load time". That's about startup perf, not data transfer.
2 replies 0 retweets 0 likes
: ...which makes PWAs absolutely killer: you get reliable startup perf w/o massive download
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.