One shared store: server state across federated remotes in React Native
A remote loaded at runtime injects its endpoint into the host's store and shares one cache; get the sharing wrong and the screen hangs on a spinner that never resolves.
A remote loaded at runtime injects its endpoint into the host's store and shares one cache; get the sharing wrong and the screen hangs on a spinner that never resolves.
The host can't see what a remote exposes. A contract package, published and installed by version, gives both sides one definition and lets semver govern drift.
Turn the host from a single screen into a real app shell: it owns the tab bar and navigation, and each tab is a remote built, shipped and loaded on its own.
Share react, react-native and a native library across a host and its remote the right way; getting it wrong crashes the app on launch, not quietly.
Two React Native apps, one loading the other's screen at runtime over Module Federation 2.0 with Re.Pack. Every step copy-paste, ending in a running app.
What runtime micro-apps buy a React Native app, what they cost, and when the trade is worth it. Intro to a series that builds a federated setup from scratch.
Engineering leadership, React Native, and building teams — in your inbox when something new goes live. No spam.
Double opt-in. Unsubscribe any time. · Privacy
Something went wrong. Please try again in a moment.
Almost there — check your inbox to confirm your subscription.