RangeX scores a target in 20 seconds.Read more

Cost & planning

Hire a React Native Developer: What to Check First

Check four things before you hire a React Native developer: a shipped app you can download, current Expo and New Architecture work, native code ability and a contract that leaves the code and store accounts in your name.

Nate Laquis12 min read

What to Check Before You Hire a React Native Developer

Before you hire a React Native developer, check four things: an app they shipped that you can download from the App Store or Google Play today, recent work with Expo and the New Architecture, the ability to write native code when a library runs out, and a contract that puts the code and the store accounts in your name. Most bad hires fail the first check. A freelancer fits a small, well-defined app. An agency fits a first product that needs design, backend and launch together. An in-house hire fits a company with revenue and a roadmap measured in years.

The framework has moved a long way in two years, which is why the date on someone's experience matters more here than it does for Swift or Kotlin. I checked the React Native and Expo release notes on November 15, 2026. React Native 0.88 came out on October 19, 2026. Expo SDK 58 shipped four days earlier, includes React Native 0.88 and is built for iOS 27. The New Architecture has been the default since version 0.76 and the only architecture since 0.82, released in October 2025.

So a developer whose last React Native project ended in 2023 learned a version of the framework that no longer exists. They can catch up. You should not be the one paying for it.

If you have not decided on React Native yet, start with how to hire an app developer, which covers the choice of platform before the choice of person.

Where to Find React Native Developers

There are three places to look, and each one produces a different kind of hire.

Freelance marketplaces

Upwork has the largest pool and the widest spread in quality. Toptal and Arc screen people before listing them and charge more for it. Fiverr works for a small fixed task, like adding a screen or fixing a build, and poorly for a whole product.

The trap on every marketplace is the same. React Native looks like React, so thousands of web developers list it as a skill after one tutorial project. A profile that says React, Next.js, Node and React Native with no store links is a web developer. Filter on shipped mobile apps and nothing else.

The community

The best freelancers rarely need a marketplace. Look at who maintains the libraries your app will depend on, who answers questions in the Expo Discord, and who has written about an upgrade they did recently. Ask two founders with apps you like who built them. A referral from someone who has been through a full build with a developer beats any profile.

Agencies

Directories like Clutch list hundreds of shops, and the reviews are useful mostly for ruling people out. A better route is to find three React Native apps you admire and ask the founders who built them. Then read the agency's case studies and download the apps.

In-house

LinkedIn, Wellfound and referrals. Plan for two to three months from job post to first day for a senior engineer, and remember that someone has to run the interview. If nobody on your team can judge mobile code, pay a senior React Native developer for a few hours to sit in on the final rounds.

What React Native Developers Cost in 2026

These are my estimates of the market. They are not from a survey, so treat them as a starting range and get three quotes.

  • Offshore freelancers: $25 to $60 an hour. The range is wide because it covers a junior in a low-cost city and a senior who has shipped ten apps.
  • Senior freelancers in the US or Western Europe: $80 to $160 an hour. The top of that range buys someone who can write Swift and Kotlin when the app needs it.
  • Agencies: $100 to $200 an hour blended, or a fixed price for the project. The rate covers a designer, a backend engineer, testing and a project lead as well as the mobile developer.
  • In-house, US: $100,000 to $140,000 base for a mid-level engineer and $130,000 to $190,000 for a senior. Add roughly 25 to 30 percent for benefits, payroll taxes, equipment and recruiting.

For a whole product, a simple app on the market runs about $30,000 to $60,000. A mid-sized one with payments, chat, several user roles and an admin panel runs $60,000 to $150,000. Bigger platforms go past that.

Four things move the price. Location is the largest. Seniority is next. Native ability is third, since a developer who can only work in JavaScript is cheaper and stops being useful the day you need a custom camera flow. The last is what the price includes. A freelancer quote covers the app. Ask who is designing it, who is building the backend and who is testing on real phones before you compare it with an agency quote that covers all four.

React Native's saving is real. One codebase and one developer cover iPhone and Android, where native development means two of each. That saving disappears if the developer you hire cannot get through an Android release build.

Two people shaking hands across a desk in an office

Seven Things to Check Before You Sign

A shipped app you can download

