We’ve been toying around with JS since 4 years, trying to figure out what’s the best approach to build mobile-friendly apps that would offer the best performances on mobile devices.
We first went SPA and then decided to take a different approach, as 3 years ago we decided to tackle our problems on mobile with an isomorphic application.
Today, we would like to guide you through years of that choice and why we decided to take a step back and go revamp our mobile website again, with server-side rendering and a pinch of React.
Spoiler alert: 30ms is considered slow.
135. “Hot” is
overrated
https://jakearchibald.com/2016/ca
ching-best-practices/
“As you can see, you can hack around poor caching in
your service worker, but you're way better off fixing
the root of the problem. Getting your caching right
makes things easier in service worker land, but also
benefits browsers that don't support service worker
(Safari, IE/Edge), and lets you get the most out of
your CDN.”
https://jakearchibald.com/2016/caching-best-practices/
NERD ADVICE
136. “Solve problems
on the right
layer”
https://www.ampproject.org/lear
n/amp-design-principles/
NERD ADVICE
137. “Solve problems
on the right
layer”
https://www.ampproject.org/lear
n/amp-design-principles/
NERD ADVICE