AI summary by TwinMind

The Future Of Mobile Dev w/ Charlie Cheever from Expo

Theo - t3․gg

2h 51m 48s

Charlie Cheever Background & Expo Origins

  • Charlie Cheever: grew up Pittsburgh, Harvard, worked Amazon/Facebook, started Quora, co-founded Expo
  • Expo origins: painful mobile development experience at Quora managing mobile teams
  • Problem: building mobile apps was extremely difficult even for simple website-based apps
  • Solution research: initially explored webview approaches, found them inadequate
  • Built framework similar to React Native before RN announcement
  • Pivoted to build on React Native when Facebook announced it with massive momentum (25k GitHub stars overnight)
  • Core philosophy: take everything good about web development and bring to mobile

Expo's Customer-Centric Approach

  • Early influence from Amazon's customer obsession culture under Jeff Bezos
  • Initially provided extensive desktop software bundles for React Native setup
  • Direct user engagement: screen sharing, Slack channels, 24/7 support for early adopters
  • Challenge scaling personal touch: now 30k potential users vs early days with ~10 users
  • Current approach: Discord, forums, feature voting, 1 hour daily community engagement
  • Twitch case study: immediate outreach for high-profile users, opened dedicated Slack channel

React Native vs Native Development Debate

  • Trend: new companies rarely choose pure native development anymore
  • Hiring challenge: difficult to find skilled Swift/Kotlin developers
  • Stanford example: Expo mobile development course enrollment now exceeds traditional iPhone programming class
  • Common choice: Expo vs no mobile app (not Expo vs native)
  • Large company adoption: gradual migration through new products rather than full rewrites
  • Uber Eats example: built in React Native while main Uber app remains native

Technical Architecture & Platform Challenges

  • Apple's browser restriction: forced pivot from true "browser for native apps" vision
  • React Native browser limitations: lacks backwards compatibility like web browsers
  • Dev client solution: custom builds with specific React Native versions for compatibility
  • Multi-platform development: iOS, Android, web from single codebase increasingly viable
  • Navigation differences: mobile vs web URL/back button paradigms need solutions

Developer Experience & Tooling Evolution

  • EAS Build: cloud-based building eliminating local Xcode/Android Studio requirements
  • Config plugins: programmatic native configuration management
  • Over-the-air updates: JavaScript-only updates without app store review
  • Global accessibility: enables iOS development without Mac hardware (important for Southeast Asia)
  • Snack: browser-based development environment for complete workflow

Industry Relationships & Ecosystem

  • Meta/Facebook relationship: strategic vs developer-focused priorities
  • React Native limitations: features Facebook doesn't need (like list performance) get less attention
  • Community partnerships: Software Mansion, Infinite Red, Callstack collaboration
  • Contrast with Google/Flutter: Google has developer business incentives, Meta doesn't
  • Open source contribution: React Native Reanimated, other core libraries

Performance & Type Safety Discussion

  • Continuous deployment benefits: critical bug fixes, rapid iteration cycles
  • Type safety challenges: remix vs trpc approaches to client-server communication
  • Planet Scale read-only regions: performance improvements limited by ORM support
  • Prisma limitations: no multi-database URL support for read/write separation
  • Zod integration: shared validation between client and server

Future Vision & Platform Politics

  • Write-once-run-anywhere goal: pragmatic approach with platform-specific switches
  • Desktop support: long-term plan, currently focusing on mobile/web parity
  • App store gatekeeping: arbitrary rules limiting innovation (Xbox Cloud Gaming example)
  • Developer time vs user time imbalance: 90% web development, 80% mobile usage
  • Single codebase future: reducing organizational complexity, aligning with user behavior

Technical Deep Dives

  • React Native web architecture: thin abstraction layer vs heavy runtime approaches
  • State management challenges: JavaScript vs native data structure coordination
  • Multimedia focus: camera, audio, WebRTC increasingly important for modern apps
  • Backwards compatibility: web-like stability vs mobile's breaking changes
  • Exit strategy concerns: vendor lock-in vs ecosystem investment decisions

TwinMind

Get summaries like this for your own meetings

TwinMind takes notes in the background during meetings, lectures, and calls, then writes the summary for you.

Free plan to get started

No bot joins your calls

Phone, desktop & Chrome apps

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome