One codebase. Both stores. No compromises anyone notices.
React Native and Expo, shipped to the App Store and Google Play. Your customers can't tell it isn't native, and you aren't paying two teams to build the same product twice.
- 4 – 6 weeks
- scope to store submission
- Fixed price
- against a written scope
- 1 codebase
- iOS and Android
Who this is for
You probably need this if…
01
Your customers are on their phones, not a desk
Drivers, field staff, patients, diners. People who will never open a laptop to do the thing you need them to do, and who bounce off a mobile browser experience.
02
You were quoted twice for the same app
Two teams, two codebases, two sets of bugs, two release cycles that drift apart. For most products that's a decision made in 2015 and never revisited.
03
It has to work without signal
A stockroom, a basement kitchen, a delivery van. If the app stops being useful when the bars disappear, staff stop using it and go back to paper.
What we build
The work, in detail.
iOS & Android from one codebase
React Native with Expo. Shared business logic, platform-specific behaviour where it genuinely matters — navigation patterns, permissions, share sheets.
Offline-first architecture
Local database, queued writes, conflict resolution on reconnect. The app keeps working with no signal and reconciles cleanly when it comes back.
Push notifications
Targeted, scheduled and event-triggered. Delivery tracking so you know what actually landed rather than what was theoretically sent.
In-app payments & subscriptions
Apple and Google in-app purchase where the stores require it, Stripe where they don't. Receipt validation and subscription state handled server-side.
Biometric & device auth
Face ID, Touch ID, secure keychain storage, and session handling that doesn't log people out every time they switch apps.
Location & device features
Background location, camera and barcode scanning, file access, Bluetooth. The hardware integrations a mobile browser simply cannot reach.
Over-the-air updates
Ship most fixes without waiting days for store review. Critical bugs get resolved the same afternoon rather than the following week.
Store submission & review
Listings, screenshots, privacy declarations, and the review process itself. We handle the rejections, which are routine and rarely about your code.
Practice areas
The disciplines behind it.
You buy this as one engagement at one price. Underneath, it draws on 4 of our practice areas, and the same people cover all of them.
Product Engineering
The core build. Web and mobile applications from scoped spec to production.
- Web applications
- iOS & Android
- API design
- Real-time features
Devices & Edge
Software for the hardware on a counter, in a stockroom or on a wall.
- POS terminal software
- Peripheral integration
- Card reader integration
- Kiosk & self-service
Design & Experience
Interfaces people can use without being trained on them.
- Product UI design
- Interaction design
- Design systems
- Prototyping
Quality & Testing
Knowing it works before a customer tells you that it does not.
- Automated test suites
- End-to-end testing
- Load & stress testing
- Accessibility testing
How it runs
Four weeks, in order.
Week 1
Scope
Screen-by-screen flow, platform decisions, store account setup, and a written specification you sign off before anything is built.
Week 2–3
Build
Core screens, data layer, offline sync and authentication. You get a TestFlight or internal-track build on Friday — on your actual device, not a simulator video.
Week 4
Build
Notifications, payments, device integrations and polish. Second build to your phone, plus the edge cases that only appear on real hardware.
Week 5–6
Ship
Store submission, review responses, staged rollout, analytics and crash reporting. Store review is the one part of the timeline nobody controls.
What you get, concretely
- Apps published to the App Store and Google Play under your accounts
- Source code in a repository you own from the first commit
- Store listings, screenshots and privacy declarations
- Crash reporting and analytics, configured and explained
- Over-the-air update pipeline so you can ship fixes fast
- Admin interface for managing content and notifications
- 30 days of post-launch fixes at no additional cost
Typical engagement
Fixed price · four to six weeks
Mobile runs longer than web because store review is outside anyone's control. One scope covers both platforms; it is not quoted per store.
Technology
What we build it with.
Defaults, not requirements. If you already run something else and have a team who knows it, we work in yours.
- App
- React Native, Expo, TypeScript, React Navigation
- Local data
- SQLite, MMKV, offline sync queues
- Backend
- NestJS, PostgreSQL, Redis, push infrastructure
- Delivery
- EAS Build, TestFlight, Play Console, Sentry
Proof
We have built this before.
Not a reference we cannot name. Systems we designed, shipped and still operate, with the decisions written down.
Questions
What people ask before signing.
- Why React Native and not fully native?
- For most products the difference is invisible to users and the cost difference is roughly half. If you're building something that genuinely needs native — heavy 3D, complex audio processing, deep platform APIs — we'll tell you, and we'll tell you before you've paid us anything.
- Who owns the App Store accounts?
- You do. We set them up under your business and work as invited collaborators. If we part ways, your apps and reviews stay exactly where they are.
- How long does store review take?
- Apple is typically one to three days, Google usually faster. First submissions attract more scrutiny. We build the buffer into the timeline and handle rejections — they're routine, and normally about metadata rather than code.
- Can it share a backend with our website?
- Yes, and it should. One API serving both means one source of truth and one place to fix things. If you already have a web app we'll build against that rather than duplicating it.
- What about updates after launch?
- Most changes ship over the air within minutes, skipping review entirely. Anything touching native modules needs a store release. We'll show your team how to do both.
- Do you do app design too?
- Yes. Interface design is included in the price — we don't quote a separate design phase and then a separate build phase for the same product.
Related reading
Written on this, by us.
Engineering · 7 min read
Offline-First Is Not a Feature, It Is a Decision You Make on Day One
Software used in a stockroom, a basement or behind a fridge will lose its connection. Retrofitting offline support is one of the most expensive changes in mobile development.
Engineering · 6 min read
Design for the Tenth Hour, Not the First Minute
Software that demos beautifully and software that is pleasant to use all day are pulling in opposite directions. If your users live in the tool, optimise for the tenth hour.
Engineering · 9 min read
Native vs Cross-Platform Mobile Development in 2025
React Native, Flutter or native iOS and Android. What each one actually costs you, and the handful of cases where the answer is not close.
What would your customers do on their phone?
Tell us what your customers are currently doing badly on a mobile browser, or not doing at all. We'll come back with a scope, a number and a store-submission date.
Phone
+1 (407) 796-2376Reply time
One business day, from an engineer
Based in
Orlando, Florida · serving the United States
What happens next
- A reply within one business day, from an engineer
- A thirty-minute call, with no qualifying call before it
- A written scope and a fixed number, if it fits