AI summary by TwinMind
Vercel's Got Some New Competition
Theo - t3․gg
32m 28s
Introduction to Mobile Backend Deployment Challenges
- Companies like Vercel made web backend deployment easy
- Mobile apps need more than just JSON APIs - require comprehensive backend solutions
- Expo (React Native company) launched deployment/hosting service for mobile-specific needs
Server-Driven UI Concept and Facebook Feed Example
- Traditional approach: server sends data, client transforms to UI using app binary code
- Problem: client must have all possible UI components in binary to render server responses
- Facebook feed example with different post types:
- Photo posts with album layouts
- Video posts with video player
- Text posts with basic content
- Adding new post type (Valentine's Day post) requires app binary update
- Desynchronization between client/server versions when backend adds new features
App Store Update Deployment Timeline Issues
- Apple App Store review process takes days/weeks
- User adoption rates after release:
- First week: 20-40% update
- First month: 50-70% update
- 2-3 months: ~90% update
- Makes time-sensitive features (Valentine's posts) impractical with traditional approach
Server-Driven UI Solution
- Instead of sending data to transform, server sends actual UI components
- Server returns HTML/JSX-like structures rather than raw JSON
- Similar to HTMX patterns but for mobile
- Big companies already use server-driven UI models for mobile apps
- Enables feature deployment without app binary updates
React Native and Server Components Architecture
- React Native is abstraction layer over native SDKs (not web view)
- React Native → Swift UI → Native iOS SDKs (one level above Swift UI)
- Server components provide standardized server-driven UI approach
- Meta's lessons from mobile server-driven UI encoded into server components
- Eliminates need for custom conversion layers between API and native UI
Code Push Limitations and Server Component Benefits
- Code Push: swap app binaries to update features without App Store
- Requires maintaining sync between JSON API and binary versions
- Must include all possible post types in binary at all times
- Server components eliminate this complexity by sending UI directly
Expo Hosting Service Features
- API routes for app endpoints
- Secure environment variables
- Static generation for web pages
- Universal React server components
- Addresses traditional hosting service limitations:
- Integration with native app platforms
- Version routing between server/native app versions
- Observability for critical metrics by platform
Live Demo - Basic App Creation and Deployment
- Created new Expo app:
pnpm create expo app latest - Ran on web (
pnpm run web) and iOS simulator (pnpm run iOS) - Deployed with:
expo export --platform web --static-render-enabledtheneas deploy - Deployment completed in seconds with live URL
- Generated static site with SSR SPA architecture
- HTML served from server, client-side navigation via JavaScript bundle
Server Components Implementation Demo
- Added server component
get-clock.tsxwithuse serverdirective - Executed bash command on server:
wc -l $(find . -name "*.tsx" -o -name "*.ts" | head -20) - Used Suspense wrapper for loading states
- Server executes code, transforms to JSX, sends to client
- Alternative to traditional API → JSON → client transformation → render flow
Blog Feed Server Component Example
- Created fake blog with JSON posts in directory structure
- Two post types: text posts and image posts
renderPostsfunction maps posts toPostViewcomponentPostViewruns on server, determines post type, returns appropriate JSX- Server chooses text vs image rendering based on post content
- Custom styling applied server-side (font-weight: bold for titles)
Network Behavior Analysis
- Server components stream via
default.txtimport - Bundle contains React Native web JS for rendering
- JSON blob with children/style tags tells React what to render
- Client JavaScript doesn't include server-specific code when
use serverdirective used properly - Metro bundler tree-shakes server components when properly marked
Development Challenges and Gotchas
- Multiple deployment failures and reloading issues
window.location.href not definederrors on mobile- Module resolution problems during deployment
- Early stage technology with stability issues
- Evan (Expo team) actively fixing issues during demo
Future Implications and Benefits
- Reduces app update frequency to routing changes and native dependency additions
- Eliminates dependency on App Store approval timeline for feature releases
- Competitive advantage for teams using this technology
- Server determines UI rendering instead of client transformation
- More flexible than traditional client-heavy approaches
Technology Readiness Assessment
- Not production-ready as of recording
- Significant bugs and edge cases remain
- Expo team actively addressing issues
- Historical precedent: Expo Dev Client seemed impossible but became widely adopted
- Confidence in Expo team's ability to deliver based on past achievements
Expo Dev Client Historical Context
- Originally seemed "unobtanium" - impossible to achieve
- Now used in 50%+ of React Native apps
- Provides dev menu with debugging tools, fast refresh, element inspection
- Custom dev client building for team-specific needs
- Demonstrates Expo's track record of delivering complex solutions
