The Mobile Web: MIA

on YouTube ↗43m

" summary

Claim: responsive design failed because the mobile web is shrinking — time-on-mobile is ~13% (and Chrome telemetry suggests it’s falling, often below 10%), while median pages still send 370 KB median JS to old 2014-class cores. Platform constraints matter: App Store rules force WebKit engines and cap capabilities, and many Android sites ship huge JavaScript. Tools and fixes that work include WebPageTest, Lighthouse (Lighthouse budgets via a JSON), origin trials (contact picker, SMS OTP), and deployment via Trusted Web Activity in Play Store — Yahoo’s PWA shows this can succeed if performance budgets are enforced.

AI-written summary · about

" chapters (10)

1. 0:00Start
2. 0:07Alex Russell
3. 0:57Desktop Pwace
4. 1:46Trusted Web Activities
5. 6:31What Is the Web
6. 22:14Mobile and Desktop Web Usage Are Diverging
7. 28:52Growth Markets
8. 31:28Why Are Apple Chips So Fast
9. 35:04Chrome Dev Tools
10. 38:56Is It Too Late

" related talks

• 37mMobile Web PerformanceEstelle Weyl · View Source 2017
• 37mAdapting to the Mobile Web F̶u̶t̶u̶r̶e̶ PresentAlex Russell · Polymer Summit 2016
• 53mPerformance Checklist for the Mobile WebColt McAnlis · HTML5DevConf 2013
• 55mReckoning: Frontend's Lost DecadeAlex Russell · performance.now() 2024
• 46mFront performance: the mobile webAna Encinar · DevFest Málaga 2019
• 47mWhose web is it, anyway?Bruce Lawson · axe-con 2023
• 55mThe Future of the Mobile WebPaul Kinlan · Strange Loop 2016
• 28mBeyond Responsive: Building a mobile web you're f*ing proud ofKate Hudson · JSConf US 2015