If you are budgeting for an app this year, here is the blunt answer first. For most business apps built by an outsourced team, mobile app development cost lands somewhere between about $10,000 and $150,000, and complex products can go well past that. It is a wide range, but it is not random. Where your project falls depends on a few things you can already see in your own feature list, and by the end of this article you should be able to estimate your own number before you speak to a single developer.
Every figure below is a rough market range, not a quote. Real prices vary with scope, with the region your team works from, and with how experienced that team is.
Rough mobile app development cost ranges for 2026
Most business apps fit one of three shapes.
- Simple app, roughly $10,000–$25,000. A handful of screens, user login, content pulled from a basic backend, perhaps push notifications. No payments and no complicated user roles. Think of a loyalty card app or an events guide.
- Typical business app, roughly $20,000–$90,000. User accounts, bookings or orders, online payments, notifications, an admin panel for your staff, and one or two integrations with systems you already use.
- Complex app, $100,000 and up. Real-time features such as chat or live tracking, a marketplace with two or three types of users, offline sync, heavy integrations, or strict data rules in areas like healthcare and finance.
These ranges assume a team billing around $20–$50 an hour, which is common for experienced teams in India. Agencies in the US, UK or Australia often bill $100–$200 an hour or more, so the same scope can cost two to four times as much. A higher rate can buy you time-zone overlap or local legal knowledge. It does not automatically buy better code, so judge a team by its past work and by the questions it asks you, not by its rate.
Where the money actually goes
When people picture an app, they picture the screens. The screens are often less than half the work. A realistic budget covers all of this:
- Design. Wireframes, then the visual design of every screen and every state: empty lists, errors, loading, permission prompts.
- The app itself. Screens, navigation, forms, and the logic that runs on the phone.
- The backend. The server, database and API that store accounts, bookings and orders and enforce your business rules. For a business app this is frequently as large as the app.
- An admin panel. Someone on your side has to manage users, content, bookings and cancellations. That needs its own screens, permissions and testing.
- Integrations. Payment gateways, SMS or WhatsApp messages, maps, and any system you already run, such as accounting software or a CRM. Each one adds setup, testing and handling for when it fails.
- Testing. Checking every flow on a spread of real Android and iOS devices and screen sizes, not only on the developer's own phone.
- Release and project management. Store listings, privacy disclosures, builds, review cycles, and the weekly back-and-forth that keeps the work on track.
If a quote only talks about screens, ask where the rest is. Either it is hidden in the price or it is missing, and you want to know which before you sign.
Estimate it yourself: a worked example
The most useful way to think about cost is features × effort × rate, plus a buffer. Here is how that works for a realistic, hypothetical project.
Say you run a salon with three branches. You want an app where customers pick a branch, a service and a stylist, book a slot, pay a small deposit, and get a reminder the day before. Your staff need to manage schedules and bookings from a computer. A cross-platform build for Android and iOS might break down like this. The hours are illustrative and cover app, backend and testing for each feature.
- Sign-up and login with a phone number and one-time code: 30–50 hours
- Browse branches, services and stylists: 40–60 hours
- Booking calendar with live availability and clash checks: 80–120 hours
- Deposit payment through a payment gateway: 40–60 hours
- Push and SMS reminders: 30–50 hours
- My bookings, with cancel and reschedule: 30–50 hours
- Web admin panel for staff, services, schedules and bookings: 100–150 hours
- UI design for around 15 screens: 60–90 hours
- Testing across devices: 80–120 hours
- Project management, store setup and submission: 60–90 hours
That adds up to roughly 550–840 hours. At $30 an hour, the build comes to about $16,500–$25,200. At $120 an hour, it is about $66,000–$100,800. Then add 15–20% contingency for what nobody knows yet, such as a payment gateway with awkward documentation.
Two lessons come out of this. First, the booking calendar and the admin panel are the expensive parts, not the attractive screens. Second, once you ask each vendor for a breakdown like this, you can compare quotes line by line instead of comparing totals that quietly describe different apps.
Notice what is not in the list: the app store's own billing system. A deposit for a haircut pays for a physical service used outside the app, so Apple's guideline 3.1.3(e) requires a normal payment method such as Apple Pay or card entry rather than in-app purchase, and Google Play's payments policy likewise keeps physical services out of Google Play billing. You pay your payment gateway's fees, not a store commission. Digital products are a different story, covered under costs after launch below.
One codebase or two?
Building separate native apps, Swift for iOS and Kotlin for Android, means writing and testing the app side twice. The backend and admin panel are shared, so the total does not double, but the app portion comes close to it.
Cross-platform frameworks let one team ship to both stores from one codebase. For most business apps (bookings, orders, accounts, catalogs, content) we would build version one with Flutter for iOS and Android together, because it removes a large share of the app-side work and, for this kind of app, users rarely notice a difference. Native still makes sense when the core value depends on deep platform features, such as advanced camera or AR work, long-running Bluetooth connections, or watch and widget extensions, or when you already employ separate iOS and Android developers.
Costs that arrive after launch
The build is a one-off. These are not.
Store accounts and commission
Publishing on the App Store requires the Apple Developer Program, which Apple lists at 99 USD per membership year, with local-currency pricing in some regions. Google Play charges a one-time US$25 registration fee.
If you sell digital goods or subscriptions inside the app, the stores take a share. Apple's Small Business Program charges 15% for developers who earned up to 1 million USD in proceeds in the previous calendar year. Google Play's fees depend on the market and the type of transaction, and Google has been rolling out a revised, lower fee structure since 30 June 2026 in the US, UK and EEA, with other regions following later. Check Google Play's current service fees for your market before you set prices.
Yearly platform updates
Even an app with no new features needs work every year, because both stores keep raising their technical minimums. From 31 August 2026, new apps and updates on Google Play must target Android 16 (API level 36). On Apple's side, apps uploaded since 28 April 2026 must be built with Xcode 26 and the iOS 26 SDK. Each change means updating libraries, rebuilding and retesting.
Hosting, services and maintenance
Servers, database, SMS credits, map lookups, email and crash reporting all bill monthly. For a small app with modest usage this can be tens of dollars a month, and it grows with your users. Beyond that, a sensible planning figure for maintenance (bug fixes, OS updates, small improvements) is around 15–20% of the build cost per year.
Time before launch
If you publish from a personal Google Play developer account created after 13 November 2023, Google requires a closed test with at least 12 testers opted in for at least 14 days before you can apply for production access. Put those weeks into your launch plan instead of discovering them at the end.
How to spend less without cutting corners
The biggest lever on your mobile app development cost is scope, so most of these come back to it.
- Cut scope, not quality. Launch the core path (find, book, pay, get reminded) and add loyalty points, reviews and referrals once people are using it. A smaller app built properly costs less to extend than a large one built in a hurry.
- Keep admin work on the web. Staff tools rarely need to live in the phone app. A web admin panel is cheaper to build and easier to use at a desk.
- Use managed services for the plumbing. Authentication, push notifications and crash reporting do not need to be written from scratch. Services such as Firebase for login, messaging and crash reports handle them for a small monthly cost.
- Have your content ready. On time-and-materials projects, waiting for copy, prices and photos is paid time.
- Be suspicious of a quote far below the others. It usually means something from the list above is missing, and it will come back later as a change request.
Also ask whether you need an app at all. If customers will use it once or twice a year, a fast, mobile-friendly website with online booking may do the job at a fraction of the cost. An app earns its place when people come back often, or when it needs the phone itself: location, camera, notifications, offline use. AtoZ Mobile Hub, a location-based app we built to help people find nearby mobile shops and offers, is an example of the second kind, because knowing where the user is standing is the whole idea.
What to do before you ask for quotes
Write your feature list as plain sentences, one per line, and mark each one "must have at launch" or "later". Note every system the app must talk to. Then send the same list to every vendor and ask for hours per feature, the hourly or daily rate, and what is excluded. You will get quotes you can compare, and the questions each team asks back will tell you a lot about how they work.
If you would like a second opinion on your feature list, or a breakdown you can hold other quotes against, send us the details and you will hear back within 24 hours. You can also look at how we structure project pricing before you get in touch.
