AI summary by TwinMind
More proof you need to use Expo...
Theo - t3․gg
20m 49s
Expo Overview and Benefits
- Expo = ecosystem of tools on top of React Native, like Next.js/Vercel for React Native world
- Two development approaches:
- Expo Go app: scan QR code for instant device testing (low complexity)
- Custom Expo Dev Client: build own wrapper with native code (high complexity)
- Eliminates need for local iOS/Android compilation
- Allows focus on feature development vs native concerns
Developer Experience Demonstration
- Live demo: npx create-expo-app → instant QR code → phone app running
- Hot reload: code changes appear instantly on device without cables
- Works across platforms: iOS, Android, web
- Enables Windows developers to build iOS apps without Mac/Xcode
Expo Package Ecosystem
- Extensive pre-built packages: audio/video, barcode scanner, battery, blur, camera, clipboard, crypto
- Native implementations optimized for both iOS/Android platforms
- Eliminates need to build custom native modules for common functionality
Allen Company Background
- French company with 90 engineers
- 7-year-old React Native apps (oldest predates React Native maturity)
- Full-stack engineers lacking native mobile development skills
- Developer experience prioritized for talent retention
Migration Strategy
- Avoided big feature branches/merge conflicts
- Created temporary Expo project in monorepo
- Registered Expo app as root, mounted old app inside
- Dual setup maintained during transition for safety
- Final migration: repo/apps/app-1 → repo/apps/app-1-expo → app-1
Native Code Classification Process
- Category 1: No native changes required (automatic linking compatible)
- Category 2: Requires specific native setup (manifest, permissions, icons)
- Subcategory A: Has existing Expo config plugin
- Subcategory B: Alternative plugin available
- Subcategory C: Develop custom plugin
- Result: 30 in-house Expo config plugins created
- 6-month migration timeline for 4 apps
Continuous Integration Transformation
- Previously: 7-minute local build times
- Now: <2 minutes S3 download/install on simulator
- EAS (Expo Application Service) handles cloud builds
- Mac Mini cluster for iOS builds with Apple certification
- Custom CLI: single command installs Dev client on any simulator
- Distribution via App Center (engineers) and S3 (simulators)
Quantified Impact
- Build time: 7 minutes → <2 minutes
- Native code changes: 5-760/month (mean ~200) over 5 years
- Team size: 90 engineers
- Calculation: 20% engineers × 10% native changes × time savings
- Result: 30 hours/month saved in build time
- Eliminated Xcode signing, Android/Java version issues
Technical Architecture
- Expo config plugins = package.json for native integrations
- Continuous Native Generation (CNG): generates native code from templates/config
- Custom Dev client distributed to all 90 engineers
- Onboarding simplified to 2 commands: install client + run bundler
Developer Workflow Improvements
- Web-like development experience for mobile
- Real device testing vs simulator-only development
- Eliminates local Xcode/Mac requirements for iOS development
- Linux developers can now contribute to iOS apps
- Faster onboarding than Next.js setup in many cases
