Ask three agencies what a mobile app costs and you will get three answers an order of magnitude apart. That is not because someone is lying: "a mobile app" describes anything from a five-screen booking tool to a marketplace with payments, chat and real-time logistics. The price follows the scope, the number of platforms, and above all who writes the code. According to Clutch's app development survey, the majority of mobile apps cost between $25,000 and $200,000. This guide breaks down the real 2026 numbers, explains which variables actually move the mobile app cost, and lists the recurring costs that rarely appear on a quote.
The six variables that decide mobile app cost
Before looking at any number, understand what you are actually buying. A quote is mostly a bet on how many days of work your requirements represent. Six factors drive that estimate.
1. The number of screens and flows
This is the single biggest driver. A screen is not just a layout: it is loading states, empty states, error states, permissions and navigation. A realistic rule of thumb is that each meaningful screen costs between one and three days of build once design is settled. An app with eight screens and one user role is a different animal from one with thirty screens and three roles.
2. Accounts, roles and permissions
An app where everyone sees the same content is cheap. As soon as you introduce sign-up, password recovery, profiles, an admin back-office and different permissions per role, you add authentication, security rules and a whole class of edge cases. Multi-role apps routinely cost 40 to 60 percent more than their single-role equivalent.
3. One platform or two
Building natively for iOS and Android means two codebases, two test cycles and two store submissions. Cross-platform frameworks and web-based approaches remove most of that duplication. If someone quotes you fully native on both platforms, expect roughly 1.6 to 1.8 times the single-platform price, not double, because design and backend are shared.
4. The backend and the data
An app that only displays content is largely a front-end project. An app that stores user data, syncs across devices, sends notifications and exposes an admin panel needs a database, an API, hosting and a security model. That backend is frequently half of the total budget, and it is the part clients most often forget to include when comparing quotes.
5. Third-party integrations
Payments, maps, calendars, CRM, accounting, e-signature, identity verification. Each integration is a small project of its own: credentials, sandbox testing, error handling, and the compliance work that comes with it. Budget one to five days per integration, more for anything touching money or identity.
6. Who actually builds it
The same specification can cost 3 000 or 120 000 depending on the supplier. A senior developer in Western Europe or North America bills between 400 and 900 per day; an agency with project management, design and QA on top lands between 700 and 1 500. Offshore teams are cheaper per day but usually need more days and tighter specifications. AI app builders change the equation entirely by removing most of the build days.
Realistic price ranges in 2026
The table below covers the initial build only, excluding recurring costs. Figures are in euros and are directly transposable to dollars or pounds within a 10 to 15 percent margin.
| Type of app | Typical scope | Agency / freelance | AI app builder |
|---|---|---|---|
| Simple showcase or catalogue app | 5 to 10 screens, no account, content from a CMS | 8 000 – 25 000 | 0 – 1 500 |
| Booking or appointment app | Accounts, calendar, notifications, admin panel | 25 000 – 60 000 | 500 – 4 000 |
| Internal business app | Roles, forms, offline data, exports, SSO | 35 000 – 90 000 | 1 000 – 6 000 |
| Marketplace or two-sided platform | Two user types, payments, messaging, reviews | 70 000 – 200 000 | 3 000 – 15 000 |
| Social or real-time app | Feeds, chat, media upload, moderation, scale | 120 000 – 400 000+ | Partial fit, expect custom work |
Two observations matter more than the exact figures. First, the gap between the low and high end of each row is driven almost entirely by scope discipline, not by supplier greed. Second, the further right you go in the table, the more the cost shifts from "building it" to "running it".
The recurring costs nobody puts on the quote
A mobile app is not a one-off purchase. Plan for 15 to 25 percent of the initial build cost every year just to keep it alive and in the stores.
- Store accounts: 99 per year for the Apple Developer Program, a one-off 25 for Google Play. Non-negotiable if you want to be in the stores. With millions of apps competing for attention, these fees are just the entry ticket.
- Hosting and database: from a few euros a month for a small app to several hundred once you have real traffic, media storage and backups.
- Mandatory OS updates: Apple and Google ship new versions every year and periodically raise the minimum SDK. An app left untouched for two years will eventually be removed from the store.
- Third-party fees: payment processing, mapping, transactional email and SMS all bill per use and grow with your success.
- Support and small changes: the price change, the new field on a form, the bug on one specific Android model. Budget a few days per quarter.
- Store commission: if you sell digital goods inside the app, Apple and Google take 15 to 30 percent. This can dwarf every other cost in this list.
Freelance, agency or AI builder: what you actually get
Price is only half the decision. The three routes fail in different ways, and knowing how matters more than knowing the day rate.
- Freelance developer: the best value per day and direct communication. The risk is the bus factor, one person's availability, holidays and priorities become yours. Works well for a well-specified first version.
- Agency: design, project management, QA and continuity are included, which is why the day rate is higher. Worth it when the app is business-critical or when you have no technical person internally to arbitrate. The risk is paying for process on a project that did not need it.
- AI app builder: you describe the app and iterate on a working version in hours instead of weeks. The cost collapses because the build days collapse. The trade-off is that you own the product decisions: nobody is going to challenge your scope for you.
Five ways to cut the bill without cutting the product
Most overspending on mobile projects is decided before a single line of code is written.
- Ship one platform first. Look at your existing web analytics. If 70 percent of your audience is on Android, there is no reason to fund iOS in month one.
- Cut the admin panel. A custom back-office is often 30 percent of the budget for a version 1 that will have twenty users. A spreadsheet or an off-the-shelf tool buys you six months.
- Question every push notification. Notifications, deep links and background sync are individually small and collectively expensive. Add them once you know which ones users want.
- Check whether you need an app at all. If your users will not open it weekly, a well-built responsive site or a progressive web app delivers most of the value at a fraction of the cost and with no store review.
- Prototype before you commission. A clickable version you can put in front of ten real users will cut more waste from the specification than any negotiation on the day rate.
Building your mobile app with Cadrant
Cadrant exists for the part of this problem that is pure cost: turning a clear idea into a working application. You describe the screens, the data and the roles in plain language, and you get an application you can open on your phone in minutes, then refine by conversation. Because the data layer runs on your own Supabase project, you keep ownership of the database and can hand the whole thing to a developer later without a migration.
In practice this changes the budgeting question. Instead of asking "can I afford to find out whether this app works?", you build a real version, put it in front of users, and only then decide where paid engineering effort is worth it, usually on the two or three flows that genuinely differentiate you.
The takeaway on app development cost
The mobile app cost is a consequence of decisions you control: how many screens, how many platforms, how much back-office, and who builds it. Fix the scope first, price it second. And before you commit a five-figure app development cost, build a working version cheaply and put it in real hands, the specification that survives that test is the only one worth paying full price for.