WhoBuilt

Discussion Panel: 10 Years of React Native and Beyond

Sep 10, 2025· 52 min· 919 views·Watch on YouTube

Speakers

Callstack host James leads a React Universe Conf 2025 panel with Expo CEO Charlie Cheever, Callstack CTO Mike Grabowski, Meta React Native core team member Nicola Corti, Nakazawa Tech CEO Christoph Nakazawa, and Vercel CPO Tom Occhino on React Native’s history, current tradeoffs, and future.

Why React Native began

Christoph Nakazawa recalls an early hackathon prototype that ran in Node.js on a computer and drove views on a phone. Tom Occhino says the first live updates to native views made the idea feel significant. He traces the motivation to slower development cycles at Facebook and duplicated work across iOS, Android, and web teams.

What helped React Native grow

The panel recalls skepticism about app quality, startup time, and using untyped JavaScript, and says strong products helped win support. Charlie Cheever points to Expo’s support for native code, autolinking, and continuous native generation as milestones. Panelists also credit Hermes and bytecode caching with improving startup performance, and community efforts such as Lean Core with broadening contributions.

Strengths and tradeoffs today

Panelists value React Native’s community, native views, native-code escape hatches, and the ability to build across platforms from one codebase without necessarily sacrificing product quality. They also identify stability and inconsistent web and mobile APIs as areas to improve. Tom Occhino argues that code sharing should not come at the cost of an experience that feels right on each platform.

Priorities for the next decade

The panel sees stability, backward compatibility, easier distribution, and simpler brownfield integration as important goals. Charlie Cheever hopes React Native can reach more of the developers building for mobile, while other panelists imagine it extending to AR or adapting to AI-driven development. Their advice to developers includes building valuable products, learning the fundamentals, and contributing to the community.

Takeaways

  • Win support by building products people value, then explain the technology behind them.
  • Prioritize stable APIs and compatibility so teams can maintain apps with fewer upgrade burdens.
  • Share code where it improves team efficiency, while keeping platform-specific user experience in view.
  • Make brownfield integration and app distribution easier to lower the cost of adopting React Native.
  • Build ambitiously, learn how the framework works, and contribute alongside the community.

Mentioned in this talk

Search inside this talk

What was claimed 13

Related talks

Discussion Panel: 10 Years of React Native and Beyond, Charlie Cheever, Mike Grabowski, Nicola Corti, Christoph Nakazawa, Tom Occhino · WhoBuilt