Mobile App Development, From Store Listing to Release Six
iOS and Android from one codebase, through store review, and maintained past launch.
We have shipped consumer apps that work offline, hold nothing on a server they do not need, and pass review without a fight. That last part is a skill: most first-time rejections are avoidable, and each round trip costs a week.
How we decide what to build on
- React Native by default. One codebase for both stores, native modules where a feature genuinely needs them, and a team that can maintain it without two separate hires.
- Fully native when the app lives or dies on something platform-specific: heavy graphics, deep background work, a hardware integration that has no bridge.
- A web app when nothing requires a store at all, which is more often than the brief usually admits. We will tell you when a progressive web app is the honest answer.
What we build in
- Local-first data, so the app works on a train and syncs later rather than showing a spinner over a dead network.
- An account wall only if the product needs one. Every registration screen between a person and value costs you most of them.
- Store listing work: screenshots, description, keywords, privacy answers. The listing is the conversion step everyone forgets after twelve weeks of building.
- Release plumbing from the start: signing, over-the-air updates for what is allowed, crash reporting that names the line rather than the screen.
What it costs
- 8-14 weeks to a first version in both stores
- 2 store review cycles to budget for, realistically
- 15-20% of build cost per year to stay compatible
The expensive part of an app is not shipping it. It is still being installed a year later.
Frequently asked questions
Do we need both iOS and Android at launch?
Only if your audience is genuinely split. Shipping one store first halves the surface area of the first release and gets real feedback weeks earlier, and with a shared codebase the second store is a fraction of the work rather than a second project. Look at where your existing customers already are before deciding.
Who owns the developer accounts?
You do, always, in your company name. An app published under an agency account is an app you cannot move, update or transfer without that agency's cooperation. We are invited to your accounts, not the reverse, and that is written into the contract.
What about app store rejections?
We design around the rules that cause most of them: account deletion, subscription disclosure, permission justifications, and anything that looks like a web page in a shell. Rejections still happen; the difference is whether they take a day to answer or force a redesign.