Most app budgets are built around one number: the development quote. Whether you are comparing local agencies or weighing offshore mobile app development, that quote usually covers design, engineering, QA and release. It rarely covers what the app needs to keep running once it is in users' hands, and those costs recur for as long as the product exists.
This guide walks through the costs we see founders and product owners miss most often, from developer accounts and store commissions to OS upgrades and customer support. We avoid quoting specific prices where they vary widely or change often. Instead, we show you where each cost comes from, what drives it up or down, and how to ask vendors the right questions before you sign.
Why the development quote is only the starting point
A vendor quote prices a defined scope of work, as it should. But a mobile app depends on two app stores, a backend, a chain of third-party services and operating systems that change every year. Each carries its own fees, and some grow with your user base.
When we help clients plan, we split the budget into three buckets: one-time build costs, fixed recurring costs (accounts, baseline hosting, tooling subscriptions) and variable recurring costs (usage-based APIs, commissions, support volume). Our guide to what drives offshore app development cost covers the first bucket in detail. This article is about the other two.
A map of the costs beyond the build
The table below lists the categories we ask every client to budget for. We have not attached dollar figures because they depend heavily on scale, region and vendor choice; use it as a checklist when you request itemized quotes.
| Cost category | What it covers | How it is usually billed | What drives it up |
|---|---|---|---|
| Developer accounts | Apple Developer Program, Google Play Console registration | Annual (Apple) or one-time (Google) | Separate accounts for multiple legal entities or enterprise distribution |
| Store commissions | Share of digital goods and subscription revenue | Percentage of qualifying sales | Selling digital content in-app, revenue above small-business thresholds |
| Backend hosting | Servers, databases, storage, CDN, backups | Monthly, usage-based | Media uploads, real-time features, poor caching |
| Third-party SDKs and APIs | Maps, payments, SMS/OTP, email, chat, AI models | Per call, per user or tiered plans | Growth past free tiers, chatty client code |
| Monitoring and analytics | Crash reporting, product analytics, logging | Tiered by events or seats | Logging too much, tracking every tap |
| Maintenance and OS upgrades | Bug fixes, SDK updates, new OS and device support | Retainer or time and materials | Large dependency tree, old architecture |
| Security testing | Penetration tests, code review, dependency scanning | Per engagement or tool subscription | Regulated data, frequent releases |
| Support and operations | User support, store review replies, incident response | Staff time or outsourced plans | Complex onboarding, payments, B2B accounts |
Developer accounts and app store commissions
To publish, you need an Apple Developer Program membership, which Apple bills annually, and a Google Play Console account, which Google has historically charged as a one-time registration fee. These are small line items, but make sure the accounts are registered to your company, not your vendor. Moving an app between accounts later is possible but slow and fiddly.
Commissions are the bigger number. Both stores take a share of revenue from digital goods and services sold inside the app, such as subscriptions, premium features and virtual items. Physical goods and real-world services (a ride, a delivered meal, a clinic appointment) generally go through your own payment processor instead, where you pay normal card processing fees.
- Apple has long applied a standard 30% commission on qualifying sales, with a reduced 15% rate for developers enrolled in the App Store Small Business Program (based on annual proceeds) and for auto-renewing subscriptions after a subscriber's first year.
- Google Play applies 15% to the first $1M of a developer's annual earnings and 30% above that, with a 15% rate on auto-renewing subscriptions.
- Both companies have changed their terms in response to regulation and court rulings, including alternative payment and external link options in some regions such as the EU and the US. Fees and eligibility for those options differ from the standard model.
Backend hosting and third-party services
Almost every app talks to a server: user accounts, content, notifications, payments. Cloud hosting is cheap at launch and grows with usage. The trap is that a design decision made during the build, such as uploading full-resolution photos or polling the server every few seconds, can multiply hosting costs at scale.
Third-party services follow the same pattern. Maps, phone verification by SMS, transactional email, video calling and AI model APIs are typically free or cheap at low volume, then priced per request or per active user. A feature that costs almost nothing during beta can become one of your largest monthly bills.
- 1
List every external service
Ask your team for a dependency inventory: each SDK and API, its pricing model, and who owns the account.
- 2
Model three volumes
Estimate monthly cost at launch, at your 12-month target and at ten times that target.
- 3
Set billing alerts
Configure budget alerts on every cloud and API account so a runaway loop or abuse shows up in hours, not at month end.
Maintenance and annual OS upgrades
Apple and Google ship major OS releases every year, and each store sets minimum target SDK or build requirements for new submissions and updates. Even an app with no new features needs periodic work to stay compliant, compatible with new devices and screen sizes, and free of deprecated APIs.
Libraries age too. Payment, analytics and authentication SDKs release breaking changes, and older versions eventually stop being supported. Budgeting for steady upkeep, whether through a retainer or a block of hours, is cheaper than an emergency rebuild when an outdated SDK blocks a release. Our ongoing maintenance and support service is structured around this annual cycle.
Security testing, analytics and user support
Security work is often cut from the initial budget and then paid for later at a higher price. If your app handles health, financial or personal data, plan for automated dependency scanning in your pipeline and an independent penetration test before launch and after major changes. Regulated industries may also need documentation and audit support.
Analytics tools are usually priced by tracked events or users. Track the events that answer real product questions; over-tracking adds cost and privacy obligations. And someone has to answer users: support tickets, review replies, refunds and account recovery all take staff time, or show up later as churn and lower ratings.
How to build a total cost of ownership budget
A practical total cost of ownership (TCO) budget covers at least the first two to three years. It does not need to be precise, but it does need every category on the table, with an owner and an assumption you can revisit.
Ask for itemized quotes
Request that vendors separate build, third-party licences, hosting setup and post-launch support so you can compare like for like.
Choose the right engagement model
Fixed-price builds suit defined scope; ongoing work often fits time and materials or a dedicated team. See how engagement models compare.
Design for running cost
Caching, image compression and sensible sync intervals lower hosting and API bills for the life of the app.
Keep ownership with you
Register stores, cloud and SDK accounts to your company so you control billing and can change vendors.
If you are scoping a custom mobile app and want a second opinion on running costs, a short architecture review before the build usually pays for itself. You can also compare how a dedicated offshore team handles build and maintenance under one monthly budget.
Frequently asked questions
How much should I budget each year for app maintenance?
There is no universal figure; it depends on complexity, integrations and release frequency. Ask your vendor to estimate a year of OS upgrades, dependency updates and bug fixing, priced separately from new features.
Do I pay app store commission on physical goods or services?
Generally no. Apple and Google commissions apply to digital goods and services consumed in the app. Physical products and real-world services usually go through your own payment processor. The rules have nuances and exceptions, so confirm against current store guidelines for your specific product.
Who should own the developer and cloud accounts?
Your company should. The vendor can be invited with appropriate roles, but billing, legal agreements and the apps themselves should sit under your organization so you keep control if the relationship ends.
Can a cheaper build lead to higher running costs?
Yes. Shortcuts such as no caching, oversized media or outdated libraries raise hosting bills and make every future OS upgrade more expensive.
This article is general guidance based on common delivery practice. It is not legal, tax or financial advice; platform rules and regulations change, so confirm current requirements with the relevant provider or adviser.