React Native
One codebase, two app stores, and a phone with no signal
Our engineers ship React Native apps beside the web dashboards that manage them: employee rewards, shift compliance and fuel site monitoring. The hard part is rarely the screen. It is the release and the moment the network drops.
What you are getting
4 things that decide this
- 01Senior engineers with React Native apps in production, each paired with a web dashboard sharing one backend.
- 02They plan for the phone being offline and for app store review before the first screen is built, because both are expensive to retrofit.
- 03You interview every engineer, run your own process, and decline anyone you are unsure about.
- 04The app code, the signing setup and the release pipeline are yours from the first commit.
What a React Native developer actually does here
Sharing one codebase across iOS and Android saves real money. It does not remove the two platforms underneath, and pretending otherwise is where projects slip.
ExtraaJe pairs a React Native app for employees with a web dashboard for HR on one Supabase backend. Shift Link does the same shape for shift workers and the agency staffing them, with a Next.js web app beside it. TankAware puts React Native in front of fuel site data coming from IoT sensors, where a site manager may be standing somewhere with poor reception.
The repeated decision in all three is what the app does when it cannot reach the server, and who the second audience is. Field staff and office staff never want the same screen.
What decides whether a mobile build goes smoothly
Offline handled as a normal state
Actions queued on the device and sent when signal returns, with a rule for conflicts. Treating no-signal as an error is how field apps get abandoned.
Releases that do not stall
Store review, staged rollout and over-the-air updates for the changes that qualify. A blocked release is a schedule problem, not a coding one.
Native code where it is needed
Camera, location, background tasks and push. Knowing which needs a native module and which does not keeps the shared codebase honest.
Lists that stay smooth
Long lists virtualised and images sized properly. Scroll stutter is the complaint users actually voice, and it maps to a small set of causes.
One backend, two front ends
Mobile and web sharing rules and permissions rather than each reimplementing them. Otherwise the two drift and only one gets fixed.
- ActionTaken on the device
- Local storeSaved before sending
- QueueWaiting for signal
- SyncSent when back online
- Conflict ruleWho wins, decided up front
The last box is the one teams skip. Two people editing the same record offline is not an edge case in field work, it is Tuesday.
Mobile apps paired with an operations dashboard
“TankAware has revolutionized how we manage petroleum sites. The real-time data and automation have exceeded expectations.”
Blake Sutherland · President, Sutherland Excavating Ltd.
How hiring works
- 01
Tell us who uses the phone
A free call about the people in the field, the network they have and what the office needs to see. If a mobile web app would serve you better, we say so.
- 02
Meet the engineers
We shortlist people who have shipped through app store review and out the other side, and you interview them yourself.
- 03
They embed
Your repository, your standups, your release calendar. One of our engineers is named on the work and stays on it.
- 04
They hand over
Signing credentials in your accounts, the release pipeline documented and store listings you control. Where a client would rather we kept shipping the releases, we do that under a service level we agree.
Stack
Mobile
Behind it
Practices
Bring us the app your field team avoids
Tell us where they use it and what happens when the signal goes. The scoping call is free, and you will leave knowing whether this needs a rebuild or a fix.
01Is React Native good enough, or do we need fully native apps?
React Native suits most business apps: forms, lists, dashboards, chat, camera and location work well and one team covers both platforms. Fully native earns its extra cost for heavy graphics, intensive background processing or deep platform integration. We tell you which side your product sits on during scoping rather than after.
02Can they build the web dashboard as well?
Yes, and this is the usual shape of the work. ExtraaJe and Shift Link each pair a mobile app for the people in the field with a web dashboard for the people managing them, on one shared backend. The same engineers moving between both is what keeps the rules consistent.
03How does the app work with no network?
Actions are saved on the device and queued, then sent when signal returns, with a written rule for what happens if two people changed the same thing. This is designed before the first screen, because adding it later usually means touching every feature.
04Who holds the Apple and Google developer accounts?
You do, in your company name, with your team on them as owners. Signing keys and store listings stay in your accounts, so nothing about updating your own app depends on us being available or agreeable.
05Can they take over an app another team built?
Yes, and they start by getting a build running and a release out through your own pipeline. Until a new team can ship a trivial change to the stores, nobody knows what condition the project is really in.
06What makes one mobile project cost more than another?
Offline behaviour and the number of audiences. A connected app for one user type is straightforward. Field staff working without signal, plus an office dashboard and an admin view, is three products sharing a backend. Scoping calls are free. Where we must assess an existing app first, a paid two-week diagnostic produces a fixed price.
