How much does it cost to build an app: how to read an estimate
Ask any studio what an app costs and you get a range. The range is useless: it describes the spread of that studio's projects, not yours. What helps is knowing how an estimate is assembled — then you can check someone else's number and see where it is padded and where it is naive.
Why nobody names an exact figure up front
An app is not a product with a price tag, it is a set of decisions, and before requirements are discussed those decisions do not exist yet. Two apps described as "a services marketplace" can differ threefold in effort: in one, providers are added by hand through an admin panel; in the other they sign up themselves, with document checks, ratings, disputes and payouts.
The honest sequence is: a short requirements conversation, then an estimate as a range, then a fixed scope for one stage. A studio that quotes an exact figure off a three-sentence email has either padded it heavily or will come back for more.
What an estimate is made of
Building screens is usually the smaller part. These line items appear in almost every project:
- Discovery and requirements: feature list, user flows, constraints, risks.
- Design: screens, states (loading, errors, empty lists), layouts for different devices.
- Client side: the app itself for iOS and Android.
- Server side: database, API, authentication, roles, admin panel.
- Integrations: payments, maps, push, third-party services, analytics.
- Testing: on real devices, not only in a simulator.
- Publishing: developer accounts, builds, store assets, getting through review.
- Support after launch: OS updates, fixes, monitoring.
If testing, publishing and support are missing from an estimate, they have not disappeared — they will be billed later, on top.
Five decisions that move the price most
Platforms. Two native builds cost more than one cross-platform build, but rarely twice as much: design, backend and analytics are shared. The difference is in the client code.
User data. Sign-up, profiles, permissions, password recovery, account deletion — backend work you cannot see on a mockup, and it is always there.
Real time. Chat, live status, live quotes, collaborative editing all need their own architecture. On our Kursly project, real-time rates from several sources turned out to be the largest piece of work, even though on the mockup it is just a table of numbers.
Offline. An app that must work without a connection and sync later is a separate layer of logic and a separate class of bugs.
Third-party integrations. Each external service means documentation of varying quality, rate limits, a sandbox, and the risk that it changes. Count them one by one, not as a single line called "integrations".
What an iPhone-only app costs
One platform is cheaper, but not half the price. The backend, design and testing barely change — you only save on client development for the second platform.
Budget for publishing separately: the Apple Developer Program costs $99 a year and must be renewed, or the app disappears from the App Store. Google Play charges a one-time $25 fee.
If the budget covers only one platform, pick it by audience rather than preference: check which devices your website visitors already use.
What to ask before you trust a number
These questions quickly show how carefully an estimate was made:
- What exactly is included, and what is not?
- Is this the whole product or the first stage?
- Which features in this estimate are the riskiest, and why?
- What happens to the price if we add a feature mid-project?
- Who owns the developer accounts and the source code?
- What does a month of support cost after launch?
Where to save and where not to
Saving on scope is sensible: cut the first version to one flow, postpone the second platform, use a ready design system instead of custom graphics, replace a complex admin panel with handling requests manually at the start.
Do not save on testing on real devices, on backend architecture, or on analytics. The first shows up as store reviews, the second as a rewrite six months later, the third means you will never know which feature anyone actually uses.
Questions people ask
How much does it cost to build a simple app?
It depends on what "simple" covers. An app with one flow and no backend logic costs noticeably less than a platform with user accounts, payments and integrations. A meaningful figure needs a feature list — from a one-line description any estimate is a guess.
Is cross-platform cheaper than native?
Usually yes, because the client code is written once for both platforms. The saving applies to the client side only — backend, design and testing stay roughly the same.
How much does app support cost after launch?
Support is normally billed monthly and covers updates for new iOS and Android versions, bug fixes and monitoring. Without it, an app starts breaking on new devices within a year or so.
Can an app be built for a fixed price?
Yes, if the scope is fixed before work starts — that is, after discovery and mockups. A fixed price based on a verbal description means either a large buffer in the estimate or arguments about scope mid-project.
