TLDR: Turning Redux state into a JavaScript string you can parse with JSON.parse() instead of an object literal, or inert script tag, appears to be significantly faster than other approaches for sending Redux store state to the browser.

For my case making this one change shaved TTI (Time To Interactive) from an already pretty good 4.04s to 3.3s, a .74s or ~18% improvement. It increased the Lighthouse performance score an average of 8 points from 87.2 to 95.2!

Techniques for keeping your app code under control even when requirements shift dramatically.

I've had this pinned on my twitter for just about as long as "tweet pinning" has been a thing:

If you don't actively fight for simplicity in software, complexity will win... and it will suck.

This is a chapter from my new book Human Redux which is now available!

As a user, nothing will more quickly sour me on a piece of software than flakiness. When we try to get someone to use our software, to some degree, we're asking them to trust us. If they're going to enter their data, spend their precious time, or hope to get some value out of the app we've built, they have to trust that it's going to do what it's supposed to do.

TLDR; The ability to build apps with web technology isn't just another way to build the same thing. It enables a whole new category of services that didn't make financial sense previously. As proof, I also introduce a real service that I've built for non-profits called Speedy that generates PWAs on the fly and is built on these ideas.

Note: I just spoke at Coldfront 2017 about why I’m such a big proponent of the Web. What follows is essentially that talk as a blog post (I’ll add a link to the video once it is published).

Also: the Starbucks PWA mentioned in the talk has shipped! 🎉