WhoBuilt

Building Universal Super Apps With React & React Native

Jun 10, 2025· 30 min· 2.9K views·Watch on YouTube

An unnamed Callstack founder and early React Native contributor discusses building modular super apps with React, React Native, Module Federation, and Re.Pack at the Codeaholics Meetup.

From bundle splitting to module federation

The speaker frames micro frontends as the architecture behind super apps. Module Federation lets separate teams build and deploy frontends independently, then compose them into one product. On the web, this grew from splitting a single application into cached chunks to connecting separately built applications.

Bringing federation to React Native

React Native traditionally used Metro, which lacked bundle splitting and Module Federation for much of its history. Re.Pack provides a Webpack-based alternative, letting teams share build infrastructure across web and mobile. The speaker also previews work to bring federation support to Metro with Zephyr Cloud.

Building and loading standalone modules

Each module can expose screens and run on its own or inside a host application. The example combines booking and e-commerce modules, with users entering a module from the main app while its team develops it separately. React lazy imports and Suspense load modules asynchronously and show a fallback while they arrive.

Providing an SDK to module teams

A host can provide third-party developers with an SDK instead of implementing every integration around their APIs. React context can supply user data, payments, permissions, and methods at runtime, while hooks give modules access to those services. The same approach can provide shared UI components that work across web, iOS, and Android.

Operating and securing a federated app

Federated modules need deployment and review processes, including a way to upload, approve, release, and roll back code. The speaker describes Zephyr Cloud as one provider and points to a Vietnamese mini-app portal with a manual submission and review workflow. Because modules may share a JavaScript context, teams should consider security audits and separate engine instances to isolate mini apps.

Takeaways

  • Use Module Federation when separate teams need to build and deploy features independently, then combine them in one app.
  • Keep modules runnable on their own so teams can develop and test them outside the host application.
  • Define an SDK that supplies runtime services and shared UI, so module teams can integrate without owning host infrastructure.
  • Plan module submission, review, deployment, and rollback as part of the architecture.
  • Assess shared JavaScript context risks and consider separate engine instances when modules need isolation.

Mentioned in this talk

Search inside this talk

What was claimed 9

Related talks