Between 9 December 2025 and 8 January 2026, 3,501 developers answered the annual State of React Native survey. 74.41% now build on the New Architecture and 86.18% start their projects with the Expo CLI. Those two numbers change what it means to hire React Native developers: the framework a candidate learned in 2022 and the framework running in production today diverge in exactly the places that break builds.
Search for how to hire React Native developers and you get vetted-expert landing pages, a rate table by seniority, and a four-step process diagram. None of them tell you how to separate a React Native engineer from a React web developer who can run npx expo start and get a login screen onto a simulator. That distinction decides whether your app ships or stalls at the first native dependency. When you hire React Native developers, you are buying native mobile competence that happens to be written in JavaScript, and the screen below is the one our React Native team runs on candidates.
The real job description for React Native developers
React Native sits in an awkward place on a CV. The language is JavaScript, the libraries look like React, and job listings often get written by someone who hires web developers. What the role demands lives one layer down, in the native build systems that JavaScript never touches.
The React Native developer role in 2026
A React Native developer builds iOS and Android apps from a single JavaScript or TypeScript codebase, using React components that render to real native views. The role covers three layers: the JavaScript application code, the native build pipeline for both platforms, and the bridge between them, including native modules written in Swift and Kotlin when a device feature has no maintained JavaScript wrapper.
That third layer is where hiring goes wrong. Most of the work on a healthy React Native project is JavaScript, and a strong React web developer can carry it. The rest sets your release schedule. Camera access, Bluetooth pairing, background location, biometric login, in-app purchases: each one either has a maintained library or needs someone who can read Apple’s and Google’s documentation and write the glue.
The gap between a React web developer and a React Native developer
A React web developer moving to mobile already has the component model, hooks and state management. Here is what does not transfer:
- The build pipeline - Xcode, Gradle, provisioning profiles, signing certificates, CocoaPods, Android SDK versions. Nothing in web work prepares you for a build that fails on a teammate's machine over an Xcode minor version.
- Native modules - when a library gets abandoned or a device feature has no wrapper, someone writes Swift and Kotlin.
- Gestures and animation - reanimated and Gesture Handler run on the UI thread and carry their own mental model. A developer who reaches for
setStateon every drag frame ships an app that stutters on a mid-range Android phone and feels perfect on their own iPhone. - The permission model - iOS and Android disagree about when to ask, what to ask for, and what happens after a refusal. App Review rejects vague permission strings.
- Background work and push notifications - silent notifications, background fetch, and what each OS kills while your app sleeps.
- Offline state - phones lose signal in lifts and underground car parks, so a mobile app queues writes and reconciles them later.
- Store review - two queues, two rulebooks, rejection cycles measured in days.
A React developer can still be the right hire. The ramp is real, though: a month or two of supervised shipping before they own a release. If the framework choice itself is still open on your side, how cross-platform mobile development works covers that decision first.
The architecture reset that changed what experience means
React Native shipped a rewritten core, and the rollout has finished. Four milestones matter when you read a CV:
- October 2024 – React Native 0.76 makes the New Architecture the default for all projects.
- 2 June 2025 – the maintainers freeze the legacy architecture codebase: "we will no longer accept PRs against the legacy architecture, nor will we develop new features for it."
- 0.81 – opt out of the New Architecture and, in the team's own words, "you'll be on your own."
- 0.82 – support for the old architecture drops entirely.
So "five years of React Native" describes two different people. One has migrated apps to Fabric and TurboModules, debugged a native module that broke on the way, and knows which libraries still lag behind. The other last shipped on 0.68 and will meet all of it on your project, on your budget.
Ask early which React Native version a candidate's last production release ran, and whether it used the New Architecture. Anyone who cannot answer in a sentence has not been near a recent upgrade.
The technical screen for React Native developers
You do not need to read Swift to screen a React Native developer. You need a handful of questions with answers you can check, plus a few artefacts that any real practitioner produces without hesitation. All of it fits in a 30-minute call.
Expo or bare React Native CLI
This is the fork in the road, and stale knowledge shows up here fastest. In the 2025 survey, 86.18% of respondents used the Expo CLI. Expo has been production-grade for years: Continuous Native Generation and config plugins let you add native code while keeping the managed workflow, which is what closed the old argument.
| Expo managed + EAS | Bare React Native CLI | |
|---|---|---|
| Who you need | A developer comfortable with config plugins and EAS Build | A developer also fluent in Xcode and Gradle |
| Native code | Added through config plugins, regenerated on each build | Committed directly into ios/ and android/ |
| Releases | EAS Build and EAS Update handle CI and over-the-air patches | Your own CI, your own signing setup |
| Where it hurts | A vendor SDK with no plugin means writing one | Every framework upgrade is a manual merge of native folders |
Bare still wins in narrow cases: an SDK from a vendor who ships no Expo plugin, a build pipeline your security team already audited, an existing bare app nobody wants to migrate. A candidate who calls Expo prototype-only has not looked at it since 2022, and that single answer dates someone faster than any framework list on a CV. For a wider view, the other multiplatform frameworks sit side by side here.
Three questions, and three things to ask for
Three questions do most of the filtering.
- Which React Native version was your last production release, and did it run the New Architecture? A good answer names a version and tells a migration story, including something that broke. A version number with no detail, or a shrug about the architecture, means the migration happened around them rather than through them.
- Walk me through the last native module you wrote or patched. Strong answers get specific fast: the device feature, the platform that fought back, the Swift or Kotlin file. "I use libraries for that" is fine from a junior and a problem from anyone billing as senior.
- How do you get a build onto a tester's phone? TestFlight, an internal Android track, signing keys, and who holds them. Anyone who has shipped answers in thirty seconds; anyone who has only built features hesitates.
Then ask to see three artefacts:
- A store listing. A live App Store or Google Play URL for a build they worked on, plus a straight answer about which parts were theirs. Portfolio screenshots prove nothing.
- A build log or CI configuration. EAS, Bitrise, Fastlane, GitHub Actions: anything showing they have automated a release instead of clicking Archive in Xcode on their laptop.
- Code they can talk about. A repository, a merged pull request, an npm package. The talking matters more than the code.
Red flags when hiring React Native developers
Some warning signs belong to this framework specifically:
- No opinion about Expo. Every working React Native developer has one, usually a strong one.
- A CV heavy on React web work with one mobile project bolted on the end. Ask what they did on it. The answer is often "the screens."
- Never opened Xcode. Possible on a well-run Expo project, and still worth probing: what happens the day a build fails with an error in Objective-C?
- Claims React Native matches native performance everywhere. It gets close, and long lists, maps, animations and image-heavy screens need deliberate work. Anyone who has hit those limits will say so unprompted.
- No Android device. Testing only on an iPhone simulator produces apps that fall over on the phones half your users carry.
- Talks about the bridge as current. The bridge is what the New Architecture replaced. Vocabulary dates people.
The places to hire React Native developers, and the going rates
Where you look shapes who you get, and what you pay shapes how long they stay. Both are more predictable than the vendor pages suggest.
The four places React Native developers come from
- Marketplaces like Upwork, Toptal, Fiverr Pro and the vetted-talent networks. Fast, with generic vetting: they test JavaScript thoroughly and mobile release engineering barely at all, so screen anyway.
- The React Native ecosystem itself. Maintainers of libraries you already depend on, speakers at App.js and React Native EU, active accounts in r/reactnative and the Reactiflux Discord. The strongest freelance React Native developers tend to be visible here and invisible on job boards.
- Software houses with a standing team. You get continuity, code review, and someone to call when the person who wrote your camera module goes on holiday. You pay a margin for that.
- Referrals from your own engineers. Slowest route, highest hit rate.
React Native developer rates in 2026
Rates track geography and release experience more closely than years on a CV. In Central and Eastern Europe, a competent React Native developer runs $25–60 per hour, where the top of that band buys someone who has migrated an app to the New Architecture and written native modules. North American agencies quote several multiples of it. Marketplace freelancers cluster lower and vary enormously in what they can finish.
The hourly rate leaves out the line items that break budgets: an Apple Developer Program membership at $99 a year, a Google Play Console account at $25 once, EAS or CI minutes, and the review cycles nobody puts in the plan. For the whole-project view, what a full custom mobile build costs breaks the numbers down, and nearshore rates and time-zone overlap covers the geography question properly.
Right-sizing your React Native team
One React Native developer can build and ship a straightforward app, and that person is a single point of failure the moment they take leave. Two is the first stable configuration: one owns releases, the other reviews. Once the app carries real offline state and syncing, add a backend developer before you add a second mobile developer, because the bottleneck usually moves off the phone.
The native question arrives on almost every project, usually sooner than the roadmap assumed: the first device feature with no maintained wrapper needs someone who writes Swift and Kotlin. Our own developers write those modules themselves, which is why our React Native team keeps 5 dedicated developers on the framework, with roughly 20 React Native apps shipped between them, instead of pairing a JavaScript generalist with an outside native contractor. IMS Audio Player and Koneser both needed that kind of work: audio playback for public spaces, and QR scanning for species identification. Ramp-up on a standing team runs under two weeks against a market norm of two to four.
FAQ – hiring React Native developers
How much does it cost to hire React Native developers?
At the $25–60 per hour common in Central and Eastern Europe, two developers on a three-month build come to roughly $25,000–58,000 in developer time. Budget separately for a designer, QA on real devices, and the store accounts. Most overruns on these projects trace back to paying twice, after a first hire who could not get a signed build into the App Store.
Can a React developer work as a React Native developer?
Often, given a ramp of a month or two. The component model, hooks, TypeScript and state management transfer directly; the build pipeline and the store process do not. Give them a real feature inside a project that already releases cleanly, rather than a greenfield app where they have to invent the pipeline as they learn it. Someone else's working release process is the cheapest classroom available.
Should I hire React Native developers who only know Expo?
For most projects, yes. The 2025 community survey put Expo CLI usage at 86.18% of respondents, which makes it the mainstream path. Check three things:
- They can write or adapt a config plugin when an SDK needs native setup.
- They have used EAS Build and know how over-the-air updates interact with store review rules.
- They can explain when a project genuinely needs to leave the managed workflow.
Answers to all three mark a developer who understands the workflow end to end. A candidate whose Expo experience stops at expo start in development still has the release half to learn.
How do I verify a React Native developer's experience without a technical background?
Buy a small paid trial task and have a developer you trust review it. Shape the task so it exercises the parts a CV cannot prove:
- A screen that reads from a device permission, so they handle the refusal path.
- A release build delivered through TestFlight or an internal Android track, so you watch it install on a real phone.
- A short written note on which libraries they chose and why.
An hour of a trusted developer's time costs a fraction of a bad three-month hire, and the trial surfaces the release skills that interviews reward people for describing well.
How long does it take to hire React Native developers?
A marketplace freelancer can start within a week, most of which goes on screening. A software house with a standing React Native team usually assigns people in under two weeks. Direct hiring runs six to twelve weeks in most markets, and longer when you hold out for senior candidates with native module experience, because there are not many of them.
Is React Native still a safe choice in 2026?
The framework is maintained by Meta, and it finished a full architecture rewrite in 2025 without fracturing its library ecosystem. The community survey drew 3,501 responses, New Architecture adoption passed 74%, and 78.7% of respondents have either migrated or plan to. Where React Native projects fail, the cause is usually the hire rather than the framework.
