Module Federation in React Native via Re.Pack allows large mobile apps to split into independently owned runtime modules, each with its own build pipeline and JavaScript release process. The host app ships through app stores and owns the native shell, while remotes are separately built JavaScript modules loaded at runtime. Key constraints include: remotes can only use native modules already in the host binary, React/React Native versions must stay aligned, and runtime delivery introduces failure modes requiring fallback UI, rollback paths, monitoring, and compatibility checks. The pattern fits super apps and enterprise platforms where multiple teams own distinct product areas and release coordination is a bottleneck. Teams should start with one remote, validate the host contract, and measure real-world performance before scaling. Simpler alternatives like shared packages or code splitting should be preferred when runtime independence isn't genuinely needed.
