AI summary by TwinMind
React Native Just Made A Long Overdue Change
Theo - t3․gg
11m 56s
React Native Framework Shift
- React Native officially recommends using frameworks like Expo for new apps
- Major change from previous create-react-native approach
- Similar to React web's move away from create-react-app to frameworks like Next.js/Remix
Historical React Native Setup Problems
- Traditional setup extremely complex: JavaScript project + Metro bundler + iOS project + Android project + bindings
- Author abandoned bare React Native setup years ago, moved to Expo
- Upload Thing supports React Native primarily through Expo due to complexity
React Web Framework Precedent
- React docs recommend frameworks over bare React
- Common problems: code splitting, routing, data fetching, HTML generation
- Companies have employees dedicated just to bundler management (Parcel example)
- Frameworks (Next.js, Remix, Vite) handle these automatically
React Native Framework Benefits
- Navigation between screens
- Data fetching and state management
- Native code upgrade management between React Native versions
- Dependency version compatibility
- Native build tools management (Xcode/Android Studio)
Xcode/Android Studio Pain Points
- Xcode still based on NeXTSTEP codebase from Steve Jobs era
- No deprecation policy = massive, slow bundle
- Android Studio equally problematic
- Author quote: "Xcode is so user friendly if you hate your users"
Framework Philosophy
- "You're either using a framework or building your own framework"
- Common solution better than reinventing everything
- Major corporations (Meta, Microsoft) build internal frameworks for Brownfield apps
- Instagram app takes 24+ hours to build from cold start
Greenfield vs Brownfield Applications
- New apps get happy path with frameworks
- Existing apps face integration challenges
- Companies want web teams contributing React Native features without hiring iOS/Android engineers
- Microsoft uses React Native for Windows 11 start menu and Xbox UI
Expo as Official Recommendation
- Only recommended community framework currently
- Free and open source framework
- EAS (Expo Application Services) is optional paid service
- Best-in-class developer experience
EAS (Expo Application Services) Benefits
- Mac build machines hosted by Expo
- Hand over React Native project + Apple credentials = automatic app generation
- Two-click deployment to App Store
- Can build iOS apps without Xcode installation
- Can build iOS apps on Windows
- Cheaper than renting Mac for builds
- Used by non-React Native developers for mobile app building
Migration and Compatibility
- Existing Expo users: no changes needed
- Migration instructions available on Expo website
- Benefits: easier React Native version upgrades, better DX
- React Native version upgrades still challenging ("hell")
- Author often initializes new project vs upgrading due to complexity
Continued Support
- Non-framework React Native usage still supported
- React Native Community CLI, template, upgrade helper continue working
react-native initmoved out of core to Community CLI- Command now:
react-native-community/cli@latest init
Server-Driven UI and Universal React Server Components
- Evan Bacon's Universal React Server Components presentation highlighted
- Server-driven UI allows server to describe both data and UI shape
- Essential for mobile: users on different app versions need same features
- Big companies (Facebook, Google) have custom server-to-mobile UI systems
- Server components make complex architecture available to solo developers
- Enables trivial implementation of previously complex patterns
