Chrome for Developers
4 HN recommenders · recommended in 4 months, 2016–2018
35:42 · 34K views · Nov 11, 2016
Alex Russell's Chrome Dev Summit 2016 talk on building web experiences that work on slow, flaky networks and low-power devices. It argues developers should focus on the performance of real-world mobile hardware rather than desktop machines.
HN commenters cite it as the clearest case for why mobile devices are slow and why code-splitting and progressive web apps are needed.
4 comments from Hacker News
Alex Russell first diagnosed this problem at Chrome Dev Summit in 2016 in a really amazing talk: this video He makes the point that lots of JS frameworks are so large that you're already doomed before you write the first line of real "app code". The framework itself has already blown your performance budget.
Take a look at this talk on why mobile devices are so much slower than desktop devices ( they are indeed 10x slower in the traces I have looked at too) - this video Also look at the speedometer benchmark ( [LINK] ) for a more realistic comparison of how slow your mobile device is compared to your desktop when running real world apps. Here are some numbers from the benchmark from some devices - [LINK]
Those words are meant for people who have the question "why should I go through all this trouble to implement this pattern?" That said, it is very vague. I think this presentation from Alex Russell does a much better job of demonstrating the need for progressive web apps: this video
Note that you should not choose Ember if you are creating an app intended to be used on mobile, as it doesn't yet have code-splitting. This talk explains about why this is a hard requirement: this video