React Native's shared codebase covers both iOS and Android, which means one maintenance retainer covers both platforms. But both app stores still enforce their own compliance requirements. Two platform changes define maintenance work right now. Google Play requires apps targeting Android 15 or later to support 16 KB memory pages, and from 1 February 2027 it won't accept updates that don't. Apps built with Xcode 27, released in September 2026, fail to launch unless they use Apple's UIScene lifecycle, which React Native supports from version 0.88. Our React Native App Care retainer handles the New Architecture migration, Expo SDK lifecycle, npm dependency audits, and platform compliance across both stores. From £675/month for iOS and Android under one agreement.
50+ apps shipped since 2017
React Native's biggest maintenance advantage is the same as its development advantage: one codebase covers both platforms. Separate native iOS and Android apps mean two codebases and two compliance cycles, so every bug fix is written twice and every platform deadline is handled twice. With React Native that duplicated work isn't there.
The deployment gap is just as significant. Native app fixes wait in Apple's review queue, often for 24 to 48 hours. React Native apps using EAS Update can push a JavaScript bundle fix directly to users' devices in under an hour, with no App Store involvement. We use staged rollouts starting at 10% of users, with Crashlytics and Sentry monitoring before promoting to full rollout. If something looks wrong, we roll back before it reaches the rest of your user base. In a production incident, that difference is meaningful.
Google Play's 16 KB page size rule and Apple's UIScene requirement land on different platforms, and with React Native one retainer handles both. You don't pay for the same compliance work twice, and you don't end up with iOS green and Android blocked because two separate teams are moving at different speeds.
We take over React Native apps from version 0.60 onwards, including Expo managed and bare workflow, apps in any state of New Architecture migration, and codebases from other agencies or freelancers. Onboarding takes 3 to 5 working days and starts with a written audit covering New Architecture readiness, dependency health, EAS credentials, and crash telemetry. The retainer starts after that report is agreed. From £675/month, 3-month minimum.
Written by Gareth Reese, Co-founder, Foresight Mobile
A four-week plan with clear deliverables and a fixed price of £3,500, credited against your first development sprint.
Total client time commitment: 5-7 hours across 4 weeks
We meet with your key stakeholders to understand your business goals, user needs, and technical constraints. You'll share any existing research, designs, or documentation you have.
Our engineering team assesses the technical feasibility, identifies integration points with your existing systems, and evaluates architecture options.
We determine whether Flutter, native development, or another approach makes the most sense for your specific requirements.
We create clickable prototypes so you can experience your app before it's built. You'll test navigation flows, validate the user experience, and gather feedback from stakeholders.
Alongside this, we prioritise features based on business value and technical complexity, mapping out a phased delivery plan with a detailed cost estimate.
You receive your complete Gameplan pack, plus a presentation walkthrough with Q&A. Your team walks away with everything needed to make a confident decision.
A named React Native engineer who tracks SDK releases, manages Expo and EAS, keeps your dependency tree healthy, and handles iOS and Android compliance under one agreement.

Taking over a React Native codebase built by another agency or freelancer is one of the most common conversations we have. The typical scenario: the original team is gone, the app hasn't been updated in 12 to 18 months, it's still running the legacy bridge architecture, several npm packages are abandoned, and a Google Play compliance deadline is approaching.
Our onboarding audit covers React Native version and New Architecture readiness, Expo SDK status (if applicable), EAS credential access, npm dependency health, native module audit (C++ dependencies, Objective-C legacy code), crash telemetry baseline from Sentry or Firebase, and App Store/Play Store certificate status. We assess whether the app needs phased migration or emergency remediation first, then produce a written report before the retainer begins. Onboarding takes 3 to 5 working days. We take over from React Native 0.60 onwards, including Expo managed and bare workflow apps, and apps in any state of New Architecture migration.
Legacy Bridge Assessment • New Architecture Readiness Audit • Dependency Health Report • EAS Credential Transfer • 3 to 5 Day Onboarding • Expo and Bare React Native

