How Much Does It Cost to Build a Mobile App?

Ask 5 developers what your app will cost and you might get 5 answers that differ by a factor of 10. That is not because someone is lying. It is because “an app” can mean a 6-screen booking tool or a full marketplace with payments, chat, maps and an admin dashboard.

The good news: once you understand what drives the price, you can estimate your own range and compare quotes intelligently. This guide explains the cost drivers by feature and team model, the fixed fees every app pays, the ongoing costs people forget, and a step-by-step way to build your own estimate.

The basic formula

Almost every app quote comes down to this:

Total cost = (hours of work across design, development, testing and project management) x (hourly rate of the team) + fixed fees + ongoing costs

Hours depend on features and platforms. Rates depend on who you hire. Fixed fees are small and predictable. Ongoing costs are where budgets quietly blow up. Each part is covered below.

Cost driver 1: features and complexity

Features drive hours more than anything else. Each one needs design, front-end screens, often server-side logic, and testing. Here is how common features compare in relative effort.

Most apps also need a backend: the servers, database and APIs that store data and power the app. If your app has accounts or shared data, the backend can be as much work as the app itself. Our guide to what an API is explains how the two connect.

Regulated data adds cost too. Health apps may need HIPAA safeguards (see HIPAA compliance for software), and apps that handle card data must follow PCI DSS, although using a payment provider’s hosted checkout reduces that burden.

Cost driver 2: platforms

You have 4 main options, each with different hour counts:

• One platform only (iOS or Android). Lowest cost; a good start if your customers lean heavily one way.
• Cross-platform (Flutter, React Native, Kotlin Multiplatform). One main codebase for both platforms, usually fewer total hours than 2 native apps.
• Native on both platforms. 2 codebases and typically 2 skill sets, so the highest hours for the same features.
• Mobile web app or progressive web app. Often the cheapest way to reach phones, with trade-offs in device features and app store presence.

Our guides to native vs cross-platform development and Flutter vs React Native cover how to choose.

Cost driver 3: who builds it

The same hours cost very different amounts depending on the team model.

For in-house budgeting, the US Bureau of Labor Statistics reported a median annual wage of $135,980 for software developers and $104,300 for software quality assurance analysts and testers as of May 2025. Benefits, taxes, tools and recruiting add to that. Agency and freelance rates vary widely by region and experience, so collect real quotes rather than relying on averages. For a deeper comparison, see IT outsourcing vs in-house.

Key takeaway: Features and team model drive most of the cost. Cutting your first version to the features that prove the idea, then choosing a team model you can manage, will save more money than haggling over hourly rates.

The fixed fees every app pays

These are small but unavoidable:

• Apple Developer Program: $99 per membership year to publish on the App Store. Fee waivers exist for qualifying nonprofits, accredited educational institutions and government entities.
• Google Play Console: a one-time $25 registration fee.
• Store commissions: both stores take a cut of digital goods and subscriptions sold in the app. Apple’s Small Business Program offers a reduced 15% commission for developers earning up to $1 million in proceeds a year. Google Play’s service fees vary by product type, program and region, and both companies have revised their US terms recently, so check the current rules before you price in-app purchases. Physical goods and services sold through an app generally use your own payment provider instead.
• Developer accounts and tools: design software, testing devices, analytics and crash reporting, many with free tiers.

The ongoing costs people forget

Launch is not the finish line. Plan for these from the start:

• Hosting and cloud services. Servers, databases, storage and bandwidth are usually billed by usage, so costs rise with users. Our guide to how cloud pricing works explains the models.
• Third-party services. Maps, SMS, email, payments and AI APIs often charge per use.
• OS and framework updates. Apple and Google release major OS versions every year, and app stores update their requirements. Cross-platform frameworks have their own upgrade cycles.
• Bug fixes and small improvements. Real users find issues testers did not.
• Security updates. Dependencies need patching when vulnerabilities are found.
• Support and monitoring. Someone needs to watch crash reports and answer users.

Many teams set aside a yearly maintenance budget as a share of the original build cost. Ask each vendor what their maintenance plan includes and how it is priced.

How to estimate your own range

Follow these steps to turn a vague idea into a budget you can defend:

1. Write the user stories. List what each type of user needs to do, such as “a customer can book an appointment and get a reminder.”
2. Cut to an MVP. Mark the stories you need to prove the idea. Everything else goes to version 2. Our MVP development guide explains how.
3. Choose platforms. One platform, cross-platform or native on both.
4. Sketch the screens. Even rough wireframes reduce estimate uncertainty a lot.
5. Identify integrations and regulated data. These are the most common sources of surprise cost.
6. Get 3 quotes from different team models. Ask each to break hours down by feature, design, testing and project management.
7. Add fixed fees and a contingency. Unknowns always appear; a buffer keeps the project alive.
8. Add year 1 running costs. Hosting, third-party services and maintenance.

When comparing quotes, look for what is excluded. A low quote that skips testing, the backend, the admin panel or app store submission is not actually cheaper. Make sure you own the code, design files and accounts, and that the code lives in a repository your company controls.

Ways to lower the cost without cutting quality

• Launch on one platform or go cross-platform.
• Use proven services for login, payments and notifications instead of building them.
• Start with a web-based admin panel built from an existing tool rather than a custom one.
• Reuse your existing website’s backend if it already has an API.
• Phase features over releases based on real user feedback.
• Invest in clear requirements upfront; changing scope mid-build is one of the most expensive things you can do.

For context on adjacent budgets, see how much a website costs and custom software development cost.

The bottom line

There is no single price for an app because there is no single kind of app. Your cost comes from features, platforms and team model, plus small fixed store fees and ongoing running costs that continue after launch. Define an MVP, sketch the screens, get itemized quotes from different team models and budget for year 1 maintenance. That approach gives you a realistic range and a plan to grow from there.

Sources

• Apple Developer Program enrollment — $99 annual membership and fee waivers
• Apple App Store Small Business Program — 15% commission for developers earning up to $1 million in proceeds
• Google Play Console Help: registration fee — one-time $25 registration fee
• Google Play Console Help: service fees — current service fee structure by region and product type
• US Bureau of Labor Statistics: Software Developers, QA Analysts and Testers — May 2025 median annual wages