What it is
React Native is a framework from Meta for building iOS and Android apps with React and JavaScript. Unlike a web page wrapped in an app shell, it renders real native components, so the app looks and behaves like it belongs on the phone. It can reach the camera, storage, location and notifications through native modules.
Most of the code is shared between the two platforms, with platform-specific pieces only where needed. Tooling such as Expo handles builds, over-the-air updates and store submissions. For a team that already writes React for the web, it means the field app is not a second, unfamiliar codebase but the same way of working.
How I use it
- Built the Rental Pilot field app for iOS and Android, shipped to the App Store.
- Drivers and crews use it for delivery, pickup and service, with photos, signatures, timesheets, clock-in, fuel logging, chat and push notifications.
- It works offline and syncs when back in range.
- Kept at feature parity with the React web app, and every screen is checked on a real device before it ships.
React Native fits when a field crew needs a real app: the camera, signatures, push notifications and working offline where the signal does not reach. I reach for it because it lets one developer keep a phone app at real feature parity with a React web app, rather than an app that mostly works.
Questions
Can you build a field app that works without signal?
Yes. The Rental Pilot field app works offline and syncs when the phone is back in range, so crews can log deliveries, photos and fuel on remote sites.
Will the phone app match our web app?
That is the standard I hold. Rental Pilot's field app is kept at feature parity with the web app, and changes are checked on real devices before release.
Do you publish to the App Store?
Yes. The Rental Pilot field app is on the App Store, and earlier Cordova apps went to both Google Play and the App Store.