WhoBuilt

Native Apps Without a Build Step

Jun 4, 2025· 43 min· 726 views·Watch on YouTube

Speaker

Michal Pierzchala, principal engineer at Callstack, explains how the React Native Enterprise Framework can reduce native build work and simplify adoption at the React Universe Meetup in April 2025.

React Native teams face varied constraints

Pierzchala describes teams maintaining long-lived React Native apps, supporting more than 10 platforms, and moving engineers between web and mobile work. Some companies rely on the Community CLI because they cannot or do not want to adopt Expo. Others need alternative bundlers such as Re.Pack with Rspack or webpack.

A framework for enterprise teams

Callstack is building a framework for large teams using the Community CLI, with migration intended to take about 10 minutes. Its design emphasizes modular plugins, support for power users, self-hosting, and incremental adoption. Teams can choose a bundler, add plugins and platforms, and configure a remote cache provider.

Reuse native builds from CI

The remote cache lets developers download a native app artifact built by CI when its fingerprint matches the local project. In an Expensify demo, a cached iOS app was downloaded and launched without a local native build. Pierzchala showed that many CI runs reused artifacts, while an actual iOS build could take around 28 to 30 minutes; the cached run took seconds, in addition to setup such as npm install.

Simplify React Native in native apps

Pierzchala says the usual brownfield setup can require a React Native compatible directory, npm dependencies, CocoaPods, and changes to native build configuration. The framework’s approach packages the React Native app as a platform framework, such as an XCFramework for iOS, for native engineers to configure and import. He says Callstack has used this approach with clients for over five years and has now open-sourced it.

Try it and follow the roadmap

The project is called React Native Enterprise Framework, and developers can start a new project with `npm create rnef-app`. Existing Community CLI apps can migrate manually today, with automation planned for the future. The roadmap includes more platform support, self-hosted over-the-air updates, continuous native generation, additional cache providers, React Server Components, and Module Federation support.

Takeaways

  • If JavaScript changes leave the native project fingerprint unchanged, a team may be able to reuse a CI-built app instead of rebuilding locally.
  • Measure the time saved against setup costs such as dependency installation; a cache hit does not remove every step.
  • A modular CLI framework can let enterprise teams choose bundlers, plugins, platforms, and cache providers to fit existing infrastructure.
  • Packaging React Native as a framework may make brownfield adoption easier for native teams that want to avoid integrating npm and CocoaPods into their app build.
  • Teams on the Community CLI can assess the framework incrementally, while accounting for manual migration in its current state.

Mentioned in this talk

Search inside this talk

What was claimed 16

Related talks