Stability First: Building React Native Apps That Scale
summary
Clearcover reports 99.997% crash-free sessions (roughly one crash per 33,000 sessions) and targets five‑9s stability; the stack centers on TypeScript by default, sharing API types via an internal npm package, and validating responses with Zod so frontend and backend schemas stay in sync. Production tooling uses Sentry to capture JS and native crashes (a date‑fns edge case and a file‑download library bug) plus non‑fatal “soft lock” telemetry and 64 recording error codes to triage issues quickly.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:52Why stability matters
- 5:42Stability vs native apps
- 7:04Stability challenges
- 7:46TypeScript for stability
- 12:20Validating external data
- 16:32Sharing types frontend/backend
- 18:39Library risk management
- 19:20Sentry for crash detection
- 20:43Monitoring soft locks
- 22:49Conclusion and key takeaways
related talks
24mReact Native - Success case study
56mStability of a React Native App with 24/7 Uptime
25mReact Native in Practice
30mReact Native
11mTips for Building Successful React Native Apps
20mHow is your app actually doing in production
35mWeb-Like Development and Release Agility for React Native
45mReact Native: Things we learned the Hard Way