Ask for two or three store links and install the apps on your own phone. Use them for ten minutes each. Scroll a long list, rotate the phone, turn on airplane mode, open the app from a notification. Then check the date of the last update and ask what the developer personally built. A screenshot in a portfolio proves nothing. An app in the store with reviews and a recent update proves someone finished.

Expo and the New Architecture

Most new React Native apps in 2026 start on Expo, and the React Native docs recommend a framework like it for new projects. Ask which Expo SDK their last project shipped on, and whether they use development builds and EAS Build or still test only in Expo Go. Then ask about the New Architecture. Version 0.81 and Expo SDK 54 were the last releases that allowed the old one, so anyone maintaining a real app has been through the migration. Ask what broke and which library gave them trouble. A developer who did the work will name it.

Native module ability

Every serious app eventually needs something no library does well. Ask for an example of Swift or Kotlin they wrote for a React Native app, as a Turbo Module or an Expo Module, and what it was for. You do not need a native expert on day one. You need someone who will not be stuck when an SDK from a payments or identity vendor ships with native code only.

App Store submission experience

Submitting is its own skill. Signing certificates, privacy labels, in-app purchase rules, screenshots, review notes and TestFlight all sit between finished code and a live app. Ask how many apps they have taken through App Review and Google Play review themselves, and ask them to describe one rejection and how they got past it. Everyone who has shipped has one.

Code ownership

The repository lives in your GitHub organization from the first commit. The Apple Developer and Google Play accounts are in your company's name, with the developer invited as a team member. The same goes for Expo, Firebase and any analytics or payments account. The contract assigns all work product to you on payment. If a developer wants to publish under their own store account to save time, the answer is no, because moving an app between accounts later is slow and sometimes impossible to do cleanly.

Tests

Ask what they test and how. A reasonable answer is unit tests with Jest on the logic that handles money, sign-in and data, and one or two end-to-end flows in Maestro or Detox that run before each release. Full coverage on a first version is a waste of your budget. No tests at all means every release is checked by hand, and that stops happening around the third month.

How they handle OTA updates

React Native can ship JavaScript changes to installed apps without a store review. It is the fastest way to fix a bug in production and the fastest way to break every user's app at once. Microsoft retired App Center and its hosted CodePush service on March 31, 2025, so most teams now use EAS Update or host their own. Ask which one they use, how they roll an update out to a small share of users first, how they roll back, and how they stop a JavaScript update from reaching a build with different native code. Ask too what they would never push over the air. Anything that changes native code or what the app is for goes through review.

Run a Paid Trial Task

Interviews tell you how someone talks. A trial tells you how they work. Pay for it at their normal rate, keep it to one or two weeks, and make it a real slice of your product so the work is yours to keep.

A good trial task for a React Native developer has these parts:

  1. One screen that loads a list from an API, with loading, empty and error states.
  2. Sign-in, using whichever provider you plan to ship with.
  3. One thing that touches the device, such as push notifications, the camera or location.
  4. A build you can install, on TestFlight for iPhone and on internal testing for Android.
  5. A repository in your organization with a README that gets a second developer running in under an hour.

Then look at what came back. Open the app on a cheap Android phone as well as your iPhone. Read the commit history: small commits with clear messages over ten days, or one large commit the night before the deadline. Count the questions they asked. A developer who asked nothing either guessed at your requirements or did not read them.

Pay attention to how they behaved when something went wrong, since something always does. You want the message that says the push certificate is blocked and here is what I need from you. You do not want three days of silence.

Agencies will not do a trial task, and that is fair. The equivalent is a paid scoping sprint of one to two weeks that ends with a written plan, a screen list and a number. If the plan is vague, the build will be too.

Red Flags

  • No store links. Web projects, GitHub repositories and Figma files are not shipped apps.
  • The app goes in their account. Their Apple account, their GitHub, their Expo project. You are renting your own product.
  • It only works in Expo Go. Expo Go is a sandbox for learning and quick demos. A production app needs development builds, and a developer who has never made one has never shipped.
  • They have not heard of the New Architecture, or call it optional. It has been the only option for more than a year.
  • A fixed price within a day, with no questions. Nobody can price an app they have not scoped. A fast number is a low number that grows.
  • Android comes later. If the plan is to build for iPhone and port afterwards, you are not getting what React Native is for. Both platforms get tested every week.
  • Hourly billing with no demos. You should see a new build every week. Hours without builds are a bill.
  • The team changes after you sign. With an agency, ask for the names of the people who will write your code and meet them before the contract.

