Improving your resource granularity is also a tradeoff, but one that benefits most apps. Per-resource overhead often lower than over-loading
-
-
Replying to @slightlylate
...which gets to why PRPL is so damned important. H/2 Push + Service Workers keep you from paying too much per view: https://www.youtube.com/watch?v=J4i0xJnQUzU …
2 replies 1 retweet 7 likes -
Replying to @slightlylate
Proportionality is key. You aren't rendering everything in your app up-front. Tools that cause you pay for it all at startup are a bug.
1 reply 3 retweets 5 likes -
Replying to @slightlylate
The really important thing about PRPL is that it separates code *prefetching* (via the SW install) from loading into the document.
1 reply 0 retweets 2 likes -
Replying to @slightlylate
...and keeps that prefetching from hampering your first view load/render (because it's async and low-priority).
1 reply 0 retweets 0 likes -
Replying to @slightlylate
To make it work, you need a system that hot-loads code into your page when needed. There are several good strategies!
1 reply 0 retweets 0 likes -
Replying to @slightlylate
The first, and one I'm keen to see more people use, is full-page transitions w/ SW-based templating & Streams.
3 replies 1 retweet 5 likes -
Replying to @slightlylate
The next, of course, is route-based code loading based on route transitions. This requires loading a JS router.
2 replies 0 retweets 3 likes -
Replying to @slightlylate
I'm not sure that this will be faster for most sites, but it seems to be what SPA devs want ¯\_(ツ)_/¯
2 replies 0 retweets 2 likes -
This Tweet is unavailable.
: just as soon as the NYT commits to one or the other on native platforms, I'm happy to follow suit ;-)
-
This Tweet is unavailable.
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.