Mobile app development costs: 7 decisions that shape your budget

Content authorBy Lincoln WoolseyPublished onReading time12 min read
Flat lay of a smartphone with an app wireframe, calculator, printed supplier quotes, and an orange pen on a light desk in a modern office.

A budget for an operational business app usually starts as a guess, and quotes from different suppliers rarely help because they are built on different assumptions. Replace the guess with a fillable cost model, then work through the seven scoping decisions that move the number up or down. Once your own figure is in place, you can compare supplier quotes that look nothing alike and see what each one includes, and what it leaves out.

Where the number comes from

Most mobile app development cost estimates fall apart for the same reason: people agree on a number before deciding what the app does or who uses it. McKinsey and the University of Oxford studied more than 5,400 IT projects and found large ones run 45 percent over budget on average. Software projects had the worst record.

You can make that risk visible. A budget built from workstreams, agreed rates, and a stated contingency survives contact with reality better than a single figure in a board pack. The rest of this article builds that budget with you, then shows how to hold three suppliers to the same definition of done.

Mobile app development cost model

Start with a worksheet. Every mobile app development cost model has the same shape: estimated effort by workstream multiplied by an agreed rate, plus the things that aren't people and the things that recur every month after launch. Keep those three groups apart on the page, because mixing them is how a twelve-month commitment gets presented as a one-off.

Here are the workstreams to price separately:

  • Discovery, prototyping, and the tested interface assumptions that come out of it

  • Interface design across the device sizes you actually support

  • Mobile build, split by platform if you're going native

  • Backend, application programming interfaces (APIs), and integrations with the systems you already run

  • Administration console for the people who configure and audit the app

  • Quality assurance (QA), including testing on real hardware

  • Delivery management, which is real effort and belongs on the sheet

Then add non-labour one-off items. Test devices and store accounts belong here, as do third-party licences and any security review you commission from outside the delivery team. The Apple Developer Program costs 99 USD a year and a Google Play Console account costs 25 USD one-time, which are trivial sums that get forgotten and then block a release.

Recurring costs form the third block, from hosting to the engineering time that keeps the app alive through operating system changes. Finally, write down what your own organisation owes the project in days. Someone has to approve designs and supply test data. Show contingency as its own line with a stated percentage and a stated reason, never folded into the estimates.

A calculated budget example

What follows is a worked example for a field-inspection app. Replace every assumption with your own. Scope: one app for inspectors working across sites on iPhone and Android, with offline inspection forms and a two-way integration with an existing asset register. Currency is GBP, and all figures exclude VAT. The assumed blended rate is £650 per day.

Effort by workstream: discovery and prototype 15 days, and interface design 20 days. Mobile build 85 days and backend and integration 55 days. Administration console 25 days, and QA and device testing 30 days. Delivery management 25 days. That's 255 days, or £165,750 at the assumed rate. Contingency at 15% adds £24,863, because the asset register's API hasn't been profiled yet and the inspection workflow has three regional variations nobody has written down.

Non-labour one-off costs add roughly £6,000 for 20 test handsets and tablets, plus the two store accounts. Delivery total lands near £196,600. Year-one recurring costs sit outside that: £10,800 for hosting and monitoring plus £23,400 for a three-day-per-month support retainer. A further £1,800 for error reporting and analytics brings the year-one total to £36,000.

Customer-owned work is 32 days of an operations lead's time over 16 weeks, plus data cleansing in the asset register. Excluded: translation, device hardware refresh, licence changes on the asset system, and an independent penetration test. Change the rate or the contingency and the whole mobile app development cost moves, which is the point of building it this way.

Seven budget decisions

Horizontal infographic with bright orange background, featuring seven white line icons and descriptions for budget decisions in British English.

Before you touch any of the seven, record the boundary conditions in writing. Target countries. Languages. Whether the app goes through public stores or private distribution. The device estate your people already carry, down to the oldest model still in service. And the conditions the app has to work in, because a loading bay with no signal is a different product from a desk.

Each decision below changes the effort or the commitment you're signing up to after launch, and therefore the mobile app development cost. Treat those as separate consequences. A choice that saves ten build days and adds a monthly obligation hasn't saved you anything.

Ready to bring your ideas to life?

Book a free 30-minute discovery call with our team — we'll understand your objectives and advise how bespoke software, MVP development, or an extended team can help your business.

Platforms and devices

In the UK, the split is close to even, with iOS at 46.9% of mobile page views in September 2026, so a public-facing app needs both. An internal app for a managed device estate is a different question, and one answer is to support a single platform and say so in the contract.

Tablets aren't free. A tablet layout is a second design pass, a second set of interaction states, and more QA. Managed hardware with a Mobile Device Management (MDM) profile removes some distribution work and adds configuration work in its place.

