Customer-facing apps
Accounts, payments, bookings and notifications for the people who buy from you.
Mobile app development for customers and teams on the move
We build iOS and Android apps in React Native, and the API behind them, so your app, your web tools and your AI workflows all work from the same data.
Why React Native?
React Native runs one codebase as a real native app on both iOS and Android, so you build and maintain one app instead of two. It uses the same language as most modern web front ends, so your app and your web tools can share logic, types and the same team. We drop down to native code only where an app needs it, such as unusual hardware access.
- First release
- 8–14 weeks
- Discovery
- 1–2 weeks, fixed price
- Platforms
- iOS and Android
- Stack
- React Native
Apps we build
Student and member apps
Grades, fees, schedules and messages, pulled from the system your organisation already runs on.
Field and inspection apps
Offline-first apps that capture photos, forms and signatures where there’s no signal, and sync later.
Companion apps for internal platforms
The parts of your web platform people need when they’re away from a desk.
Push notifications
Notifications on every device a user signs in on, triggered by real events in your systems.
Voice and camera input
Photos, voice notes and documents captured on the phone and passed into your AI workflows.
How a mobile app gets built
Every app follows the same five steps. The API comes first, because an app is only as reliable as the backend it talks to.
Map
Who uses the app, where, and what they need to get done in under a minute.
API first
The endpoints the app needs, documented and tested before the screens.
Build
Test builds every week on your team’s phones through TestFlight and Google Play testing.
Release
App Store and Google Play submission, with crash reporting in place.
Improve
Over-the-air updates for fixes, store releases for new features.
Included in every build
- Documented APIEvery endpoint described in an OpenAPI spec and covered by automated tests.
- Push notificationsDelivered to every device a user signs in on, tied to real events in your systems.
- Store submissionWe handle App Store and Google Play review, under your own developer accounts.
- Crash reportingCrashes and slow screens reported with enough context to fix them.
- Runbook and handoverWritten for the engineer who maintains it after us.
Mobile work our engineers have shipped
Student mobile app and API
81 documented API endpoints
Mobile app development FAQ
Should we build native or React Native?
For most business apps, React Native: one codebase, one team, and performance your users won’t notice the difference in. Native makes sense for heavy graphics, complex background processing or hardware React Native doesn’t support well.
Do you build the backend too?
Yes. Most of our mobile work starts with the API: sign-in, the endpoints the app needs, push notifications and documentation. If you already have a backend, we build on it.
Can the app work offline?
Yes, if the work needs it. The app keeps what it needs on the device, queues changes and syncs when it’s back online, with clear rules for what happens when two edits conflict.
Who publishes the app to the stores?
We handle submission and review, under your Apple and Google developer accounts, so the app and its listing are yours.
How long does a mobile app take?
A first release usually takes 8–14 weeks from the end of discovery, depending on how many screens and integrations it needs.