Mobile Apps
One codebase for iOS and Android, going native where it actually makes a difference.
- React Native
- Expo
- iOS + Android
How it works
We build with React Native and Expo. One codebase, both platforms, and native code where it is needed.
Why one codebase
By far the largest part of an app is the same work on both systems: screens, state, storage, connectivity. Building that twice costs roughly double and buys nothing. What does differ — permissions, camera, background behaviour — gets its own path.
Where we go native
When a requirement reaches deep into the operating system, we write that piece natively and bind it in. Bluetooth devices, background location, platform payment flows. That is the exception rather than the rule, but it has to be possible.
Offline
Mobile devices are regularly without a network: in a lift, in a warehouse, on a train. We decide early what has to work without a connection and how to merge when two devices have changed the same data.
You see something every week
From the first sprint you get builds on your own device, via TestFlight and internal distribution on Google. Not as a video, but as an app you can use.
- Developer accounts with Apple and Google, in your name. We set them up, but they belong to you.
- Devices for testing where hardware is involved — scanners, wearables, vehicles.
- Someone on your side who tries a build every week.
An app for both platforms, in your store accounts, with the source code in your possession.
If you skip this
Two separate native apps mean double the development and two builds that drift apart. That pays off when you genuinely push the limits of each platform — and rarely otherwise.
Questions about this step?
A conversation costs nothing and takes half an hour. Afterwards you will know whether we are a fit.