Crossing the chasm between quality and performance
summary
Team rebuilds a brick‑and‑mortar point‑of‑sale using React Native, defines load‑lifecycle metrics (first meaningful paint, time to interactive) and sets thresholds like 100 ms for “lightning fast” and a failure region near 7 seconds. Engineers and designers monitor a dashboard (scores ~0.8–0.97 acceptable) and enforce 60 frames per second. The outcome: checkout latency drops — reduced checkout time by more than half — and Dropbox adopts “problem framing cards” to pair quality principles with measurable performance.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 3:23The chasm
- 8:05Performance principles
- 12:22Product principles
- 17:29Closing the chasm
related talks
39mDefault to performance
26mImproving React Native Performance in Facebook Marketplace
24mOptimising React Native "Tools and Tips"
26mMeasuring and Improving React Native Performance
21mThe UI Was Beautiful. The Frame Rate Wasn’t. Why We Didn’t Fix It.
23mPractical Performance for React Native
17mAchieving Highly Performant Angular Apps
32mPractical Performance Tips Building Progressive Web Apps