App Development

A mobile app is a harder commitment than a website, and it is worth being honest about why. You are shipping into an environment you do not control, through a review process you cannot rush, onto devices that go offline, with users who will not reinstall if the first run disappoints. Most of the engineering effort goes into those realities rather than into features.

What we build

• Cross-platform apps in React Native or Flutter — one codebase, both stores.
• Native iOS and Android in Swift or Kotlin where performance or platform integration requires it.
• Offline-first data with sync and conflict resolution that matches how the app is actually used.
• Push notifications that are useful rather than merely possible.
• In-app payments and subscriptions, including store billing rules.
• Store submission — listings, review responses, phased release.
• Analytics and crash reporting, so the next release is informed by evidence.

Cross-platform or native?

Frequently asked questions

How long does it take to build an app?

A focused first version is typically ten to sixteen weeks including store submission. Complex apps with offline sync, payments and multiple roles run longer. Store review adds days rather than weeks, but it is a dependency rather than something you can compress.

Do we really need an app, or would a mobile site do?

A responsive website covers more cases than most people expect. An app earns its cost when you need offline capability, push notifications, device hardware, or the repeat usage that makes a home-screen icon valuable. If none of those apply, we will say so.

Who handles App Store and Play Store submission?

We do, under your developer accounts so the listings remain yours. That includes listing assets, review questions and phased rollout.

What does maintenance involve after launch?

Both platforms ship major releases annually, alongside store policy changes and dependency updates. An app that goes untouched for a year usually accumulates problems, so budget for ongoing releases rather than treating launch as the finish line.

How the engagement runs

• Scoping call, then discovery. We establish what you actually need before quoting. You approve scope before we write a line of code.
• Fixed price or capped time and materials. Tightly specified work suits a fixed price; genuinely new work suits a capped retainer. We recommend one rather than offering both and letting you guess.
• Weekly demos. You see working software every week, so nothing surprising turns up at the end.
• You own everything. Repositories, infrastructure and documentation transfer to you on payment. No vendor lock-in, no licensing you do not control.
• NDA as standard, usually before the first detailed call. We will often send one ourselves if you do not.

If you are planning a mobile app and want a straight assessment of scope, timeline and cost, tell us what you are building. We work with clients across the UK, EU and US.