“How much will our app cost?” is the first question most people ask, and the honest answer is that it depends on decisions you have not made yet. This guide explains those decisions, so you can see which ones move the number and make them deliberately. It does not quote prices: a figure without your scope behind it would not help you.
Scope: features, screens and user roles
Scope is the largest driver by far. Three things define it:
- Screens. Each screen needs design, building, data and testing.
- User roles. A customer app, a driver app and an admin panel are three products, even if they share data.
- Features with hidden depth. Chat, payments, maps and live tracking, offline mode, bookings and notifications each bring rules, edge cases and third-party services.
The most reliable way to control cost is to decide what the first release must do for its first users, and move everything else to later releases.
Platforms and approach
Do you need iOS, Android or both, and on phones only or on watches and tablets too? Building natively for both platforms means two codebases. A cross-platform build with Flutter or React Native shares most of the code, though platform-specific work still exists. Our guide to native versus cross-platform apps explains how to choose.
Back end, admin panel and integrations
Most apps need a server: accounts, data, business rules and notifications live there, and someone needs an admin panel to manage content, users and orders. This part is often as large as the app itself and is the part most often missing from early estimates.
Integrations add to it. Payment providers, CRMs, ERPs, shipping, analytics and identity providers each need setup, testing and handling of their failures.
If you already have a back end or an API, the app may connect to it instead — which changes the estimate considerably.
Design depth
A clean app built from standard platform components costs less to design than one with a custom visual identity, illustrations and animation. Both can be right. What matters is deciding upfront, because changing the design approach mid-build is expensive.
Connected devices and hardware
Apps that talk to hardware — wearables, sensors, medical or industrial devices — carry extra work: pairing and reconnection, live data, syncing stored readings, firmware updates from the app, and testing with real devices and firmware versions. In our connected-wearable case study, much of the engineering sat in exactly these areas.
Estimates for hardware apps are more accurate when the device’s communication protocol is documented and sample devices are available early.
Testing, release and store requirements
Testing covers each feature on the phones and OS versions your users have, plus regression testing before each release. The App Store and Google Play review apps against their guidelines, including privacy disclosures and account deletion; meeting these is part of the work, not an afterthought.
Fixed scope or dedicated team
How you buy the work also shapes cost:
- A fixed-scope project has a defined scope and price. It suits a first release with clear requirements. Changes are handled as change requests.
- A dedicated team is priced by people and time. It suits products whose priorities will change as you learn, or long-term development.
Our article on dedicated teams versus project teams compares the two.
After launch: maintenance, OS updates and hosting
An app is never finished. Apple and Google release new OS versions every year and raise their store requirements; libraries need updates; servers cost money to run; users report problems and ask for features. Plan a budget for the year after launch, not only for the first release.
How to get an estimate you can trust
Share these with any team you ask for an estimate:
- Who the app is for and the one thing it must do well.
- The features for the first release, and the ones that can wait.
- Platforms (iOS, Android, watch, web admin) and any devices it connects to.
- What exists already: designs, a back end, an older app, documents.
- Any deadline and why it exists.
An estimate built on these is far more reliable than one built on a single sentence. If you would like one, send us those details and we will reply with the questions that matter for your scope.