Softellar

React Native Staff Augmentation

React Native Staff Augmentation for iOS and Android

A React Native app is one codebase that ships as two native apps, each with its own store, its own review and its own native code underneath. A React Native engineer from our in-house team joins your codebase and works in your repository, your reviews and your releases. You lead the work.

Discuss your React Native app

We reply within 24 hours

Companies we have built software for

  • Multi Radiance Medical
  • Loma Lux Laboratories
  • WellVu
  • Commercial Capital Group
  • Grand Auto
  • HostMy
  • Land Base
  • Auto Tuning

Where iOS and Android Part Ways

Most of a React Native app is one codebase. The work an engineer is added for is often lower down, where it becomes two.

One codebase

  1. 01

    Screens and features

    • React Navigation

    Where it goes wrong

    A screen checked on an iPhone ships with the keyboard covering the form on Android, or the back button closing the app.

    What the engineer adds

    Every screen run on both platforms before review, with safe areas, the keyboard and the back button handled in one place.

  2. 02

    Long lists and animations

    • Reanimated

    Where it goes wrong

    A list renders every row at once, and an animation run from JavaScript stutters whenever JavaScript is busy.

    What the engineer adds

    Lists that render what is on screen, animations that run on the UI thread, and startup time measured on a mid-range Android phone.

  3. 03

    Offline data and sync

    • SQLite
    • Realm
    • MMKV

    Where it goes wrong

    A form filled in with no signal is lost, or sent twice when the signal returns.

    What the engineer adds

    Data kept on the device, a queue of changes waiting to send, and a sync that is safe to repeat.

  4. 04

    Code shared with the web app

    • TypeScript
    • TanStack Query
    • Redux Toolkit
    • Zustand

    Where it goes wrong

    A helper that reaches for the browser is imported into the app, which then crashes at launch.

    What the engineer adds

    A shared package for types, validation and the API client, with screens written for each platform.

Two platforms

  1. 05

    Push notifications and deep links

    • Firebase
    iOS
    Apple’s push service and Universal Links
    Android
    Firebase Cloud Messaging, notification channels and App Links

    Where it goes wrong

    A tap on a notification opens the home screen, not the job, when the app was closed.

    What the engineer adds

    One handler for a link from a notification, an email or a cold start, and the permission asked when the user can see why.

  2. 06

    Native modules

    • Swift
    • Kotlin
    iOS
    Swift, built in Xcode
    Android
    Kotlin, built in Android Studio

    Where it goes wrong

    The SDK for a scanner, a camera or a payment terminal has no React Native package, or the package stopped being maintained.

    What the engineer adds

    A thin module in Swift and Kotlin behind one typed interface, so screens call it the same way on both.

Mobile and React in Production

Products where our engineers built the mobile app or the React front end, the two sides React Native joins.

United States

Imaging Data Processing For A Healthcare Technology Company

High-performance thermal imaging data processing solution for healthcare technology providers.

  • Java SE
  • OpenCV
  • Android SDK
  • Kotlin

A Release Is Not a Deploy

A web fix is live in minutes. A mobile fix may wait for store review, and the old version stays on phones until each user updates.

One fix, two routes to a phone

A JavaScript fix

  1. 1Merged
  2. 2Published as an over-the-air update
  3. 3On phones at the next launch
  4. Only JavaScript, styling and images, and only to builds with compatible native code.

A fix that touches native code: A new SDK, a permission or a React Native upgrade

  1. 1Merged
  2. 2Built and signed for each store
  3. 3TestFlight and Google Play test tracks
  4. 4Store review
  5. 5Staged rollout
  6. 6Users update over time
  7. Store review and each user’s update are outside your team’s control.

Versions still on phones

  • Version 4.358%
  • Version 4.230%
  • Version 4.112%

The API keeps serving all three until the oldest is retired.

What the engineer sets up

Need the whole app built? React Native development covers a new app or a rebuild, as a project we run.

React Native development services

Clients on the Apps We Built

A native Android app, a React front end and an enterprise application, each quote linked to the project behind it.

