Build — Mobile
Apps people keep on the first screen.
Native and cross-platform applications, from store listing to the update six months after launch.
The problem
Most mobile projects are scoped as a smaller version of the website and then discover that mobile is not a smaller anything. Push notifications need a reason to exist or they get switched off in week one. Offline behaviour was never specified, so the app is a browser that fails worse. And nobody costed the part that never ends — store review, OS releases twice a year, and the device that is three years old and still in your users' hands.
What you get
- Native iOS and Android, or a single cross-platform codebase where that genuinely fits
- Offline-first data handling with conflict resolution you can explain to a user
- Push notifications tied to something a person actually wants to know
- Authentication including biometric unlock and session handling that survives a cold start
- App Store and Play Console setup, listing assets, and the first submission
- Release pipeline, crash reporting and a documented update path
How it works
We start by deciding whether you need an app at all. A responsive site installed to the home screen covers a surprising share of briefs, costs a fraction, and skips store review entirely — and we will say so when it applies rather than take the larger project. Where an app is right, we scope around the things that only exist on mobile: what happens with no signal, what a notification is allowed to interrupt, and what the app does on a five-year-old device. Then we build in fortnightly builds you can install and use, not screenshots. Handover includes the signing keys, the pipeline and the store accounts in your name.
Technical detail
Native or cross-platform
React Native or Flutter where the app is primarily screens over an API and the team is small. Native Swift or Kotlin where it leans on the camera, background processing, or platform features that a bridge makes fragile. We make that call in discovery with the reasoning written down, because reversing it later is a rewrite rather than a refactor.
Offline and sync
Local-first storage with an explicit conflict strategy, chosen per data type rather than globally. Last-write-wins is fine for a preference and unacceptable for an order. The rule is that a user should never lose work they watched the app accept.
Release and store
CI producing signed builds on every merge, TestFlight and internal testing tracks from the first week rather than the last. Store accounts, signing certificates and provisioning stay in your name from day one — an app you cannot ship without us is not an app you own.
What's not included
- Games and real-time 3D. Different engine, different discipline, and we would be learning on your budget.
- App Store Optimisation and paid user acquisition. We ship the app and set up the listing; growth marketing is a specialism and not ours.
- Ongoing OS-release maintenance as an open-ended retainer. We will document the update path and quote a defined maintenance scope; we do not sit on standby indefinitely.
Where we hand off, we tell you before the invoice arrives — not after.
Related services
You dream it. We create it.
Discovery call, project brief, or just a question. Get in touch.
Get in touch