What an App Really Costs: Development Plus the Annual Bill After Launch
When a company asks what it costs to build an app, the answer it usually receives is a development quote: 300,000 yuan, 500,000, or more. That number answers only "what does it cost to build the software". It says nothing about what the app costs every year once it is live. In practice, for an app that stays in operation, cumulative spending in years two through five often matches or exceeds the entire first-year build investment.
At Juhui Software we have built custom software for a decade, and we have seen projects start with a comfortable first-year budget and then stall in year two under maintenance bills and iteration demands nobody planned for. Laid out properly, all of this is plannable before the project starts.
1. Development is the first payment, not the whole bill
App spending falls into two categories with entirely different natures. The first is one-off: requirements, UI design, frontend and backend development, testing, store submission. Once paid, it is finished. The second is recurring: as long as the app serves users, it generates cost every month, and only shutting the service down stops it.
Budgeting only the first category is the most common planning error. The test is simple: ask what you will still be paying for one year after launch. Whatever you can list belongs in the budget.
2. Servers and infrastructure: hundreds a month to tens of thousands
This range is enormous and depends on user volume and data shape. An app with a few thousand daily actives and mostly text and images runs on one mid-range cloud server plus object storage, typically a few hundred to two thousand yuan a month. Ten thousand daily actives with real-time messaging or audio and video needs load balancing, multiple application servers, Redis and a message queue, commonly five thousand to thirty thousand a month. Device connectivity or live location data adds time-series storage and bandwidth on top.
Bandwidth is routinely forgotten. The moment images and video move to a CDN, traffic cost climbs with usage. Estimate it from traffic per active user per month rather than picking a round total.
3. Third-party services: small unit prices, many line items
A normally operating app usually carries five or six third-party services at once: SMS verification, push notifications, maps and geolocation, payment channels, object storage, content moderation, crash monitoring. Individual monthly fees run from tens to thousands of yuan; one thousand to five thousand a month in total is typical.
Watch the percentage-based items. Payment channels charge a fraction of a percent of transaction volume, so that cost grows with the business. It must be modeled separately from fixed monthly fees, never blended into a single number.
4. Maintenance and iteration: the most underestimated line
Launch is not the finish line. Mobile operating systems ship new versions annually, app store review rules change, third-party SDKs reach end of life, payment interfaces get upgraded. These external changes force code changes whether or not you want new features.
The common industry benchmark is that annual maintenance runs about 15 to 20 percent of the original development cost. That covers defect fixes, dependency upgrades, adaptation to new OS versions and minor enhancements. Below that range, either nobody is really maintaining the app, or every change is billed as a separate project.
If the business itself changes quickly, add an iteration budget. A practical structure is quarterly batches priced by person-day rather than a contract promising unlimited changes for a year — the latter usually leaves both sides unhappy.
5. Compliance and licensing: industry-dependent, not optional
This is the line most often missing from the budget and the one that stings when triggered. Apps handling real-name identity, payments or location data need ICP filing, public security filing and personal information protection assessments. Some industries also require graded protection evaluation, costing anywhere from tens of thousands to over a hundred thousand yuan depending on the system's classification. App stores impose hard requirements on privacy policies and permission declarations; non-compliant submissions are rejected outright.
Paying earlier is cheaper. A post-launch regulatory notice costs the assessment fee plus lost business during any suspension.
6. Calculate the five-year total
Here is an algorithm you can apply directly. One-off investment equals development plus design plus first-time submission and compliance. Annual operation equals servers and bandwidth, plus third-party services, plus maintenance at 15 to 20 percent of development cost, plus iteration budget, plus annual compliance review. Add both, multiply by five, and you have the five-year total.
Seen this way, the answer to "what does an app cost" typically lands 60 to 100 percent above the initial quote. That is not padding — it is making visible what would otherwise be scattered across years. For a decision-maker, the five-year total is more useful than a first-year quote, because it maps directly to whether the project is worth doing at all.
7. What you can trim, and what you should not
Trimmable: size servers to actual concurrency instead of buying headroom up front; consolidate third-party services where one ecosystem can cover several needs; move non-core features to phase two and fund them from the iteration budget.
Not advisable to trim: testing, security and compliance, and the maintenance budget. All three share one property — money saved here does not vanish, it returns later at a higher unit price. A project that loses data or fails store review three months after launch usually pays more to fix it than it ever saved.
So the accurate answer to what an app costs has two parts: a one-off build investment, and an annual operating cost. Add them together and you have a number you can actually decide on, rather than a first-year quote that only feels comfortable.