Web-Like Development and Release Agility for React Native
summary
Cloud CI via Mobile Center builds and distributes React Native apps, with crash reporting that links JS stack traces to source maps and real-device testing; a live payment bug is fixed and deployed over the air with CodePush (can stage to ~5% of users; code-signing planned). Remote debugging runs JS in an IDE by replacing Chrome with node-chakra to enable time‑travel snapshots, and a gesture-mirroring tool (Mayaki) records/replays events for multi-device integration tests.
AI-written summary · about
chapters (21)
- 0:00React Native development intro
- 1:44Web-like development model
- 3:30CodePush OTA updates
- 5:17React Native DevOps challenges
- 6:18Mobile Center intro
- 7:22CI setup for React Native
- 9:11Real device testing
- 10:35Gesture mirroring testing
- 13:22Debugging React Native apps
- 16:11Chrome DevTools remote debug
- 17:57VS Code React Native debug
- 19:00Time travel debugging
- 23:16CodePush real-time fixes
- 26:49Mobile Center crash analytics
- 29:18CodePush & Mobile Center future
- 31:48Why set up CI for React Native
- 32:30VS Code React Native tools
- 33:12Time travel debug experiment
- 33:53Mayaki multi-device testing
- 34:34Virtual device walls testing
- 34:55Summary & resources
related talks
40mWeb Like Release Agility for React Native Apps
31mFrom Zero to DevOps
15mWeb-like Release Agility for Native Apps
41mAutomating mobile applications from dev to production
19mWorld Class experience with React Native
31mThe Final Push: Deploying React Native
27mPractical CI/CD for React Native
17mReact Native Deployments with MS App Center
