Mobile App Development Costs: Which Features Drive the Budget?
The budget for a mobile app is driven far more by its features than by its number of screens. Two apps with ten screens each can differ several times over in effort if one only shows a catalogue and the other has user accounts, payments, offline work and a connection to your stock system. This article walks through the features that move the budget most, so you can decide what belongs in the first version and compare quotes on the same basis. It deliberately contains no prices, because they depend entirely on scope.
Where the effort goes
An app is more than what you see on the phone. A quote usually covers the app itself (screens, navigation, loading and error states), the server and API, an admin panel for your staff, testing on different phones and connections, store publishing, and support after launch. Many features touch all of these – which is why "just add a login" or "just add payments" is rarely a small job.
1. Platforms and devices
iPhone, Android or both? Phones only, or tablets with their own layouts too? A cross-platform framework lets one codebase serve both platforms, but each still needs its own testing, store listing and occasional platform-specific work – see native vs cross-platform development. Starting on one platform can be a sensible way to test the idea: roadmeter.app, for example, is available on Android, with an iPhone version coming.
2. The back end: is there already a server and an API?
This is often the largest hidden item. If your data – products, prices, bookings, customer accounts – already lives in a system with a documented API, the app can use it. If not, the server, database and API have to be built first, which can be as much work as the app. The car specifications catalogue auto-data.net shows the efficient case: its website, its Android and iOS app and a paid API all work from one database, so the app didn't need a data source of its own. More in one API for a website and a mobile app.
3. User accounts and login
An app without accounts is considerably simpler. Accounts bring registration, login, password reset, email confirmation and profile editing – and store rules:
- Apple's App Review Guidelines say: "If your app doesn't include significant account-based features, let people use it without a login."
- If the app supports account creation, Apple requires that you "also offer account deletion within the app". Google Play requires an in-app path to delete the account and associated data, plus a web link where users can request deletion.
- If the main account uses a third-party or social login, Apple requires an equivalent alternative login option with specific privacy features.
Each login method is one more thing to build, test and support. Several roles with different permissions – managers, staff, partners – add more; see user roles and permissions.
4. Payments
How you take money depends on what you sell, and store rules shape part of the design:
- For physical goods or services used outside the app – food, tickets, repairs – Apple's guidelines say you "must use purchase methods other than in-app purchase", such as Apple Pay or card entry through a payment provider.
- For digital content or features unlocked inside the app – subscriptions, premium content – Apple's guidelines require in-app purchase, with its own setup and subscription states. The rules differ by region (apps on the United States storefront, for example, may link to other purchase methods), so check the current text for your markets.
Refunds, failed payments, invoices and reconciliation with your accounting add further work.
5. Offline work and synchronisation
"It should work without internet" can mean very different things. Showing recently loaded data offline is manageable; letting people create and edit data offline and syncing it later is much harder. Android's guide to offline-first apps calls writing locally first and syncing later "nontrivial because there can be conflicts between the network and local data sources", and notes that an offline-first app doesn't have to support writing data offline at all. Decide which actions truly need to work without coverage – a technician's report on site, for example – and keep the rest online.
6. Device features
Camera, barcode scanning, location, maps, Bluetooth devices, sensors – each needs a permission request, sensible behaviour when the user says no, and testing on several real devices. Features that keep running in the background, such as recording a route with the screen off, are the most demanding. An app like roadmeter.app, which measures trips, acceleration, braking and track laps with the phone's GPS and sensors, illustrates the point: in apps of this kind the screens are rarely the hard part – reliable measurements across different phones are.
7. Notifications
Push notifications need a server side that decides who gets what and when, in-app settings for users, and a permission flow on each platform. Automatic order or booking updates also depend on the system that knows the status.
8. Integrations with other systems
Connections to a CRM, ERP, stock or accounting system, payment and delivery providers are the hardest items to estimate, because the effort depends on the other side: whether it has a documented API, how clean its data is and how it reports errors. Our article on API integrations explains what to find out in advance.
9. Languages
Each language adds translated texts, store listings, date and number formats, and testing – and language handling can break in unexpected places. An Italian user of the auto-data.net app once reported that the app stayed in English after choosing Italian: the website had started passing the language code as "it,it-IT,it-CH" instead of "it", and the API didn't recognise it. The fix was to normalise language codes in the API. That is why every language needs testing, not just translating.
10. Design, privacy and accessibility
Standard platform components are faster to build and familiar to users; a fully custom look and complex animations add time, which pays off mainly when the brand is part of the product.
Every app on Google Play must complete the Data safety form, which includes data "collected and handled through any third-party libraries or SDKs" – analytics, crash reporting, advertising. Each extra tracking tool adds paperwork as well as code. Accessibility – readable text at larger font sizes, screen reader labels, sufficient contrast – is much cheaper to build in from the start than to add later.
Costs outside the code
- Developer accounts. Apple's Developer Program costs 99 USD per membership year (prices may vary by region and are shown in local currency during enrolment). Google Play charges a one-time registration fee of US$25. Organisations enrolling with Apple need a D-U-N-S Number and a working public website; Google Play also verifies the developer's identity.
- Store materials and services – screenshots, descriptions, a privacy policy, hosting, and usage-based services such as maps or SMS.
- Upkeep – support, bug fixes, and changes when a store raises its technical requirements (our article on apps and mobile websites gives a current example). Updating a working app just because a newer version of something exists isn't a cost to plan for; updating when a store, a security issue or a needed feature requires it is.
Simpler and bigger versions of the same feature
| Feature | Simpler version | What makes it bigger |
|---|---|---|
| Accounts | No login, or email and password | Several login methods, family or company accounts |
| Payments | Payment on delivery or a payment provider's page | Saved cards, subscriptions, refunds, invoices |
| Offline | Recently viewed data readable offline | Creating and editing offline, with sync |
| Location | A map and address search | Continuous tracking, including in the background |
| Admin | One administrator | Roles, approval steps, change history |
How to keep the budget under control
- Write down the one job the app must do well, and rank every feature against it.
- Mark each feature "launch", "soon after" or "later" – our guide to defining an MVP without removing what users need helps.
- Find out early whether a usable API exists; if not, plan for it explicitly.
- Ask every developer to split the quote by feature, so you compare like with like.
- Agree in advance how changes will be handled – see why software projects go over budget.
If you are planning an app, send us the features you have in mind and tell us what already exists – a website, a database, an API, systems the app should talk to. We'll help you separate what the first version needs from what can wait, and estimate based on that scope. See our mobile app development service or contact us.
Sources
- App Review Guidelines – Apple Developer
- Become a member – Apple Developer Program – Apple Developer
- Get started with Play Console – Play Console Help
- Understanding Google Play's app account deletion requirements – Play Console Help
- Provide information for Google Play's Data safety section – Play Console Help
- Build an offline-first app – Android Developers