Native apps wait days for App Store review. React Native apps don't have to. EAS Update pushes compiled JavaScript bundle updates directly to users' devices, bypassing the app store queue entirely. A production crash that would strand users on a broken app for 48 hours pending Apple's review can be resolved in under an hour via a staged OTA rollout.
Done carelessly, OTA updates cause more damage than they fix. Pushing an untested update to every user at once can put a broken release on every phone before anyone notices. Our OTA protocol uses phased rollouts: 10% of users first, with Sentry and Crashlytics telemetry checked before promoting to full rollout, or a rollback straight away if something looks wrong. From SDK 55 (and by default from SDK 56), Hermes bytecode diffing means each OTA patch is a small binary diff, not a full multi-megabyte bundle download, which matters for users on slower cellular connections. Premium plans add emergency incident response: priority handling in business hours, best efforts outside them.
Staged OTA Rollouts (10% to 100%) • Crash Telemetry Before Full Rollout • EAS Update Rollback Protocol • Hermes Bytecode Diffing • Premium Emergency Incident Response
React Native apps face the same Apple and Google deadlines as native apps, with a JavaScript layer and a C++ dependency chain on top. Google Play requires apps targeting Android 15 or later to support 16 KB memory pages, and from 1 February 2027 it won't accept updates that don't. React Native supports 16 KB pages from version 0.77. The usual blockers are older releases of libraries with native code, such as react-native-reanimated, react-native-screens, SQLite drivers and react-native-vision-camera, built before their maintainers shipped 16 KB-aligned versions. On a phone with a 16 KB kernel, an unaligned library can crash the app or push it into Android's compatibility mode.
On iOS, apps built with Xcode 27 and the iOS 27 SDK, released in September 2026, fail to launch unless they use the UIScene lifecycle. The trigger is the SDK you build against, not the iOS version on the user's phone, so an untouched app keeps running until you next build it. React Native 0.88 (October 2026) added SceneDelegate support: an older app needs upgrading, its entry point moving from AppDelegate to a SceneDelegate, and a scene manifest adding to Info.plist. Apple's upload minimum is still Xcode 26, but Apple has raised it each April, so we plan the change before then. Privacy manifests for third-party React Native libraries also need to be in place for App Store submissions. We schedule both tracks ahead of the deadlines.
16KB Page Size Compliance • UISceneDelegate Migration • Privacy Manifest Updates • App Store + Play Store Rejection Handling • Proactive Compliance Scheduling
A typical React Native app has 50 to 100+ npm dependencies. Some are actively maintained by organisations like Shopify, Callstack, or Software Mansion. Many are not. When a package maintainer goes quiet, the library eventually breaks against an iOS SDK update, a new Android Gradle Plugin version, or a React Native architectural change. The failure is rarely immediate. It surfaces when you're trying to push a compliance update with a Google Play deadline bearing down.
We run monthly dependency audits using npm audit and community indices like reactnative.directory, identifying packages that are deprecated, abandoned, or incompatible with the current React Native version. Where a drop-in replacement exists, we plan the swap. Where it doesn't, we fork and patch. We act on security advisories as soon as they're published.
Monthly npm Audit • Security Patch Management • Deprecated Package Replacement • Native Module Conflict Resolution • Abandoned Package Forking
Expo ships three SDK releases a year, each tied to a specific React Native version. An app left on an old SDK falls behind Apple's minimum Xcode version for uploads, which Apple has raised each April, and eventually can't produce a build the App Store will accept.
We manage the full Expo lifecycle: SDK version tracking, eas.json build profile maintenance, credential rotation (Keystores, Apple provisioning profiles), and App Store Connect API key management. SDK upgrades are tested in a dedicated EAS Build preview profile before promoting to production. For apps using EAS Update, we turn on Hermes bytecode diffing (an option in SDK 55 and on by default from SDK 56), which sends each update as a small binary patch, so downloads on mobile data are much smaller. Recent Expo SDKs run only on the New Architecture, so staying on a supported SDK means migrating, and we plan that migration with you.
Expo SDK Tracking • EAS Build Profile Management • Credential Rotation • OTA Staged Rollouts • Hermes Bytecode Diffing (SDK 55+)
Since React Native 0.82 (October 2025) the New Architecture (Fabric, TurboModules and JSI) has been the only runtime, and the old bridge code is being removed release by release. An app that hasn't moved is stuck on React Native 0.81 or earlier, which no longer gets fixes, and more libraries drop support for the old architecture with each release.
The practical blocker for most apps isn't the core framework. It's the dependency tree. A native module that was never updated either runs through React Native's compatibility layer or blocks the upgrade, so it has to be replaced, forked or rewritten. Our retainer includes a full compatibility audit using reactnative.directory indices: we identify blocking packages, plan replacements or internal forks, and execute the migration in a staged branch with no production disruption.
Hermes V1, the default JavaScript engine since React Native 0.84, is faster too: in Software Mansion's tests on the Expensify app, time to interactive improved by 7.6% on Android and 2.5% on iOS. We handle the migration so you get those gains without the risk.
New Architecture Audit • Fabric + TurboModules Migration • Dependency Compatibility Review • Hermes V1 Optimisation • Staged Branch Testing
Two platform requirements need React Native-specific work on top of normal native compliance.
Google Play 16 KB memory pages: Google Play requires apps targeting Android 15 or later to support 16 KB memory pages, and from 1 February 2027 it won't accept updates that don't. React Native supports 16 KB pages from version 0.77. The usual blockers are older releases of libraries with native code, such as react-native-reanimated, react-native-screens, SQLite drivers and react-native-vision-camera, built before their maintainers shipped 16 KB-aligned versions. On a phone with a 16 KB kernel, an unaligned library can crash the app or push it into Android's compatibility mode. Apps still on React Native 0.76 or earlier need to upgrade first.
Apple UIScene lifecycle: Apps built with Xcode 27 and the iOS 27 SDK, released in September 2026, fail to launch unless they use the UIScene lifecycle. The trigger is the SDK you build against, not the iOS version on the user's phone. React Native added SceneDelegate support in 0.88 (October 2026), so an older app needs upgrading, its entry point moving from AppDelegate to a SceneDelegate, and a scene manifest adding to Info.plist. Privacy manifests for third-party React Native libraries also need to be in place for App Store submissions.
Yes. Agency and freelancer handovers are a significant part of our work. The most common scenario is an app that hasn't been updated in 12 to 18 months, running an old React Native version, with several abandoned npm packages, missing EAS credentials, and an approaching Google Play compliance deadline.
Our onboarding process starts with a structured code audit: React Native version and New Architecture readiness, Expo SDK status if applicable, npm dependency health, native module audit covering C++ dependencies and Objective-C legacy code, crash telemetry review from existing Firebase or Sentry setup, and EAS credential access verification. Where certificates or Keystores have been lost with the previous team, we work with the client to regenerate them through Apple Developer and Google Play Console. Onboarding takes 3 to 5 working days and produces a written report with a prioritised remediation plan before the retainer begins. We take over from React Native 0.60 onwards, including apps in any state of New Architecture migration.
EAS Update is Expo's over-the-air update service. It allows maintenance teams to push JavaScript bundle updates (bug fixes, content changes, minor UI updates) directly to users' devices without going through App Store or Google Play review. A critical production fix that would otherwise take 24 to 48 hours to clear App Store review can reach users in under an hour.
The maintenance implication is that OTA updates require disciplined operational protocols. Pushing an untested bundle to your entire user base at once has caused production incidents. Our protocol uses staged rollouts: starting at 10% of the user base, with Sentry or Crashlytics telemetry monitored before promoting to full rollout. If issues surface, we execute an EAS Update rollback immediately to revert. We also turn on Hermes bytecode diffing (an option in SDK 55 and on by default from SDK 56), which sends a small binary patch to each phone instead of the whole bundle, so updates download much faster on mobile data. This is configured by default for all Expo managed apps on our retainer.
Yes. We maintain both Expo managed workflow apps and bare React Native CLI apps. The maintenance tasks differ significantly. Expo managed apps use Continuous Native Generation (CNG), where upgrades are handled by incrementing the SDK version and regenerating the native directories from your app.config.js. That removes most of the manual CocoaPods and Gradle conflict resolution, so upgrades take less time than on a bare app of similar complexity.
Bare React Native requires full ownership of the native layer: Xcode configuration, Podfile management, Android Gradle Plugin alignment, and manual native module linking. It's more flexible for deep OS integrations (custom BLE hardware, proprietary C++ libraries, advanced ARKit) but more fragile when Apple and Google ship toolchain changes. For Expo apps, we also manage EAS Build, EAS Submit, and EAS Update as part of the retainer, including eas.json profile management, credential rotation, and OTA staged rollout protocols. If your Expo SDK version is approaching end-of-life, we assess the migration path as part of onboarding.
The React Native New Architecture comprises three components: Fabric (the renderer), TurboModules (native module loading), and JSI (the JavaScript Interface). Together they replace the legacy asynchronous bridge that React Native used from its launch until 2025. Since React Native 0.82 (October 2025) the old architecture can't be switched on, so an app that relies on it can't move to a supported React Native version until it migrates.
Migration is not optional for apps with a long-term future on the app stores. If your app uses the legacy bridge, it'll increasingly fail as npm packages drop bridge support and Apple/Google SDK requirements evolve. In practice, migration means auditing your dependency tree for packages that haven't been rewritten for Fabric and TurboModules, replacing or forking those that haven't, then enabling the New Architecture flags. The performance gains are real: Hermes V1 (default since React Native 0.84) cut time to interactive by 7.6% on Android and bundle load time by 9% on iOS in Software Mansion's tests on the Expensify app. We run New Architecture migrations as part of our onboarding assessment and as part of the ongoing Standard and Premium retainers.
Our React Native App Care retainer starts at £675/month. That covers both iOS and Android under one agreement. Billed by the hour instead, maintenance costs swing from month to month, and the expensive months are the ones with a platform deadline, such as an iOS SDK change or Google Play's yearly target API update.
Our fixed monthly retainer removes that unpredictability. Standard is £995 a month and Premium £1,495, or we can price a custom plan for a larger portfolio. There's a one-off onboarding fee of £500 to £1,000 depending on codebase complexity, with a 3-month minimum term followed by rolling monthly billing.
A React Native maintenance retainer covers: React Native version tracking and upgrades; npm dependency audits and security patch management; Expo SDK management and EAS Build/Update/Submit configuration (where applicable); OTA update staging and rollback protocols via EAS Update; iOS compliance including Privacy Manifests, Xcode SDK adoption, and UISceneDelegate migration; Android compliance including target API level, 16KB memory page size, and Gradle/AGP toolchain; crash monitoring via Firebase Crashlytics or Sentry; App Store and Play Store review handling; and monthly health reports covering crash-free rate, ANR rate, and bundle performance.
What it doesn't cover: new feature development (scoped separately), major rewrites, or design changes. Our Essentials retainer at £675/month handles the ongoing compliance and dependency load. Standard (£995/month) adds backend monitoring, an engineer check-in and a priority SLA: on Standard and Premium, we respond to a critical (Severity 1) issue within 2 business hours and aim to fix it within one business day, not counting app store review time. Premium (£1,495/month) adds emergency incident response (priority handling in business hours, best efforts outside them), quarterly architecture reviews and penetration testing. Business hours are 9:00 to 17:30 UK time, Monday to Friday, excluding UK public holidays. Essentials is best efforts, and no plan includes out-of-hours cover.
React Native ships a new minor version every two months, approximately six releases per year. React Native supports only its three most recent minor versions, so in November 2026 anything older than 0.86 (June 2026) is unsupported. The further behind an app falls, the more upgrades stack up before its next iOS or Android build will go through.
In practice, active maintenance involves monthly dependency checks, a React Native version review every quarter, and two platform deadlines a year: Apple's minimum Xcode version for uploads, which last moved up on 28 April 2026, and Google Play's target API level requirement at the end of August. On top of the routine cadence, two platform requirements apply now: the Google Play 16KB page size requirement (required for new apps and updates since 1 November 2025, with non-compliant updates blocked from 1 February 2027), and Apple's UIScene requirement for apps built with Xcode 27 and the iOS 27 SDK, released in September 2026. Both require React Native-specific remediation that goes beyond standard iOS/Android native compliance work.
You've got a working app and nobody reliable to look after it. Maybe your developer handed in their notice. Maybe the offshore team stopped responding. Maybe the freelancer who built it has gone quiet at the worst possible time.
App Care onboarding gets you from that situation to a UK-based team who knows your codebase inside out, with a shared Slack channel and agreed response times. Onboarding takes 3 to 5 working days. The fee is typically £500 to £1,000 depending on complexity, and we waive it, with your first month included, if we've just rescued your app or taken it from no-code to production. After that, App Care starts at £675 a month for both iOS and Android, with a three-month minimum and then rolling monthly.
We start with a short call to understand what your app does, what platforms it runs on, and what the handover situation looks like. Then we request access to the repository (GitHub, GitLab, or Bitbucket), your App Store Connect and Google Play accounts, and any backend infrastructure. If a departing developer is still available, we'll use some of that time to fill in gaps. If not, we work from the code.
We review the architecture, third-party dependencies, security posture, and anything that looks fragile. If there's technical debt that needs fixing before we can support the app properly, we scope that separately so you know what it'll cost. We also build internal documentation covering how the app is structured, where the critical logic lives, and how deployments work.
We add Firebase Crashlytics and Sentry for crash reporting, and set up CI/CD pipelines so releases don't depend on one developer's laptop. Test builds go out through TestFlight on iOS and Google Play's internal testing track on Android.
Your retainer covers OS updates, security patches, App Store compliance, crash investigation, and proactive monitoring. Feature work is scoped and priced separately so you always know what you're paying for. The initial commitment is three months, then rolling monthly with no long-term lock-in. You stay because the service is good, not because you're contractually stuck.
Your app, your way. Here's how we make it happen
Fixed monthly retainer: you know exactly what you're paying and what's covered. No hidden call-out fees, and no surprise invoices when something breaks.
Essentials is £675 a month, Standard £995 and Premium £1,495, or we agree custom pricing, and every plan covers both iOS and Android. All three include monthly OS compatibility updates, crash monitoring, App Store and Google Play compliance checks, a monthly health report and a named contact who knows your app. Standard adds an engineer check-in and a priority SLA. Premium adds emergency incident response (priority handling in business hours, best efforts outside them), quarterly architecture reviews and penetration testing.
We track crash-free session rates, ANR rates and App Store and Play Store review trends through the month, and you see them in your monthly health report. In our experience, catching a problem early costs a fraction of an emergency fix.
You focus on your product roadmap. We make sure the app underneath it keeps working as Apple and Google move the goalposts. New OS? We test before it ships to end users.
We track crash-free sessions for every App Care app in Firebase Crashlytics, and the figures go into your monthly health report alongside ANR rates and App Store and Play Store ratings. In our experience, an app stays stable when the team supporting it knows the product and watches these numbers every month.
We're based in Manchester with offices in London and Birmingham. We think the relationship is as important as the retainer. Drop in whenever you like.

The team has delivered exactly what we asked for but is able to use their own skill and judgment to make improvements.
“They’re more thoughtful than any other development team I’ve worked with..... I’m not sure what they could improve."
"The team has delivered exactly what we asked for but is able to use their own skill and judgment to make improvements"
"Foresight Mobile effectively and promptly met our needs. They were a candid, reliable, and collaborative partner."