When “Good Enough” - Just Isn’t Good Enough
summary
Claims that React Native can match native feel if teams invest in platform-specific craft, not just reuse web habits. Provides a concrete win: reverse‑engineers iOS animation (reads QuartzCore assembly and reimplemented Apple’s CA spring animation in JS) to match native transitions. Recommends practical practices: build a shared component library, design collaboratively across disciplines, budget time for polish, and validate UX with users. Argues RN yields speed plus acceptable native parity when organizations grow maturity.
AI-written summary · about
chapters (7)
- 0:00Introduction and topic change
- 2:28Art history and parallels
- 7:03React Native and efficiency myth
- 9:49Capitalism and software constraints
- 15:50Maturity in development practices
- 22:13Building sustainable mobile apps
- 26:53Call to resist mediocrity
related talks
32mGood Enough Still Isn't Good Enough
26mReact Native is the new black
10mReact Native, your UX superhero
25mGoing Native
28mBeing a Good Platform Citizen
52mWhy you should use React Native for your next mobile app
27mBuilding high quality mobile apps with React Native
01h 01mReact Native: A Better Way to Do Mobile