RangeX scores a target in 20 seconds.Read more

Cost & planning

Mobile App Development Agency: What You Pay For and What to Check

A mobile app development agency should own the parts a web shop never touches: store accounts, App Store review, TestFlight, device testing, push certificates and release management. Here is what that work costs and how to check an agency has done it before.

Nate Laquis12 min read

What a Mobile App Development Agency Should Do for You

A good mobile app development agency designs and builds your iOS and Android app, and it also handles the work that only exists on phones: setting up the App Store and Google Play accounts in your company's name, getting the build through App Store review, running TestFlight and Play testing tracks, testing on real devices, wiring push notifications and in-app purchases, and shipping updates after launch. In the US, a cross-platform first version from a capable agency usually costs somewhere between $50,000 and $250,000 and takes two to five months. The cheapest way to tell a mobile agency from a web shop that also does apps is to ask which apps they shipped under the client's own developer account, and then download them.

This post covers that mobile-only work, what market prices look like and why, the four kinds of agencies you will meet, the checks that only make sense for mobile, and the contract points that protect your store listing. It also covers when hiring an agency is the wrong move, because for some founders it is.

If you want the general agency vetting process (references, team structure, red flags on sales calls), read how to vet a software development agency first. I am not going to repeat it here. Everything below is about phones. Apple and Google fees and rules were checked against their own developer pages on November 22, 2026.

The Work a Web Shop Never Has to Do

A web agency deploys whenever it wants. A mobile agency ships through two gatekeepers, onto thousands of device and OS combinations, to users who may not update for months. That difference shows up in eight places.

Store accounts, and whose name is on them

The Apple Developer Program costs $99 a year. A Google Play developer account is a one-time $25. Both should be enrolled by your company, not by the agency and not by a developer's personal Apple ID. An organization enrollment with Apple needs a D-U-N-S number for your legal entity, which can take days to issue, so start it in week one. The agency gets added to your account with a Developer or App Manager role. It never holds the Account Holder seat.

On Google Play, a new personal account has to run a closed test with at least 12 testers opted in for 14 straight days before it can publish to production. An organization account skips that rule. A mobile agency knows this and tells you to register as an organization before it costs you two weeks.

App Store review and rejections

Apple says it reviews at least 50% of submissions in under 24 hours and 90% in under 48. The time is rarely the problem. Rejections are. The ones I see most on first submissions:

  • Guideline 2.1, app completeness. No demo account for the reviewer, a backend that was asleep, placeholder text left in a screen.
  • Guideline 4.2, minimum functionality. An app that is a wrapped website with nothing a phone adds.
  • Guideline 5.1.1(v). If your app lets people create an account, it has to let them delete it inside the app.
  • Guideline 4.8. If Google or Facebook sign-in is the main way in, you also need an equivalent option that limits data to name and email and lets people hide their email. In practice that means Sign in with Apple.

An experienced team clears these before submission. Ask how many rejections their last three apps had and what each one was for. A team that says "never" is either new or not counting.

TestFlight and internal testing tracks

You should be holding the app on your own phone every week from about week three. On iOS that is TestFlight, which takes up to 100 internal testers from your team and up to 10,000 external testers once a build passes beta review. On Android it is the internal, closed and open testing tracks in Play Console. Weekly builds you can tap through tell you more than any status report.

Device and OS-version testing

Your app has to work on a three-year-old Android phone with a small screen and on the newest iPhone with the Dynamic Island. Ask which minimum iOS and Android versions they plan to support, which physical devices they own, and whether they use a device cloud like BrowserStack or Firebase Test Lab for the rest. Google also sets a floor: from August 31, 2026, new apps and updates on Google Play must target Android 16 (API level 36). An agency should know that date without looking it up.

Push notifications and certificates

Push on iOS runs through APNs and needs a key from your Apple account. On Android it runs through Firebase Cloud Messaging. Signing certificates and provisioning profiles expire, and an expired one at release time stalls your launch. The keys and certificates belong in your accounts, with the agency granted access.

An iPhone on a stand next to an iMac and an Apple keyboard on a desk, the setup used to test a mobile build

In-app purchases and Apple's commission

Guideline 3.1.1 says digital features and content sold inside the app, subscriptions included, go through Apple's in-app purchase. The standard commission is 30%. Auto-renewing subscriptions drop to 15% after a subscriber's first paid year. The App Store Small Business Program charges 15% from the start if your proceeds were under $1 million the prior calendar year, but you have to enroll, and plenty of founders never do. On the US storefront, apps can now include buttons and links to buy on the web, which changes the math for subscription products. Your agency should walk you through all of this before you design the paywall, and most teams wire it with RevenueCat or StoreKit 2 and Google Play Billing directly.

