Choosing a React Native development company: four checks before you sign
How to evaluate a React Native development company or a single hire: check their live apps on the stores, test their framework currency, ask who owns the over-the-air update pipeline, and get code, accounts and continuity in writing.
Advice from Omnistu, with no statistics, read 22 November 2026: most guides to hiring a React Native development company are written by companies selling exactly that, including this one - Omnistu provides React Native development among its services. So instead of a sales pitch, here are four checks you can run on any supplier, us included, using only public sources and their own answers. Each one catches a failure mode that a polished proposal hides well.
Check one: the stores, not the pitch deck
Ask every candidate for live App Store and Google Play links to apps they have built, then read the listings yourself. Three things matter on a store page: the seller name (an app published under the client's own organization is the model you want; one published under the vendor's account raises the question of who really owns it), the last update date (an unmaintained app tells you what happens after launch), and what reviewers report about reliability. A portfolio of screenshots is a claim; a live listing is evidence - that an app exists and is maintained. It is not evidence that this vendor built it, or that it is React Native at all: a store page shows neither authorship nor framework. For those, ask for a reference at the client company who can confirm the work with their permission, and a technical walkthrough of a comparable codebase. If a company cannot show one live store app comparable to yours plus a reference who confirms it, treat that as an answer.
Check two: framework currency
React Native moves fast, and stale practice is the quiet risk in any quote. Three current facts, all verified 22 November 2026: the latest release is 0.88 per the official versions page; since 0.82 the New Architecture is the only architecture - the release announcement calls 0.82 "the first React Native that runs entirely on the New Architecture"; and Expo's documentation marks the old "managed vs bare workflow" split and "ejecting" as deprecated concepts; the current model is Continuous Native Generation, which Expo recommends but describes as fully optional - you can stop using it at any time. So ask two questions: which React Native version will my app ship on, and what is your upgrade policy after launch? Strong answers name a recent version, describe how they keep third-party native modules compatible, and treat upgrades as recurring work. A proposal still promising to "eject from Expo if needed" is quoting documentation that no longer exists.
Check three: who owns the update pipeline?
React Native apps can update JavaScript and assets over the air, without a store resubmission - within store rules. Ask which update system they use and who controls it, because the landscape changed recently: Microsoft's App Center retired on 31 March 2025, and CodePush, the long-time standard, continues only as a self-hosted standalone version. Expo's EAS Update is the hosted route; Expo's open-source tools are free under the MIT license, while its build, submit and update services are separate paid products. Either way, Apple's rule 2.5.2 (read 22 November 2026) says apps "may not download, install, or execute code which introduces or changes features or functionality of the app" - over-the-air updates cover fixes and assets inside the rules, but anything touching native code, permissions or new features needs a new binary through review. Ask who owns the update channel, how runtime versions are managed so an incompatible bundle is never pushed, and how a bad update is rolled back. "We will set that up later" means you end up owning an unmanaged pipeline.
Check four: ownership, in writing
Nothing about hiring a React Native company automatically gives you the code, the repository, the accounts or the store presence. Those come from the contract and the account setup. Before work starts: repositories under your organization from day one, written IP assignment, store accounts in your organization's name - Apple's own enrollment guidance says the organization whose app it is should enroll in the Apple Developer Program, listed at 99 USD per year, and submit the app, adding hired developers to its team - plus documented signing credentials and environment configuration, and continuity terms covering notice, replacement and handover. A supplier who will not write these down has answered your question.
One developer or a company?
A single strong React Native developer can carry a small app. What one person cannot carry alone is everything around the framework: native modules in Swift or Kotlin for payments, GPS or biometrics, testing across devices, store operations, and continuity when they are unavailable. If you have your own technical lead, a hire or an augmented engineer can work; without one, you need a supplier who brings delivery coordination with them. Our freelancer vs staff augmentation vs dedicated team guide compares the engagement models; the four checks above apply to all of them. And if you are still deciding whether React Native is the right framework at all, start with our React Native vs Flutter comparison.
Red flags worth a walk-away
A guaranteed App Store approval - nobody can promise that; review applies to every submission. A fixed price before any scope is written down. "You will never need native code" - most real apps eventually do. A portfolio without live store links. No answer on post-launch upgrades. And framing that treats Expo as a separate platform rather than tooling around React Native - the current Expo model supports custom native code through development builds, so that either/or is a decade old.
Sources, all read 22 November 2026: React Native, Versions (latest release 0.88); React Native 0.82 announcement ("the first React Native that runs entirely on the New Architecture"; the legacy flag is ignored from this release); Expo, Continuous Native Generation ("managed vs bare workflow" and "ejecting" marked deprecated; CNG recommended but "fully optional, and you can stop using it at any time"); Expo, Develop an app with Expo (open-source tools free under MIT; hosted build, submit and update services separate); Microsoft Learn, App Center retirement (retired 31 March 2025; CodePush continues as a self-hosted standalone version); Apple App Review Guidelines (rule 2.5.2 quoted above; read the current text before relying on it - guidelines change); Apple Developer, Program enrollment (the client organization should enroll and submit; membership listed at 99 USD per year). This guide cites no provider prices and ranks no provider.
Evaluating React Native suppliers for a real product? Omnistu's React Native development page lists how we scope and hand over, and our 20 questions to ask an app development company gives you the rest of the interview - write to team@omnistu.com with what you are deciding.
Frequently asked questions
How much does it cost to hire a React Native development company?
We are not listing rates: they vary by region, seniority and provider, and any number printed here would age badly. Compare written quotes against the same scope and the same written terms, and count your own management time as a cost. For how estimates are built, see our guide to how app development cost is estimated.
Should my React Native app use Expo?
Expo is tooling around React Native, not a separate platform. Its open-source tools are free under the MIT license and support custom native code through development builds; its hosted build, submit and update services are paid products. The old worry about being trapped in a "managed workflow" is deprecated - Expo's current model is Continuous Native Generation, recommended but documented as fully optional. Whether it fits your project depends on your native-module needs and your team's release workflow, not on the label.
React Native or Flutter - does the framework matter more than the company?
The supplier matters more. Both frameworks ship serious apps, and a strong team with the less fashionable choice beats a weak team with the fashionable one. If the framework decision is still open, our React Native vs Flutter guide compares them on real decisions; then run this guide's four checks on whoever builds it.
Are over-the-air updates allowed by the app stores?
Within limits. Apple's rule 2.5.2 (read 22 November 2026) says apps "may not download, install, or execute code which introduces or changes features or functionality of the app" - so JavaScript and asset updates within those bounds are how systems like EAS Update operate, while native code, permission or feature changes need a new binary through review. Read the current guideline text before relying on it, and ask your supplier how they stay inside it.
How do I verify a company's React Native portfolio?
Ask for live App Store and Google Play links, then check them yourself: the seller name on the listing, the last update date, and reviewer reports on reliability. Speak to references at client companies who can confirm the work with their permission - logos on a website are not references, and a store listing alone proves neither the vendor's authorship nor the framework used. Screenshots and case-study PDFs are claims; listings plus permissioned references are evidence.
What should be in the contract before work starts?
Written IP assignment, repositories under your organization from day one, store accounts in your organization's name, named access roles for production and store consoles, a review cadence with acceptance criteria, continuity terms (notice, replacement, knowledge transfer) and exit terms. Ownership comes from the contract and the account setup, not from hiring.