React Native, one shared codebase.

Expo (managed with dev client) for 85 percent of modern React Native projects. The dev client workflow lets you add most native modules Expo does not include out of the box, so the old objection of 'Expo cannot do X' is outdated in 2026. Bare workflow only when you need deep native work that cannot live behind an Expo config plugin: custom Bluetooth stacks, specialized camera pipelines, background audio processing, or hardware-specific integrations. Team size and native expertise also matter. For teams of 2 to 4 engineers shipping a standard app, Expo wins. For teams with dedicated iOS and Android engineers already in place doing specialized native work, bare may fit.

US and UK senior React Native engineers are $145 to $200 per hour at boutique agencies; Indian senior engineers are $85 to $140 per hour. A standard React Native MVP with Expo Router, auth, push notifications, OTA updates, and store submission runs 10 to 16 weeks. A full production build with native module bridges, offline sync, in-app purchases, and deep links runs 14 to 22 weeks. A rewrite from native iOS or Android runs 16 to 26 weeks depending on feature count. A 2-week audit is refundable. Scoped quote in 48 hours.

Over-The-Air (OTA) updates via EAS Update let you ship JavaScript bundle changes directly to users without an App Store or Play Store review. JS-only changes (bug fixes, content updates, feature flag flips, new screens that use existing native modules) reach users in minutes instead of 1 to 7 days. Native changes (new modules, permission changes, icon changes) still require a store submission. OTA matters because it decouples JS velocity from store review cycles, lets you roll out fixes same-day, and supports channel-based staged rollouts (beta, canary, production).

Three paths. One, use an existing Expo module (expo-camera, expo-notifications, expo-location cover most needs). Two, use a community module with an Expo config plugin (most major libraries have these now). Three, write a custom Expo module when the need is genuinely unique. The Expo Modules API in 2026 is mature enough to write Swift and Kotlin native code inside an Expo project, so 'we need custom native code' is no longer a reason to leave Expo. Only when the native work is large enough to justify dedicated iOS and Android engineers do we recommend bare.

Yes. For simple offline (cached API responses, offline queue of pending writes), TanStack Query with persistent cache via AsyncStorage or MMKV handles most cases. For full offline-first (collaborative editing, complex sync, conflict resolution), WatermelonDB or Legend State plus a custom sync layer is the pattern we ship. For the hardest case (offline-first with CRDTs or operational transforms), Replicache or PowerSync via a managed backend. Offline-first adds 4 to 8 weeks to the scope; we map the offline requirements in week one.

expo-notifications for the client side; Firebase Cloud Messaging (FCM) on Android and APNs on iOS as the delivery providers. On the backend we integrate with a provider: Expo Push (for small volume), OneSignal or Customer.io (for marketing and rich notifications), or direct APNs/FCM via a backend service for full control. Critical UX details: permission prompts are shown at the right moment (not on app launch), not-opted-in state is handled, silent push for background data is measured and respected by iOS throttling rules.

EAS Submit handles both stores from command line. Before first submit, we set up App Store Connect and Google Play Console accounts under your organization, configure signing certificates (managed credentials via EAS), write store listings, create screenshots in every required size (we have a Figma template for this), prepare privacy labels and data safety forms. First submit typically takes 1 to 3 days of review on Apple, same-day on Google. We run a dry-run against the review guidelines internally before submitting. First rejection rate is rare but handled by same-week fix and resubmit.

You do, fully. GitHub repository under your organization. Apple Developer Program membership and Google Play Developer account under your legal entity. EAS account and signing certificates under your EAS organization with DH engineers as named collaborators removable any time. Push notification provider (Expo Push, OneSignal) under your billing. On exit: repository transferred, credentials rotated, store access handed off, 30-day support tail. No lock-in through signing, tooling, or vendor choice.