Progressive Performance (Chrome Dev Summit 2016)

Channel:Chrome for Developers · Length:35:41 · Published:2016-11-11 · Views:34333

Watch on YouTube

Summary

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.

Why HN recommends it

HN commenters cite it as the clearest case for why mobile devices are slow and why code-splitting and progressive web apps are needed.

Take a look at this talk on why mobile devices are so much slower than desktop devices — HN, 2016

Web development · Software performance & optimization

Subtitles (excerpt)

[MUSIC PLAYING] ALEX RUSSELL: Hi, good afternoon. I'm Alex Russell. I'm an engineer on the home team. And to set expectations, This isn't the talk I usually give, so I hope you'll bear with me through some difficult content. These days, I usually put this slide up to talk about Progressive Web Apps, which Francis Berriman and I named last year. Progressive Web Apps are the culmination of multiple years of my team's work. I've been working with Jake on service workers for, I guess, four years now. And the team that I work on has been designing and building the core technology for Progressive Web Apps, the stuff that you've been hearing about for the last couple of Chrome Dev Summits, and all day today, and probably all day tomorrow. And I apologize a little bit, but not really. But as you can imagine, building and maintaining all of that stuff, and working on the standards for it, is a full time job. But I'm not going to talk about Progressive Web Apps today. At least not directly. You see, for the past year, I've also been working with Thao and her team, to partner with folks who are about to launch their Progressive Web Apps, to make sure that they're really high quality. And this incidental consulting work has given me a broad view into the practices

On Hacker News

Alex Russell first diagnosed this problem at Chrome Dev Summit in 2016 in a really amazing talk: [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. — feross, 2018-09
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: [VIDEO] — scribu, 2017-02
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) - [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] — inian, 2016-12
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: [VIDEO] — Touche, 2016-11

Related videos