One flag on its own deserves a question. Two is a reason to keep looking.

Hand holding a smartphone showing a grid of apps

When React Native Is the Wrong Call

Sometimes the right move is to hire nobody for React Native, because the app should be written in Swift or Kotlin. A good React Native developer will tell you this. One who needs the work will not.

Go native when the hard part of the product is something the phone does, more than something the screen shows.

  • Augmented reality, 3D and games. ARKit, ARCore and a game engine are where that work lives.
  • Heavy media processing. A video editor, a real-time audio tool or a camera app with custom filters spends most of its code in native frameworks.
  • Constant hardware work in the background. A Bluetooth device that syncs all day, or continuous location tracking with tight battery limits.
  • A product built around the watch, widgets or CarPlay. React Native can host these, but each one is written natively anyway.
  • New OS features on release day. If your pitch depends on an API Apple announced in June, you will be writing Swift.
  • One platform, for good. An iPhone-only product with a Swift engineer already on the team gains little from a second language.

In those cases read how to hire an iOS app developer or its Android counterpart and hire for the platform.

The list is shorter than founders expect. Most products are feeds, forms, profiles, payments, chat, maps and notifications, and React Native handles all of them on both platforms from one codebase. It handles more than that, too. Vybes is a members-only dating app we built in React Native for iOS and Android, with real-time WebRTC video calling and ID verification. It went from concept to the App Store in 8 weeks and holds a 4.8 rating.

When an Agency Is the Wrong Call

We are an agency, so weigh this section with that in mind. In these situations I would tell you to hire someone else.

The job is small. One feature, a bug, an upgrade from an old Expo SDK. A senior freelancer will finish before an agency has scheduled the kickoff.

You have a technical cofounder. If someone on your team can set the architecture and review code, you need hands. Hire one or two contractors who report to that person.

Your budget is under about $20,000. A good agency will turn the project down. A bad one will take it and staff it with juniors. Cut the scope to something one freelancer can ship, or build a clickable prototype and raise money with it.

The app is the company and the money is in the bank. If you have funding, paying users and three years of roadmap, the knowledge of how the product works should live with employees. An agency can ship the first version and hand it over, and it should not be your engineering team in year three.

You cannot give it time. An agency needs a decision-maker for a few hours every week. Without one, the team builds its best guess and you pay for the guess twice.

The reverse is also true. A freelancer is the wrong call when the product needs design, a backend, two store launches and someone to hold the plan together, because one person is now doing four jobs and you are managing all of them.

Application code on a dark screen

Freelancer, Agency or In-House

Here is the pick for each situation I see most often.

  • A non-technical founder with a first product and a launch date: an agency. You need design, mobile, backend and store submission from one team that has done it together before.
  • A small app with screens already designed and a simple backend: a senior freelancer, after a paid trial.
  • A technical founder who needs more hands: one or two freelancers working in your repository under your review.
  • An existing React Native app that is stuck on an old version: a freelancer or a small agency for a fixed upgrade project. Ask for the migration they did most recently.
  • A funded company with paying users and a long roadmap: hire in-house, starting with one senior engineer who can do native work. Use an agency to keep shipping while you recruit.
  • A product that is mostly AR, media processing or hardware: a native developer, and skip React Native.
  • A budget under $20,000: a freelancer and a smaller first version.

Many companies use all three over time. An agency ships the first version, a freelancer covers the gap after launch, and the first full-time engineer arrives once revenue supports the salary. The longer comparison is in in-house vs agency vs freelance.

Whoever you pick, run the same checks. Download their apps. Ask about Expo, the New Architecture and the last native module they wrote. Put the repository and the store accounts in your name before any code is written, and pay for a short trial before a long contract.

This is what we do. We design and build React Native apps for founders, on iPhone and Android, from the scoping call to the App Store, with a weekly demo and the code in your repository. We have launched fifty products. If you are about to hire for a React Native app and want a plan and a number first, book a free strategy call.

hire react native developerReact Native developer ratesReact Native agencyExpo developerfreelancer vs agency

Get your number.

Thirty minutes. You leave with a plan and a number.

Book a free call