React on Top, Native Underneath

React Native staff augmentation adds a React Native engineer to your mobile team, and you lead the work.

The engineer writes screens in React and TypeScript, drops into Swift or Kotlin when a feature needs the platform, and takes a build through both stores.

The goal

One codebase that behaves like a native app on both platforms, with releases you can take back.

Tools, by the job they do

Screens and navigation
  • React Navigation
State and server data
  • Redux Toolkit
  • Zustand
  • TanStack Query
Animations
  • Reanimated
Data on the device
  • SQLite
  • Realm
  • MMKV
Native code
  • Swift
  • Kotlin
Tests
  • Jest
  • React Native Testing Library
  • Detox
  • Maestro
Builds and releases
  • Expo Build
  • Expo Update
  • Fastlane
  • TestFlight
Crashes and analytics
  • Sentry
  • Firebase Crashlytics
  • Firebase Analytics
With Expo
  • Expo
  • Expo Build
  • Expo Update
Without Expo
  • React Native CLI
  • Xcode
  • Android Studio
TypeScript across all of it, in an app built with Expo or with the React Native CLI.

Waiting on a Store Review?

Tell us what the app runs on and what is stuck, and an engineer will tell you who we have.

We reply within 24 hours and can sign an NDA first.

Have files or a long brief? Use the full form

Before the First Build Is Installed

Four questions we ask before proposing a React Native engineer, then the five steps to their first two weeks.

What we ask

  1. 01

    Which React Native version it runs, and whether it uses Expo

    For exampleReact Native 0.74 on Expo, with the New Architecture still turned off

    So the engineer knows which libraries the app can use, and how far it is from the current version.

  2. 02

    Which native modules it depends on

    For exampleA barcode scanner SDK, a Bluetooth printer and one module written in-house in Swift

    So the engineer knows which parts need Swift or Kotlin, and which could hold up an upgrade.

  3. 03

    Who can release, and how a build reaches each store

    For exampleOne developer builds on a laptop and uploads to TestFlight by hand

    So the first release does not wait on a signing key or a store account only one person holds.

  4. 04

    Which app versions are still on users’ phones

    For exampleThree versions, the oldest from last spring

    So a change to the API does not break the version some users never updated.

Then, in this order

  1. 01Brief

    You answer these questions, plus the role, the seniority and the start date.

  2. 02Shortlist

    We match the brief against our in-house engineers and send the profiles that fit.

  3. 03Interview

    You test them the way you would test your own hires, then pick who joins.

  4. 04Order

    A short order under the master services agreement names the engineer, the rate and the start date.

  5. 052-week trial

    The engineer joins your standups and opens a first pull request in week one.

Terms at a glance

Read the full agreement
Start
Often within 48 to 72 hours
Trial
The first 2 weeks, before any long-term commitment
Replacement
Within 48 hours, at no extra cost
Notice
One month to scale up or down, with no penalties
IP
Full ownership assigned to you under the MSA
Working hours
Standups and reviews from 2 to 6 PM CET, the US morning

US Office, European Engineering

Headquartered in Warsaw, Poland, with a client office in New York. A European engineering team that works in your hours, with a US point of contact.

Headquarters

Warsaw, Poland

Engineering and delivery, and the main contact point for clients in Europe.

Client office

New York, United States

Kickoffs, contracts and account management for North American clients.

Shared hours with North America

Clients in Europe share the full working day with the team.

8 AM to 12 PM New York time, 2 PM to 6 PM in Warsaw.

Awards for Staffing and React

Rankings for our staff augmentation and React work, then for the in-house team our React Native engineers come from.

Related reading

Before You Add a React Native Engineer

Guides from our team on choosing React Native engineers, running staff augmentation well and how it compares with outsourcing.

All Insights

Frequently Asked Questions

Questions teams ask before a React Native engineer joins their mobile app.

Have a different question? Talk to our team

What Is in the Next Release?

Tell us about the app, the native code under it and how a build reaches the stores today.

We reply within 24 hours, and we can sign an NDA before you share details.

Talk to the people who will scope your project