React Native lets one team share the bulk of the interface and logic across both platforms. Platform-specific work in camera handling and store compliance still carries its own cost. Shopify's own React Native team reported app launch times improving by about 10% on Android after a major framework migration, which is the kind of maintenance work a shared codebase still demands. When Shopify later rebuilt its Shop app natively, it reported cold start dropping 23% on iOS. Both framings are true, and both have a budget line.

Journeys and accessibility

List the roles first. An inspector and a supervisor who approves are products sharing a login, as is an administrator who configures. Then name the priority tasks for each role and the workflow variations between regions, sites, or contract types, because variations are where estimates quietly double.

Languages multiply content and testing, so decide now rather than at user acceptance testing. Accessibility is scope with a published definition: WCAG 2.2 added nine new success criteria when it was published in October 2023, several aimed squarely at touch targets and focus visibility on mobile.

Don't accept a build estimate against a feature list. Steve McConnell's cone of uncertainty puts concept-stage estimates at 4x high or 4x low, and the range narrows to roughly ±25% once interface design is done. A tested prototype is the cheapest way to move along that curve.

Backend and integrations

Scope each API by name, direction, and owner. Who maintains the asset register endpoint you're calling? If the answer is a third party with a release schedule of their own, that's a dependency with a date attached, and your supplier can't control it.

Data mapping deserves its own mobile app development cost estimate. Field names, units, and the inevitable free-text column holding three kinds of information are discovery work, done once, properly. Administration tooling also hides here, since someone has to manage users and reference data.

Watch for backend effort appearing twice. It turns up inside the mobile estimate and again under integration. Ask each supplier to show backend days in exactly one place on the sheet.

Offline and device features

Describe the conditions, not the feature. Ofcom's spring 2026 update put good 4G geographic coverage from all four operators at 84% of UK landmass, with 96% covered by at least one. Your inspectors work in the gaps and inside steel structures.

"Offline" covers a wide range of engineering. Read-only cached data is modest work. Full local capture with background synchronisation and conflict resolution, where two people edit the same record on different devices, is a substantial piece of design before anyone writes code. Decide which conflicts the app resolves automatically and which ones a supervisor sees.

Device features follow the same logic. Camera capture with compression and retry, and background location, each carry permission flows and testing on the oldest handset in your estate. Price them individually against how the work actually happens.

Ready to bring your ideas to life?

Book a free 30-minute discovery call with our team — we'll understand your objectives and advise how bespoke software, MVP development, or an extended team can help your business.

Data identity and security

Classify the data before you design the login. Inspection photographs that include people, site addresses, and engineer identities each carry different handling obligations. The Information Commissioner's Office is explicit that UK GDPR sets no fixed retention periods, so your retention schedule is a decision you make and justify, and it becomes a feature the app has to implement.

Authentication choices drive mobile app development cost. Single sign-on against your identity provider and role-based permissions are separate builds, as is an audit trail of who changed what. The National Cyber Security Centre recommends a session timeout of 15 minutes for sensitive information, which sounds minor until you discover what re-authentication does to a workflow performed in gloves.

Write down who owns device controls and who commissions the security review. If your insurer or a customer requires independent testing, that's a named cost and a date in the plan, held by one party.

Testing and distribution

Name the supported devices and the minimum operating system versions in the contract, and attach acceptance criteria to each priority task rather than to the app as a whole. Accessibility testing needs its own line that covers manual checks with assistive technology.

Distribution shapes the release calendar. Apple reports that 90% of submissions are reviewed in under 24 hours, though an incomplete submission stretches that considerably. Google Play requires new apps and updates to target Android 16 from the August 31, 2026 deadline, which is a recurring obligation.

For an internal workforce app, consider private routes. Apple supports custom apps for organisations through Apple Business Manager, and there's also unlisted app distribution by direct link. Either way, agree who supplies test accounts and the sign-off for each release.

Operation and change

A launched app has a running mobile app development cost that nobody estimated at kickoff. Hosting and monitoring. Error reporting. Support hours for the inspector whose sync failed at 7 am. Analytics, if you plan to learn anything from usage.

Then there's the work the platforms impose on you. Annual operating system releases break things. Store policy changes arrive with deadlines. Integration endpoints get versioned by their owners. Budget this as capacity and decide whether it sits with your team or with a partner running Tier 2 technical support. Future releases are a separate roadmap with separate funding, and keeping them separate from the initial delivery is what stops "phase two" from eating the first launch.

Compare quotes consistently

Three quotes for the same brief will differ by more than price, and almost always because they scoped different things. Normalise them before you compare anything. Rebuild each one onto your own worksheet, line by line, and the real differences in mobile app development cost surface quickly.

Align these before you look at any total:

  1. Scope statement, expressed as roles and priority tasks rather than feature names

  2. Workstreams and the days allocated to each, with backend shown once

  3. Rates, rate changes over the contract, and what counts as a chargeable day

  4. Stated assumptions and stated exclusions, written as a list you can challenge

  5. Contingency percentage and what it's reserved for

  6. Recurring charges, separated into hosting, support, and licences

  7. Customer inputs, in days, by role and by week

  8. Acceptance criteria and who signs them off

  9. Intellectual property ownership of code, designs, and infrastructure definitions

  10. Support responsibilities after go-live, including response times and escalation

