Guide · Azerbaijan market
What determines the cost of a mobile app
"How much does an app cost?" has the same answer as "how much does a house cost?" — it depends on what you build. A simple app with a few screens and a small backend and a platform with several user roles, payments, real-time tracking and integrations are different orders of effort. This guide lists the factors that drive the budget, so you can shape the scope before asking for estimates.
[ 01 ]
In short
In short
- 01
The app is only part of the product; the server, database, admin panel and integrations often take as much work.
- 02
The number of distinct screens and user roles is the clearest predictor of scope.
- 03
Cross-platform development usually costs less than two native apps; native is justified by specific needs.
- 04
Offline work, real-time features, complex payments and hardware integrations add significant effort.
- 05
Publishing, updates for new OS versions and support are recurring costs.
[ 02 ]
Guide
Factor 1: platforms
- iOS and Android with a cross-platform framework (Flutter, React Native) — one codebase, most common for business apps.
- Two native apps — separate codebases, higher cost, maximum platform capabilities.
- One platform first — if your users are overwhelmingly on one.
- Progressive web app — no stores, lower cost, some limitations. See PWA vs native app.
See native vs cross-platform apps.
Factor 2: screens and roles
Count the distinct screens a user sees and the roles in the system: customer, courier, manager, administrator. Each role often needs its own screens and permissions — sometimes its own app. A customer app plus a courier app plus an admin panel is three products sharing one backend.
Factor 3: backend and admin panel
Most business apps need:
- user accounts and authentication;
- a database and business logic;
- an API for the app;
- an admin panel for your team — content, orders, users, notifications;
- push notification infrastructure;
- analytics.
If you already have a backend — for example, for your website — the app may reuse it, which reduces cost.
Factor 4: integrations
Payments through a local provider, CRM, 1C, delivery services, maps, identity verification, messengers. Each integration's cost depends on the quality of the other system's API and documentation. See API integrations.
Factor 5: complex features
These add significant effort:
- Offline mode with synchronisation and conflict handling.
- Real-time features: live tracking, chat, collaborative editing.
- Maps and geolocation with routing or background tracking.
- Media: video recording, processing, streaming.
- Hardware: Bluetooth devices, NFC, specialised scanners.
- Complex payments: subscriptions, split payments, wallets.
Factor 6: design
Custom design for both platforms, with every state — loading, empty, error — and accessibility considered, takes more time than adapting a design system, but shapes how the app is perceived and used.
Factor 7: languages
Azerbaijani, Russian and English versions require translation, layout checks for longer texts and localised formats for dates, numbers and currency.
Factor 8: quality assurance
Testing across devices and OS versions, automated tests for critical logic, and beta testing with real users. Skipping testing does not remove the cost — it moves it to after launch, where it is higher.
Factor 9: publishing and support
- Developer accounts with Apple and Google, and preparation of store listings.
- Store review, which sometimes requires changes.
- Updates for new iOS and Android versions every year.
- Monitoring of crashes and performance.
- Server hosting and maintenance.
See publishing apps to the App Store and Google Play.
How to reduce the cost sensibly
- Define the first release around one core scenario. See defining MVP scope.
- Replace secondary features with manual processes for the first users.
- Reuse existing backends and admin panels.
- Choose cross-platform unless there is a clear reason not to.
- Postpone offline mode and real-time features unless they are central.
[ 03 ]
FAQ
Frequently asked questions
Can you give a typical price for an app?
Not responsibly without a scope. We give a fixed estimate after defining the first release, the screens and the integrations.
Is it cheaper to build a website first?
Often yes. A web app or PWA can test demand, and a native or cross-platform app can be added later on the same backend.
What recurring costs should we expect?
Hosting, store developer accounts, updates for new OS versions, monitoring, bug fixes and gradual improvements. Plan for them from the start.