It sounds like we got TTI plans, action items, goals, now what about post TTI
-
-
Replying to @richardiii @ken_wheeler and
Shockingly similar advice: keep your main thread responsive! I've got an epic rant in me about this. TTI is *generic* in best possible way
1 reply 0 retweets 1 like -
Replying to @slightlylate @richardiii and
The first interaction is loading...the next is whatever you tap on. Getting it done and your main thread responsive again is the next goal
1 reply 0 retweets 0 likes -
Replying to @slightlylate @richardiii and
That could be a navigation or it could be in-page. Doesn't matter. Think of them as "actions" w/ time to get back to responsive as metric
1 reply 0 retweets 0 likes -
Replying to @slightlylate @richardiii and
Web devs don't compare this because we can substitute full page loads for anything we can do w/ Ajax. Makes it hard to discuss.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @richardiii and
But conceptually, why do we build SPAs at all? It's an amortisation calculation: TTI for each action can be lower of handled in script...
1 reply 0 retweets 0 likes -
Replying to @slightlylate @richardiii and
...But cost for the initial action goes up. What we want is low and constant TTI for all actions. This is why opening up threads matters...
1 reply 0 retweets 0 likes -
Replying to @slightlylate @richardiii and
...including the network thread (Service Workers). SWs get us low variability if we use them well and don't over-load code into the renderer
1 reply 0 retweets 0 likes -
Replying to @slightlylate @richardiii and
I have a pet theory: there's a metric that describes TTI + variance across a full session; captures lived experience of web vs. native
1 reply 0 retweets 0 likes -
Replying to @slightlylate @richardiii and
This metric would show why nobody (statistically) wants apps, particularly for one-off experiences. Also shows why app model feels better.
1 reply 0 retweets 0 likes
In the app model, you amortise up-front pain over a hopefully long time. Model gives low variance. Web is high variance.
-
-
Replying to @slightlylate @richardiii and
...until now. The best PWAs can deliver low up-front cost + low long-term experience variance.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.