WhoBuilt

Actually Distributed Mobile Development at Scale

Sep 9, 2025· 20 min· 971 views·Watch on YouTube

Speaker

Zackary Chapple, CEO and co-founder of Zephyr Cloud, explains how teams can develop and release React Native applications independently at React Universe Conf 2025 with Callstack.

Why growing a mobile app gets difficult

Chapple traces the path from generating and shipping an app to managing updates, app store review, and a growing team. As more developers contribute, a production break can disrupt releases, and partial rollbacks are difficult in a monolithic React Native app.

Lessons from distributed systems

He compares mobile development with the evolution of back-end and web architectures, from monoliths to microservices and micro frontends. He describes the tradeoffs of iframes and independently updated packages, including fragmented tools and many pull requests to coordinate changes.

Module Federation comes to React Native

Chapple presents Module Federation as a way to expose and consume application modules, with a mental model similar to Docker. He outlines its evolution from webpack to Rspack and version 2.0, and describes work with Callstack to add Metro support to Module Federation Core.

Independent releases and environment management

With Module Federation, teams can ship mini apps independently from their own infrastructure, such as an S3 bucket or CDN. Chapple says this can reduce dependence on app store releases, but multiple environments can create unwieldy configuration; he cites one e-commerce company with 250 lines of config.

Zephyr deployments and a customer example

Chapple describes Zephyr as a way to manage environments, tags, versions, and rollbacks for federated modules. He reports a deployment to Cloudflare’s edge in 260 milliseconds and says Southern Glazer’s Wine & Spirits went from releases taking about two months across environments to deploying in under a second after adopting Re.Pack and Module Federation.

Takeaways

  • Break a large mobile app into modules so teams can release at different speeds.
  • Plan how modules resolve across development, staging, and production before configurations multiply.
  • Independent module releases can reduce the need to wait for a full app store release.
  • Keep rollback paths available for each deployed module and environment.
  • Test combinations of mini app versions to speed up field testing.

Mentioned in this talk

Search inside this talk

What was claimed 12

Related talks