Native modules

Cross-platform frameworks cover most of an app. The rest is native: a camera feature, Bluetooth, background location, Apple Health, a widget, a payment SDK with no React Native or Flutter wrapper. Ask who on the team writes Swift and Kotlin when the framework runs out. If the answer is "we have never needed to", the first native problem will cost you weeks.

Release management and over-the-air updates

Each store release needs version numbers, release notes, screenshots and often a phased rollout. React Native teams can also push JavaScript fixes over the air with Expo's EAS Update, which skips store review for small fixes. Apple allows that for interpreted code as long as the update does not change what the app is for. A mobile agency has a written release process and a rule for what goes over the air and what goes through review.

What Agency Mobile Builds Cost in 2026

Here is what I see in US market quotes for agency-built apps this year. These are estimates from proposals founders have shown me and from public rate data, not a price list.

  • A focused first version, one codebase for iOS and Android: $50,000 to $120,000. Accounts, a core loop of five to fifteen screens, push, basic analytics, a simple admin panel. Eight to fourteen weeks.
  • A full product with payments and real-time features: $120,000 to $250,000. Subscriptions or a marketplace, chat or video, an admin dashboard, integrations. Three to five months.
  • Two native codebases, regulated data, or hardware: $250,000 and up. Swift and Kotlin teams, HIPAA work, Bluetooth devices, offline sync at scale.

Hourly rates explain most of the spread. Onshore US agencies tend to bill $150 to $250 an hour, nearshore teams in Latin America $50 to $100, and offshore volume shops $25 to $60. A lower rate is often worth it. It can also mean more hours, more rework and a second build, so compare total quotes for the same scope, not rates.

What moves a quote up, in rough order of impact:

  1. Native versus cross-platform. Two native apps cost roughly 1.5 to 2 times one React Native or Flutter app for the same features.
  2. Real-time and media. Video calls, live chat, uploads and feeds add backend work and testing.
  3. Payments. In-app subscriptions are moderate work. A two-sided marketplace with payouts through Stripe Connect is a lot more.
  4. The admin side. Founders forget the dashboard they need to run the business. It can be 20% of the build.
  5. Design depth. Custom motion and a full design system cost more than a clean, standard interface.

Then budget for the store and running costs: the $99 Apple fee every year, the $25 Google fee once, hosting, a crash tool, an analytics tool, and a monthly retainer for updates after launch. For a full breakdown by feature, our guide to how much it costs to build a mobile app goes line by line, and the app development cost calculator gives you a range for your own feature list in a couple of minutes.

Four Kinds of Mobile Agencies

Most of what you will find falls into one of four shapes. None of them is wrong. They fit different founders.

Offshore volume shopLocal agencyFreelancer collectiveProduct team
Typical rate$25 to $60 an hour$120 to $250 an hour$60 to $150 an hourUsually a fixed price for an agreed scope
Who you talk toAn account managerA project managerThe developers, often one leadThe people designing and building it
Good atA tight, fully written specIn-person workshops, local clientsSmall, well-defined buildsDeciding what to build, then shipping it
Watch forRotating developers, slow store fixesWeb work first, mobile secondNobody owns release or QAHigher upfront cost
Store workVaries a lotOften thinDepends on one personUsually part of the plan
Best forVersion two of a proven app with a clear specAn established business that wants to meet in personA budget under $50,000 and a narrow scopeA founder with an idea and a deadline

The local agency row is the one that surprises founders. Plenty of agencies with "mobile" on the homepage are web shops that wrap a site in a native shell when a client asks. The checks in the next section catch that in one call.

Freelancer collectives can be excellent, and the risk is concentration. If one person holds the signing keys, the store access and the knowledge of how the build works, you depend on that person's calendar.

The Checks That Only Apply to Mobile

Run these on every agency you are serious about. They take an hour in total and they sort agencies faster than any portfolio page.

Download their apps from the store

Ask for three apps they shipped that are live now. Install them. Then scroll to the bottom of each App Store listing and read the seller name. You want to see the client's company there, not the agency's. An agency that publishes client apps under its own account is either careless about ownership or keeping a hold on you. On Google Play, the developer name sits under the app title.

Use each app for ten minutes. Turn on airplane mode. Deny a permission and see if it recovers. Check the version history for how often they ship.

Ask for their crash-free rate

Every serious team watches crash-free users in Firebase Crashlytics or Sentry. Ask what rate they hold on their live apps and ask them to share a screen. My own bar is above 99.5% of users crash-free on a stable release. A team that does not know the number does not watch it.

Ask who submits the build

Someone has to fill in App Store Connect, write the review notes, set up the demo account, answer Apple's messages and handle a rejection on a Friday night. Ask for that person's name. If it is "you do that part", you have just learned the quote leaves out the hardest week of the project.