When a quote looks cheaper, find the line it's missing. A total mobile app development cost that excludes device testing or the administration console is a smaller promise. Ask each supplier to restate their number against the normalised sheet and watch how they handle the question.

Test scope before commitment

Discovery exists to narrow the cone before you sign for the build. A short, paid piece of work that produces a tested prototype and a revised mobile app development cost estimate converts arguments into evidence. It also tells you how a supplier thinks when the answer isn't obvious yet.

Evolved Ideas worked this way on Salurate, an at-home saliva testing service that needed an app to handle user data, talk to a central database, and alert clinicians. The team built the interface in React Native with a Laravel backend. They improved it iteratively against user feedback alongside the client's device developers. Drop-off during testing fell to under 5% from over 50%.

Nigel Clarke, CEO of Salurate and Morgan Innovation and Technology, described the partnership this way: "Diversification is key, and having a tech partner like Evolved, who we can rely on for expertise beyond our in-house capabilities, has been crucial in securing new business, entering new markets, and staying competitive." That combination of mobile front end and bespoke software on the backend is the same shape as a field-inspection app talking to an asset register.

Discuss the first release

Bring us the awkward parts: the device estate you inherited and the integration nobody wants to touch. We'll work through the interfaces and what genuinely belongs in release one before anyone writes a number down. Talk to Evolved Ideas about a 30-minute discovery call, and we'll help you build a mobile app development cost model you can defend line by line.

Ready to bring your ideas to life?

Book a free 30-minute discovery call with our team — we'll understand your objectives and advise how bespoke software, MVP development, or an extended team can help your business.

Treat VAT as a separate cash requirement from the delivery estimate. Ask each supplier whether its rates and quoted totals include VAT, then record the tax treatment beside the quote. Keep VAT outside the mobile app development cost model if your organisation can reclaim it.

Record the integration owner's responsibilities, release dates, test access, and support contacts before development starts. Add a contingency line for delayed specifications or changed endpoints. If the interface isn't ready, use agreed mock data so the mobile team can continue without hiding the dependency.

Rebuild each quote against the same workstream sheet before comparing totals. Check for device testing, administration tools, accessibility checks, data migration, release support, and customer-owned tasks. A lower figure is meaningful only when the scope, assumptions, exclusions, rates, and acceptance criteria match.

Yes, the client needs to assign people who can approve designs, explain operational rules, supply test data, and accept completed work. Put those days on the delivery plan by role and week. If you want help defining that commitment, contact [Evolved Ideas](https://evolved-ideas.com/contact-us).

Use a prototype before approving the full build when workflows, device conditions, or integration assumptions remain unclear. Test it with representative users, record the changes, and revise the estimate afterward. This reduces disagreements because stakeholders approve observable behaviour rather than interpreting feature names differently.

Schedule a Discovery Call

Book a free 30-minute call that works for you

You Might Also Like

Discover more insights and articles

A close-up of hands writing on documents at a wooden desk, surrounded by colorful post-it notes and a softly glowing laptop.

Membership website development: connecting members, events and CRM

An association’s public site and member portal often fail in the same way: they work on their own, but they no longer talk to the membership, payment, and event systems around them. Replacing either one is easier to commission when you start from seven requirements. Use them to set the scope first, then organise procurement around them, so every supplier responds to the same brief and the integration problems that prompted the replacement stay at the centre of the decision.

A focused programmer types on a laptop at a sleek black desk in a modern office, surrounded by multiple monitors displaying code.

Software intellectual property: 7 ownership questions before you sign

Paying for bespoke software does not automatically mean you own it, and the gaps usually surface when the relationship ends. Before you sign, settle seven questions about software intellectual property with your development partner and with qualified legal counsel. They establish what transfers to you, and what you need in practice to keep the system running if the partnership ends, such as source code, documentation, and access to the environments it runs in.

A person examines software development documents at a metallic desk, surrounded by a softly blurred office in warm natural light.

Fixed price vs time and materials for a software development project

Fixed price feels safe and time and materials feels flexible, but neither tells you what you’re committed to when the brief changes. Compare three ways to buy bespoke software: fixed price, time and materials, and a sequence of capped phases. For each, see what it commits you to and how an unplanned requirement plays out in practice. Then settle a short list of questions before you sign anything, while you can still change the terms.

A business professional focused on coding at a sleek black desk in a modern office with natural lighting and an exposed brick wall.

5 .NET development companies for established applications

Choosing a firm to look after an established, business-critical .NET application is a risk decision, and the case studies on a supplier’s website rarely settle it. Five companies that work on this kind of system are reviewed here against their published case evidence, so you can see what each one has demonstrably done. A set of due-diligence questions and a controlled trial brief then let you test any of them, including firms not on the list, before you hand over the application.