Cost guide
How much does a mobile app cost?
Last reviewed , published by Gjethe
The short answer
A mobile app's cost depends on the number of platforms, the features and screens, whether it needs a backend and admin panel, integrations, design ambition and ongoing maintenance. Pricing is based on your project and agreed in your quote.
App budgets vary more than almost any other software project, because “an app” can mean a simple booking tool or a marketplace with payments, chat and real-time tracking. This guide breaks down what you are actually paying for, which choices change the price most, and the running costs that continue after launch. The sections below explain each cost factor and how it shapes the quote you receive.
What are typical app complexity levels?
Three common app sizes and what moves each one. Your quote depends on the agreed scope.
| Level | Typical scope | What usually moves the quote |
|---|---|---|
| Simple app / MVP | A few core screens, login, basic data, one main user flow | Platforms, design ambition, backend needs |
| Medium complexity | Several user flows, payments or bookings, notifications, admin panel | Payment provider, notification logic, admin features |
| Complex app | Multiple roles, real-time features, many integrations, offline support | Sync and offline rules, integrations, testing across devices |
Which factors change the price most?
Platforms
iOS and Android from one cross-platform codebase usually costs less than two native apps. A web version adds more.
Features and screens
Every user flow (sign-up, search, checkout, chat, settings) is design, development and testing work.
Backend and admin
Most apps need a server, database and an admin panel for your team. These are often as much work as the app itself.
Integrations
Payments, maps, calendars, CRMs or hardware each add set-up and testing.
Real-time and offline
Live tracking, chat and offline sync are technically demanding and raise cost.
Design
Custom animations and illustration cost more than clean, platform-standard interfaces.
Native or cross-platform?
Cross-platform frameworks such as React Native let one codebase run on iOS and Android, which usually reduces build and maintenance effort. Native development (Swift for iOS, Kotlin for Android) makes sense when an app depends heavily on platform-specific features, demanding graphics or the very latest operating system capabilities.
For most business apps, cross-platform offers the best balance of cost and quality. The right choice depends on your features, and a good partner will explain the trade-offs for your case rather than defaulting to what they prefer.
Which costs continue after launch?
| Cost | What it covers |
|---|---|
| App store accounts | Apple Developer Program (annual) and Google Play (one-off registration) |
| Hosting and backend services | Servers, databases, file storage, push notifications |
| Third-party services | Maps, payments, SMS, analytics, error tracking |
| Maintenance | Updates for new iOS and Android versions, security patches, bug fixes |
| New features | Improvements based on user feedback |
How to keep your app budget under control
Start with the smallest version that delivers real value to users, the MVP, and add features based on what people actually use. Many features planned before launch turn out to matter less than expected.
Write down the core user flows before asking for quotes, decide which platforms you need at launch, and check whether an existing tool or a web app would solve part of the problem. Ask every vendor to list what is included, especially the backend, admin panel and app store submission.
What a good app quote should list
- Platforms covered and the technology used
- Screens and user flows in scope
- Backend, database and admin panel
- Integrations and third-party services
- Testing on real devices
- App store submission
- Support after launch and maintenance options
- Who owns the code and accounts
The hidden half of an app
Example: how scope changes the estimate
Imagine a booking app for a chain of clinics. Version A lets patients see available slots and book an appointment, with confirmation emails. Version B adds payments, reminders by push notification, a patient history screen and an admin panel for staff to manage schedules. Version C adds video consultations, insurance checks and an integration with the clinic's practice management system.
Each version is a sensible product, but each step adds design, backend logic, testing and ongoing maintenance. Writing down which version you need at launch, and which features can follow, is the single most useful thing you can do before asking for quotes.
Features that commonly add cost
| Feature | Why it adds effort |
|---|---|
| User accounts and login | Security, password resets, social login and account management |
| Payments and subscriptions | Provider integration, receipts, refunds and app store rules |
| Push notifications | Backend triggers, permissions and testing on both platforms |
| Chat or real-time updates | Live connections, message storage and moderation |
| Maps and location | Permissions, background tracking and battery considerations |
| Offline mode | Local storage and syncing changes when back online |
Frequently asked questions
Why do app quotes vary so much?
Vendors often quote different scopes. One may include the backend, admin panel and store submission; another only the app screens. Compare scope line by line.
Is it cheaper to build for one platform first?
Sometimes. With cross-platform frameworks, supporting both iOS and Android usually adds less than building a second native app, so launching on both is often worthwhile.
Do I need a backend?
If your app stores user data, syncs between devices, sends notifications or has an admin panel, yes. Some simple apps can use managed services that reduce backend work.
How much does app maintenance cost?
It depends on the app's size and how often you add features. Budget for regular updates to keep up with new iOS and Android versions, plus hosting and third-party services.
Can a web app replace a mobile app?
For many business tools, yes. A progressive web app works in the browser and can be installed on phones. Native apps are better when you need deep device features or app store presence.
Who owns the app after it's built?
With Gjethe, you do. Once paid, the code, designs and store accounts belong to you.
Can I get a fixed price?
Yes. Every project gets a fixed quote after a free consultation, based on the agreed scope.
What should I prepare before asking for quotes?
A short description of your users, the main things they need to do, the platforms you need and any systems the app must connect to.
Do app stores take a commission?
Apple and Google charge a commission on many in-app purchases of digital goods and subscriptions. Physical goods and services are usually paid through normal payment providers. Check the current store rules for your business model.
Is it cheaper to reuse our website's backend?
Often, yes. If you already have an API and database, the app can connect to them instead of building a new backend.
Related services
Mobile App Development
iOS and Android apps, from design to store launch.
React Native Development
Cross-platform apps with native modules where needed.
iOS App Development
iPhone and iPad apps that follow Apple's guidelines.
Android App Development
Android apps for the full range of devices.
MVP Development
The smallest product that proves your idea.
UI/UX Design
Research, wireframes, prototypes and interfaces.
Talk it through with us.
Tell us what you need. You get an honest assessment, a clear plan and a written quote. The first consultation is always free.
- What happens next
- 1You tell us what you need
- 2We aim to reply within 24 hours with questions
- 3You get a written quote for your project