Mobile App Development
We Build Apps People Keep on Their Phone.
iOS and Android from one codebase, on the backend you already run. We design the first session so people come back, make it work without signal where it has to, and get it through store review.
Available for new projects
Who This Is For
If one of these is you, keep reading.
Retail and Direct-to-Consumer Brands
Repeat buyers and a loyalty scheme that need somewhere to send a push and take a payment.
Field Service and Logistics
Technicians and drivers in patchy coverage who need to record work offline and have it reach the office.
SaaS Companies Adding a Companion App
Notifications, camera, and approvals on the move, running on the web app's existing backend.
Membership and Service Businesses
Gyms, clinics, schools, and clubs that want bookings, check-in, and messaging in one place.
Businesses With an Orphaned App
The agency's gone, the SDK deadline has passed, and the app needs rebuilding or someone to take it over.
Why Build an App
Five reasons that hold up, and one that usually doesn't.
A Channel You Own
Push notifications go straight to the customer, with no platform fee and no algorithm deciding who sees it.
Higher Conversion Than Mobile Web
Already logged in, details saved, one tap to pay. Repeat customers buy more easily in an app.
Field Teams Without Signal
Technicians, drivers, and inspectors record their work with no connection. It reaches the office when they're back in coverage.
Device Features and First-Party Data
Camera, GPS, fingerprint login, and sensors, all tied to a known user. A website can't do that reliably.
Where Customers Buy
Most online shopping now happens on phones. If your customers buy that way, the app is the shop.
Brand Presence
The weak reason. "Our competitor has one" rarely justifies the cost of building and looking after an app. If that's the main reason, a good mobile site is usually the better spend.
What Makes Mobile Hard
Two gatekeepers, a yearly deadline, and one session to win people over.
App Store Review
Apple turned down about a quarter of submissions in 2024. Google Play makes new accounts run a closed test before they can go live.
Uninstalls
46% of Android installs are gone within 30 days, most on day one. The first session decides whether the app stays.
Native or Cross-Platform
Flutter and React Native are about as popular as each other. The right pick depends on what hardware you need and who'll look after the app.
Working Offline
Field apps break when two devices change the same record and nobody decided which version wins.
Too Many Devices
Android runs on tens of thousands of different phones. We test on the set that covers most of your users.
Annual SDK Deadlines
Every year Apple and Google require apps to be built against a recent version of their tools. Miss it and new users can't find the app, or your next update gets rejected.
Mobile in Numbers
Why the first session and store review get planned.
1.93M
App Store submissions Apple rejected in 2024, out of 7.77 million reviewed.
46%
of Android installs are gone within 30 days, most on day one.
63%
of global online shopping expected to happen on mobile by 2029.
12 × 14
testers and days of closed testing Google Play asks of new accounts.
Sources: Apple, App Store Transparency Report (2024) · AppsFlyer, App Uninstall Benchmarks Report (2025) · Statista, Mobile Commerce Worldwide · Google Play Console, Testing Requirements
Where App Builds Go Wrong
Five mistakes we've seen in other people's apps, and avoided in ours.
Sign-Up Before Value
A long registration form and a wall of permission prompts before the app shows anything useful. People leave.
Push Permission on First Launch
Since Android 13, the app has to ask before it can send notifications. Ask before you've shown anything worth having and most people say no for good.
Upload Everything on Reconnect
Records clash, and someone's work gets overwritten or disappears. The field team stops trusting the app.
Submitting Without Reading the Guidelines
Crashes, missing details, and rule-breaking business models cause most rejections. Every round trip costs days.
No Maintenance Budget
The money runs out at launch. A year later the SDK deadline passes and the app drops out of search.
How We Build It
We've shipped our own products. One codebase, one backend, and a plan for what happens after launch.
Fit Check First
If a mobile site or a progressive web app does the job for less, we say so before we scope a build.
Cross-Platform by Default
One codebase for iOS and Android. We go native only when the hardware or performance needs it.
One Backend
The app shares its data with your website, CRM, and the rest of the business. Nothing to keep in step by hand.
Onboarding People Stick With
Show something useful before asking anyone to sign up. Ask for permissions when they make sense. Build the first session to earn the second.
Works Without Internet Where It Needs To
Data lives on the phone first and syncs when there's a connection. We decide field by field which version wins when two people edit the same thing.
Store Review as a Phase
We check the guidelines, fill in the listing and privacy labels, run the closed test, and try it on real devices before we submit.
What we build with
- React Native
- Expo
- Flutter
- TypeScript
- Supabase
- Firebase
- PostgreSQL
- App Store Connect
- Google Play Console
- Figma
Built the same way: Receivables · Banyan · Egis · Lift
Why We Ship in Small Steps
A five-month build with one store submission at the end is how apps get rejected and budgets run out. We put a new build on your phone every two weeks.
A Build on Your Phone in Weeks
A TestFlight or Play internal build inside the first month. You're tapping through real screens on your own phone.
Real Users Steer the Roadmap
Beta testers are on the app before the stores are. What they do in the first session decides what gets built next. Features nobody opens never get built.
Stop at Any Point
Every two weeks you see a live demo of what shipped and make a decision: keep going, change direction, or stop. You are billed per step, so if you stop, you pay for what shipped.
Change Your Mind Cheaply
After a two-week step, a scope change costs days. After a big-bang build it costs months. The one thing we fix early is native or cross-platform.
Hardest Parts First
Offline sync, phone hardware, and anything Apple looks at closely get built and tested before anything cosmetic. If the store is going to object, you find out in week three.
No Surprises at Submission
The build we submit is the one you and your testers have been using for months, checked against the guidelines along the way. Review becomes a step in the plan.
How a Fixed-Price App Build Runs
Short loops. A build on your phone in the first weeks, then a new one every step. The code and the store accounts are yours from the start.
- Typical timeline
- 12-20 weeks
- First build on your phone
- Week 3
- Live demo
- Every 2 weeks
- 01
Discovery and Fit Check
Week 1A fixed-fee week. What you want it to do, who'll use it, what systems it needs to talk to, and whether an app is the right answer at all. You keep the scope document whether or not you go ahead.
- Fit verdict
- Scope document
- Fixed price for the build
- 02
Scope and Platform
Week 1-2Native or cross-platform, what we can reuse from your backend, how much has to work offline, and the smallest version worth releasing.
- Platform decision
- Offline model
- 03
Design and Prototype
Week 2-3The sign-up and permission screens designed to keep people, and tried on real users before we build.
- Clickable prototype
- Tested first session
- 04
Build in Increments
Week 3-14Shared backend, automated tests on every change, and a set of test devices from the first step. A new build on your phone every two weeks.
- New build every 2 weeks
- Live demo every 2 weeks
- 05
Beta and Store Preparation
Week 14-18TestFlight, Play closed testing, a guideline check, the store listing, and privacy labels.
- Beta with real testers
- Store listings
- Guideline check
- 06
Launch
Week 18-20Live in both stores. Usage, crashes, retention, and uninstalls tracked from day one.
- Live on iOS and Android
- Retention dashboard
- 07
Maintain
OngoingYearly SDK targets, testing on each new OS release, and new features on whatever schedule suits you. On a monthly retainer, or handed over to your own team.
What It Costs
Fixed fee
Ends with a scope document and a fixed price for the build. Yours whether or not you go ahead.
- Scope document
- Fixed price
$40k - $150k
Offline sync, phone hardware, and how much backend already exists move the number most. A companion app on an existing backend sits at the low end; a field app that has to work without signal sits at the high end.
- Billed
- Per 2-week step
- Stop
- At any point
- Price moves
- Only if scope does
When You Don't Need an App
Three cases where a website is the better spend.
Infrequent Use
If customers deal with you a few times a year, they won't keep the app. A fast mobile site wins.
Search-Driven Traffic
Apps don't show up in Google. If that's how new customers find you, the website is the product.
No Device Features, Tight Budget
A progressive web app gives you an icon on the home screen and basic offline use without store review. iOS still limits push and background sync.
Common Questions
If yours isn’t here, book a call and ask.
Find Out If an App Is the Right Call.
Tell us who'd use it and what they'd do in it, on the call. If it's a fit, a one-week discovery follows, and at the end of it you know whether an app is the answer, what the first version looks like, and a fixed price to build it.