A hand holding a black Android smartphone, the kind of real device an agency should test a build on

Ask how you will test it

The answer you want is "a TestFlight and Play internal build every week, starting in week two or three." Ask to see a past client's TestFlight cadence. A build on your own phone beats a demo on a shared screen.

Ask what happens when the framework runs out

Give them one native feature your app needs, say background location or a home screen widget, and ask how they would build it. You will hear in two minutes whether they have done native work or plan to learn it on your budget.

Contract Points for a Mobile Build

These are the clauses that matter more for an app than for a website.

  • Developer accounts in your name. The contract says your company enrolls in the Apple Developer Program and Google Play Console and holds the Account Holder or owner role. The agency gets a lower role and loses it at the end of the engagement.
  • Signing keys and certificates. The Android upload key, Apple distribution certificates and the APNs key are created in or handed to your accounts. Losing an Android signing key used to mean you could never update the app again. Play App Signing fixed most of that, but you still want the keys.
  • Code ownership. Full assignment of the code, the designs and the backend to you, with a repository in your GitHub organization from day one. Our agency contract checklist on who owns your app code goes clause by clause.
  • Third-party accounts. Firebase, RevenueCat, Expo, Sentry, your backend host and your domain all sit under your company's billing.
  • Store submission and rejections in scope. The statement of work names who submits each build and says rejections caused by the agency's work are fixed at no extra charge.
  • A warranty window after launch. Thirty to ninety days of bug fixes on the launched version is normal.

If an agency already holds an app of yours under its account, Apple supports transferring it between developer accounts with its reviews and ratings intact. Ask for it in writing now. It gets harder once the relationship has gone bad.

The First Month After Launch

A mobile agency that disappears on launch day leaves you alone for the hardest four weeks. Here is what that month should hold:

  • Daily crash checks for the first two weeks. Real users on real phones find crashes no test caught. Fixes ship over the air when they can and through review when they cannot.
  • A phased rollout. Apple's phased release spreads an update over seven days. Play's staged rollouts let you start at a small percentage. Use both for the first few updates.
  • Review replies. Someone reads every App Store and Play review in week one and answers the ones with a real bug in them.
  • A look at the numbers. Signup completion, the first core action, day-one and day-seven retention. That tells you what goes into version 1.1.
  • An OS release plan. If you launch in late summer, a new iOS version lands within weeks. Someone has to test against the beta before it ships to everyone.

Ask every agency what the first month looks like and what it costs. A retainer for updates and monitoring is normal. A blank stare is a signal.

When an Agency Is the Wrong Call

I run a company that builds apps for founders, and I still tell some founders not to hire one. Two cases come up most.

A simple app a no-code builder can handle

If your first version is a directory, a booking form, an internal tool for your own staff or a content app with a login, try a builder first. Adalo, FlutterFlow and Glide can publish to the stores. Bubble's native mobile builder can too. You can test demand for a few hundred dollars a month and learn what users want before you spend $80,000. The ceiling is real: performance, offline use, native features and complex logic all hit it. Many founders still get months of learning out of it before they need a real build.

A founder who should hire a first engineer

If the app is the company and you plan to change it every week for years, you need someone in-house who owns it. That is true if you already have product-market fit and need a team to grow it. It is also true if your edge is technical, like a novel model or a hardware integration, and the knowledge has to stay inside. An agency can build version one and hand it over, and that can be the right sequence. But if you have the funding and a strong candidate now, hire them.

One smaller case: a budget under about $30,000 for a full two-sided marketplace. Scope it down to one side first, or wait.

A man writing code on a laptop at a desk, the kind of first in-house engineer some founders should hire instead of an agency

What This Looks Like on a Real Build

Vybes is a members-only, video-first dating app where first dates happen face to face on a VybeCheck video call. We built it in React Native for iOS and Android, with real-time WebRTC video, ID verification and date scheduling with push notifications. It went from concept to the App Store in eight weeks, holds a 4.8 rating, and the company is now valued at $10M. The full Vybes case study covers the stack and the screens.

That build had the mobile-only work in it: push notifications for date scheduling, real-time video calls that had to work on both iOS and Android, and an App Store launch on a deadline. It is the part of an app most founders never see, and it decides whether launch week goes well.

We design and build iOS and Android apps for founders, from the first scoping call to the App Store. If you are comparing agencies for your app and want a straight answer on scope, timeline and which kind of team fits, Book a free strategy call.

mobile app development agencyApp Store reviewApple developer account ownershipmobile app development costhiring an app agency

Get your number.

Thirty minutes. You leave with a plan and a number.

Book a free call