A remote is built and shipped on its own, so the host can't see what it exposes. A shared contract package, published to a registry and installed by version, gives both sides one definition. Then semver governs what happens when they drift.
Turn the host from a single screen into a real app shell. It owns the tab bar and navigation; each tab is a separate remote, built and shipped on its own, loaded at runtime.
Share react, react-native, and a native library across a host and its remote the right way, and see why getting it wrong crashes the app on launch instead of failing quietly.
Build it from zero: 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 making. The 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.
Three React Native storage tiers: Keychain for tokens, encrypted store for PII, AsyncStorage for preferences. When to use each, and how Redux Persist fits in.
A practical guide to setting up Mock Service Worker v2 in a React Native project. From installation to a full set of handler scenarios covering 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.