23 posts
Series: RN Module FederationState ManagementRN FoundationsHiring
The CDN goes down and the app still starts, from a copy of each remote built into the binary. In a CDN launch, a remote that fails to load drops to its own copy while the other stays on the CDN, and Try again finally retries.
Every launch, the app asks the CDN which remote versions it may run. Then an operator ships a new one to an installed app with one directory and one line of JSON, and rolls it back the same way. Plus what Apple and Google permit, quoted from the current texts.
The remotes leave the dev server: built for production, signed at build time and served from a CDN that is a directory and a port. The registry sits in the middle, and one table says which changes still cost an app-store release.
A remote ships JavaScript only, so the host lends it a native screen through one promise: a routing table, a TurboModule, and a Quick Battle in SwiftUI and Compose built so every exit settles the promise.
A shared testing package gives every remote the same WCAG bar: contrast, touch targets and status semantics checked in the packages that own them, each team's own screens checked in its own suite, and a failing test that found a button nobody could measure.
Three federated apps carry three copies of the same greys until a design-system package moves to the seam: gluestack-ui components and NativeWind under Re.Pack, one shared singleton, and one theme toggle that re-themes every remote at once.
The same PokéAPI data arrives over REST and GraphQL through one RTK Query slice, one tag invalidates across both, and the honest question is when Apollo's normalised cache is worth two caches during the transition.
TanStack Query and Zustand rebuild the app Redux Toolkit and RTK Query just built; both work, and what separates them is what happens when independent teams stop coordinating.
A remote injects the slice it alone owns into the shared store, the contract carries the one action that crosses, and a write arrives as a prop; dispatch before the slice exists and the add vanishes in silence.
Who owns a boundary, a component, a data definition? Five tests for cutting a federated React Native app along team lines, and what moves each answer.
A remote and an installed package inject their endpoints into one host store and share one cache; get the sharing wrong and the screen hangs on a spinner that never resolves.
RTK Query tags and TanStack Query keys look interchangeable in single-team code. At multi-team scale they change what fails when teams drift out of sync.
Server state and client state have different requirements. Why modern React stacks split the job between two libraries instead of one store.
No app can see what the others ship. Two packages, published and installed by version (a typed contract and the shared detail screen), give every side one definition and let 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.
An argument for organising React Native projects by feature, not by type. The delete test, import boundaries, where shared code lives.
Detox + Cucumber for React Native E2E. Step definitions, a custom formatter, parallel execution, and accessibility regression tests in plain Gherkin.
Tokens don't belong in AsyncStorage. How SecureStore, an encrypted store and AsyncStorage split the job in React Native, and what goes where.
Setting up Mock Service Worker v2 in React Native, from installation to a full set of handler scenarios: success, errors, timeouts and offline.
Practical advice from someone who reviews take-home tech test submissions. What actually matters, what doesn't, and the mistakes that cost candidates the job.
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.