Skip to content
Go To Agency
Go To Agency

Mobile App Development That Survives the App Store Review

Most mobile projects do not fail on code. They fail on the parts nobody scoped: store review rejections, push notification permissions, offline state, and the second platform that was assumed to be free. We scope those in writing before we start.

Send your brief →
Written reply within 24 business hours4.9/5 from 35 reviewsAsync by default, no calls required

The app is the easy part. Shipping it is not.

You can get an app built almost anywhere. What you cannot get cheaply is someone who has already been rejected by Apple's review team and knows why. Account deletion, tracking permission, subscription restore, and privacy labels are the four that catch most first submissions, and each one costs a review cycle to learn.

24-48h
Apple's stated target for a first review decision
iOS 15+
Minimum iOS version Apple currently accepts for new builds
Account deletion
Required in-app for any account creation (App Store rule 5.1.1)

One codebase, two stores, no surprises

React Native or native, decided on your constraints

React Native when the app is mostly screens over an API, which is most of them. Native when you need deep hardware access, background processing, or a widget. We tell you which before you commit, and why.

Store submission handled end to end

Developer accounts, provisioning, privacy labels, screenshots, review notes, and the response when review comes back with questions. We have been through the rejection loop and write the submission to avoid it.

Offline and flaky network as a requirement

Mobile users lose connection in lifts, tunnels and basements. Local persistence, optimistic updates and conflict resolution are designed in, not patched after the first angry review.

Push notifications that people keep enabled

Permission asked at the moment it makes sense rather than on first launch, deep links that open the right screen, and a backend that will not wake every user at 3am when a job retries.

Backend and API included

An app is a client. We build the Postgres schema, the API and the auth behind it, so you are not co-ordinating two suppliers who each blame the other.

Analytics you can act on

Funnel events wired from the first build, so you can see where people drop before the store reviews tell you.

How a mobile project runs with us

< 24h
Reply to your brief
100%
Scope agreed in writing before we start
4.9/5
Client rating
100%
Projects delivered remotely

Mobile app engagements

MVP

On quote
  • One platform, or both via React Native
  • Up to 8 core screens
  • Auth and user accounts
  • API and database
  • Store submission included
Send your brief →
Recommended

Full product

On quote
  • iOS and Android
  • Push notifications and deep links
  • Offline support
  • Payments or subscriptions
  • Analytics and crash reporting
  • Post-launch support window
Send your brief →

Takeover

Custom
  • Audit of an existing codebase
  • Dependency and OS version upgrade
  • Store account migration
  • Roadmap before any rewrite is proposed
Send your brief →

What actually decides a mobile budget

Mobile quotes vary wildly between agencies for the same brief, and the reason is rarely rate. It is that the same sentence hides very different amounts of work. These are the five variables that move a mobile estimate more than anything else, so you can read any quote, ours included, and see what it assumed.

One platform or two, and what cross-platform really saves

React Native shares most of the application code between iOS and Android, so the saving is real but it is not fifty percent of the project. Store submission, testing and platform-specific behaviour stay doubled, and a handful of screens usually need per-platform treatment. Budget a cross-platform second store at roughly a quarter of the first rather than nothing, and treat any quote that adds the second platform for free as a quote that has not thought about review.

Whether an API already exists

An app is a client for something. If you already have a documented API with authentication, the app is the whole project. If you do not, the backend, database schema, auth and hosting are a second project running underneath, frequently larger than the app itself. This single fact is the most common reason two quotes for the same app differ by double.

Payments, and specifically subscriptions

A one-off purchase is straightforward. Subscriptions are not: Apple and Google each take their own store commission on digital goods, both require restore-purchase flows, receipt validation has to happen server-side or it is trivially bypassed, and you need to handle the states where a subscription lapses, is refunded, or is shared through family sharing. If your model is subscription, say so in the first line of your brief, because it changes the shape of the whole build.

Offline behaviour

Deciding that the app simply requires a connection is a legitimate choice and it is much cheaper. Deciding it must work on the underground and reconcile later is also legitimate, and it means local persistence, sync, and a conflict resolution rule for every entity a user can edit. What costs money is discovering the requirement after the architecture assumed the first answer.

Who supplies the design

Finished screens in Figma with states and edge cases specified are the fastest possible input. A rough idea and a competitor's app means design is part of the project, which is fine but should be priced as such. The expensive middle ground is a partial design that stops at the happy path, because every empty state, error and loading case then gets decided during development, one interruption at a time.

React Native if the app is screens over an API, which covers most business apps, because one codebase serving both stores roughly halves the build and every future change. Native if you need sustained background work, tight hardware integration, a complex widget, or you are shipping something performance-critical like real-time video processing. The honest answer depends on your feature list, so send it and you get a recommendation with the reasoning, not a preference.

We quote per project, on request, and publish no prices. What actually moves the figure: the number of distinct screens, whether you need one platform or two, whether an API already exists or has to be built, whether payments are one-off or subscription with restore logic, and whether design is supplied or produced. Two apps described in the same sentence can differ by a factor of four once specified. Send the brief in writing and you get a figure for that scope.

Yes, including the parts that go wrong. Privacy labels and the data disclosure form, App Tracking Transparency if you use any attribution, in-app account deletion which Apple now requires whenever users can create an account, subscription restore, and the review notes that explain to a reviewer how to log in and test. If review comes back with questions we answer them.

You do, from the start. The repository is yours, the Apple and Google developer accounts are registered to your company rather than ours, and the app is published under your name. We have seen the alternative and it holds companies hostage. If you already have accounts registered to a previous supplier we help you transfer them.

Often, yes. We start with a paid audit: dependency state, how far behind the OS targets it is, test coverage, and whether the architecture will take the features you want. Sometimes the answer is that a rewrite costs less than the next three features on a codebase that fights you, and we will say so plainly rather than bill for the slow route.

Everything is written and asynchronous, which is how we work with every client including the ones an hour away. You get written updates, a preview build you can install, and answers within one business day. We do not run calls, and no project has needed one.

What else we build

Multilingual Sites Where the hreflang Is Actually CorrectWebflow or an AgencyFramer or an AgencyWeb Applications, Not Websites With Logins Bolted On

Related services

Marketing websiteWebsite redesignWeb application
See all our services
4.9/5 sur 35 avis clientsRead what our clients say

Send the brief, get a real figure

Describe the app in writing, including the five variables above if you know them. You get a scoped quote and a written reply within one business day. No call, no pitch deck.

Request a quote →
Free quote →