Mobile app development for the phones people actually own.

We put the scope in writing before work begins and bill against it, with a written change order if it grows. Scope drives it: how many screens, whether it needs offline sync, whether payments are involved, and whether it integrates with systems you already run. A focused single-purpose app is the smallest engagement we take; a customer app with accounts, payments and push notifications sits several times higher. Both stores are covered by the same build, because one codebase produces both.

Cross-platform, for most businesses. React Native serves both stores from one codebase, which roughly halves the build cost and the ongoing maintenance, and for the apps most companies need the performance difference is not perceptible to users. Go native when the app is hardware-heavy: continuous background location, heavy real-time graphics, or intensive camera and video processing. We will tell you which category yours falls into during scoping rather than defaulting to whichever is more profitable.

Eight to sixteen weeks from signed scope to a live store listing. The build itself is usually ten of those weeks; the remainder is discovery, design, device testing and store review. App Store review is the unpredictable part: typically a few days, occasionally longer if a reviewer queries a permission or a privacy declaration. We prepare the submission paperwork during the build rather than at the end, which removes most of that risk.

Yes, both, including listing copy, screenshots, privacy policy declarations and the data-safety forms each store now requires. First submissions are frequently rejected over a permission that is not justified in the listing or a privacy form that does not match the app’s behaviour. We handle those exchanges. You keep ownership of the developer accounts throughout, because they are registered to you, not to us.

Apps need maintenance in a way websites do not. Each major OS release can deprecate an API, change a permission model, or alter how notifications behave, and the stores enforce minimum SDK versions on a schedule. Budget for a maintenance retainer or at least an annual update. An app left untouched for two years will eventually stop being installable, and that cost is better known before you start than after.

Usually, if it is React Native or Flutter and the codebase is in reasonable shape. We begin with a short paid audit covering the code, the build pipeline, the store accounts and the dependency versions, then report on what it will take to move forward. The most common finding is abandoned dependencies rather than bad code: libraries two or three major versions behind, where the upgrade is most of the work.