--- title: "Mobile App Development Cost: A Worked Budget" canonical: https://wavect.io/software-development-guide/mobile-app-development-cost/ language: en description: "Budget the complete mobile product: discovery, design, app, backend, device testing, store release and ongoing operation. This worked EUR example separates …" image: "https://wavect.io/img/general/bak/open_graph_preview.jpg" --- Mobile budget guide # How much should you budget for a mobile app? Budget the complete mobile product: discovery, design, app, backend, device testing, store release and ongoing operation. This worked EUR example separates assumptions from a quote and shows where offline behavior and platform differences change the estimate. Published: 2026-11-03 by Wavect Short answer A mobile app budget is the cost of accepted user journeys across the app, backend, devices and release process, plus ongoing operation. A shared codebase can reduce duplicated implementation, but it does not remove platform testing, native integration or store submission work. Best for - Buyers comparing mobile proposals with different inclusions - Teams deciding between mobile web, a shared app and native implementations Outside this guide - A market-price benchmark or a Wavect fixed-price offer - Medical, banking or hardware scope priced without specialist assessment // 01 ## Compare the options Compare the same accepted journey, device matrix and backend scope in every proposal. | Decision | Mobile web / PWA | Shared mobile app | Separate native apps | | --- | --- | --- | --- | | Delivery | Browser deployment; verify device capabilities | Shared implementation plus native integrations | Platform-specific implementation and releases | | QA | Browser and device behavior | iOS and Android, including plugin behavior | Each platform and supported OS/device set | | Offline | Design storage, retry and conflict behavior | Design storage, retry and conflict behavior | Design storage, retry and conflict behavior | | Best reason to choose | The browser meets the actual user journey | Shared product behavior with validated native needs | Platform-specific capabilities justify separate work | // 02 ## Where Wavect lands on this ### Price one usable journey before counting screens Consider a hypothetical field-service pilot: a worker signs in, opens assigned jobs, records a form offline and submits it when connectivity returns. An operator reviews the result in a small web administration view. The estimate includes iOS and Android, an existing identity provider, one backend integration and agreed accessibility checks. Payments, a scheduling optimizer, new hardware and regulated clinical decisions are excluded. This is an estimating exercise, not a shipped client project. A five-screen app can hide expensive permission rules, conflict resolution and unreliable upstream systems. Write acceptance examples first: a worker cannot see another team’s jobs; closing and reopening the app preserves an unsent form; a retry does not create two records. Ask each supplier to state which of these behaviors their price covers. [Android’s offline-first architecture guidance](https://developer.android.com/topic/architecture/data-layer/offline-first) explains why connectivity affects the data layer, rather than being a checkbox added after the screens. ### A transparent example in EUR Assume 44 person-days at EUR 900 per day: EUR 39,600. Add an illustrative 20% delivery reserve of EUR 7,920, giving EUR 47,520 for the initial build. Both the rate and reserve are assumptions, not Wavect prices or market averages. The phase table below shows the 44 days. Person-days are effort, not elapsed calendar days; parallel work, client decisions and store review change the schedule. For the first 12 operating months, assume EUR 300 per month for hosting and tools (EUR 3,600) and two maintenance days per month at the same illustrative rate (EUR 21,600). Initial build plus these operating assumptions totals EUR 72,720, excluding VAT. Store-program fees, paid third-party services, transaction charges, content production and new features are excluded and need separate lines. The reserve covers delivery uncertainty, not a second maintenance allowance. [Download the assumptions and arithmetic](/downloads/mobile-app-budget-example.json) and replace them with your own quote inputs. ### What changes the mobile estimate? Offline writes require decisions about local storage, identity expiry, retries and conflicting edits. A read-only cache is a different scope from submitting a legally significant record. Device hardware, Bluetooth accessories, background activity and camera behavior need a prototype on target devices before a supplier promises broad compatibility. A shared framework is not two finished apps for the price of one. [React Native documents platform-specific code](https://reactnative.dev/docs/platform-specific-code), while [Flutter describes its platform integration layers](https://docs.flutter.dev/resources/architectural-overview). Use those boundaries to ask what must remain native, which dependencies need maintenance and who can reproduce the release. The [React Native versus Flutter comparison](/blog/react-native-vs-flutter-dach-hiring/) addresses stack selection; this guide addresses what a budget must include. ### Test the release, not only the demo Agree physical devices, OS versions, screen-reader journeys, slow connections, interrupted uploads and expired sessions. Test the signed release build as well as development builds. Include permission refusal, background/resume behavior and account removal where applicable. Record defects by user impact and agree the blocking threshold before launch. A green automated suite does not demonstrate every device or accessibility behavior. Assign ownership of developer accounts, certificates, signing keys, privacy declarations and release notes. [Apple’s review guidelines](https://developer.apple.com/app-store/review/guidelines/) are a primary reference for the submission process and requirements. A development completion date is not an approval guarantee. Budget review-response work explicitly and distinguish a supplier defect from a later policy or product change. ### Compare proposals on equal terms Request a scope table with included journeys, excluded functions, accepted devices, dependencies, test evidence, client responsibilities and post-release support. For each uncertainty, name the experiment that would resolve it and the decision date. Do not conceal a missing integration behind an unexplained contingency percentage. If the API is undocumented, a small integration probe may be more valuable than another polished screen. After launch, plan OS and dependency updates, monitoring, incident response, restore procedures and a repeatable store release. Ongoing feature development is separate from keeping an accepted version working. Ask what happens if you stop the engagement: repository access, accounts, build instructions, data export and an owner for outstanding incidents should already be clear. [Mobile App Development](/services/mobile-apps/) owns a commissioned app; [Software Discovery](/services/software-discovery/) can define the scope before procurement. Illustrative effort allocation. Every amount is an assumption, not a quote. | Work package | Person-days | At EUR 900/day | | --- | --- | --- | | Discovery and acceptance scope | 4 | EUR 3600 | | UX and accessible interaction states | 5 | EUR 4500 | | Shared mobile implementation | 14 | EUR 12600 | | Backend and administration | 8 | EUR 7200 | | Device QA and failure cases | 8 | EUR 7200 | | Store release and handover | 5 | EUR 4500 | // 03 ## Cost, risk and timeline Build assumption EUR 47,520 44 days at EUR 900, plus 20% reserve 12-month operation assumption EUR 25,200 Hosting/tools plus planned maintenance Combined example EUR 72,720 Excludes VAT and the separately listed items // 04 ## Where this usually goes wrong - Comparing a frontend-only quote with a complete app and backend - Treating framework reuse as evidence that device QA can be removed - Buying screens without acceptance for retries, access control and offline writes - Confusing initial reserve, maintenance and new-feature budgets // 05 ## The checklist Before requesting a binding proposal, give every bidder the same brief. 1. Name one user, one job and the complete accepted journey 2. List integrations, data owners and the API assumptions to verify 3. Specify target platforms, devices, OS versions and accessibility tasks 4. Describe offline reads, writes, conflict and retry behavior separately 5. Request design, backend, QA, release and handover as explicit budget lines 6. Name the store-account owner and submission-response responsibility 7. Separate build reserve, operating cost, maintenance and future features 8. Agree acceptance evidence and the decision-maker who signs it off // 06 ## What this looks like in our work Offlinery documents a React Native and Expo mobile product, including iOS/Android releases and background location. The product wound down in 2025. This is delivery evidence, not proof of the hypothetical field-service scope, rate or budget above. ### [Offlinery](/case-studies/offlinery/) - **Status:** Wind Down - **Outcome:** Real-time - Proprietary Matching Engine - **Summary:** Proprietary real-time proximity matching on iOS/Android against aggressive OS throttling, full stack. - **Stack:** React Native / Expo, NestJS, TypeORM These are selected projects, not our full portfolio. We have shipped 100+ products since 2018. // 07 ## Related services & reading - [SERVICE Mobile App Development](/services/mobile-apps/) - [SERVICE Software Discovery and Requirements](/services/software-discovery/) - [GUIDE Software QA checklist before launch](/software-development-guide/software-qa-checklist-before-launch/) - [GUIDE Software development cost in Austria](/software-development-guide/software-development-cost-austria/) - [CASE STUDY Offlinery](/case-studies/offlinery/) // 08 ## FAQs ### How much does a mobile app cost in Austria? There is no defensible single price without scope. This hypothetical budget totals EUR 47,520 for an initial build and EUR 72,720 including stated first-year operating assumptions. These are transparent planning inputs, not Austrian market averages or a Wavect offer. Replace the effort, rate and exclusions before using them for procurement. ### Is React Native or Flutter always cheaper than native development? No. Reuse can reduce duplicated implementation, while native modules, device requirements, upgrades and testing can consume the difference. Compare the same accepted product, platforms and maintenance period. Validate high-risk integrations before assuming a saving. ### Should backend and maintenance be included in the app quote? They should be explicit. A mobile interface may depend on identity, business rules, administration, hosting and monitoring. Separate initial backend work from recurring operation and maintenance, and state whether post-launch feature changes are excluded. ### Can a PWA replace a mobile app? Sometimes. Test the actual journey on the intended devices, including installation, offline behavior, permissions and notifications. Choose mobile web when those capabilities suffice; choose a store-distributed or native implementation when a verified requirement justifies its additional delivery and release responsibilities. ## Structured Data ```json { "@context": "https://schema.org", "@graph": [ { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ], "employee": [ { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } } ], "founder": [ { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } } ], "legalRepresentative": [ { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } } ], "name": "Wavect GmbH", "subjectOf": { "@id": "https://wavect.io/verified-claims.json#dataset", "@type": "Dataset", "creator": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "description": "A machine-readable registry of quantitative and qualitative claims published by Wavect, with review dates, localized page appearances and public third-party citations where available.", "inLanguage": "en", "isAccessibleForFree": true, "license": "https://creativecommons.org/licenses/by/4.0/", "name": "Wavect verified publication claims", "url": "https://wavect.io/verified-claims.json" }, "url": "https://wavect.io/" }, { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "sameAs": [ "https://www.wikidata.org/wiki/Q139796365", "https://www.linkedin.com/in/wsdt", "https://github.com/wsdt" ], "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "sameAs": [ "https://www.wikidata.org/wiki/Q139796367", "https://www.linkedin.com/in/jocr77/", "https://github.com/jo-chris" ], "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/#website", "@type": "WebSite", "inLanguage": [ "en", "de", "es", "zh" ], "name": "Wavect", "potentialAction": { "@type": "SearchAction", "query-input": "required name=search_term_string", "target": { "@type": "EntryPoint", "urlTemplate": "https://wavect.io/search/?q={search_term_string}" } }, "publisher": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "url": "https://wavect.io/" }, { "@id": "https://wavect.io/software-development-guide/mobile-app-development-cost/#webpage", "@type": "WebPage", "dateModified": "2026-11-04", "inLanguage": "en", "isPartOf": { "@id": "https://wavect.io/#website", "@type": "WebSite" }, "lastReviewed": "2026-11-04", "url": "https://wavect.io/software-development-guide/mobile-app-development-cost/" } ] } ``` ```json { "@context": "https://schema.org", "@graph": [ { "@id": "https://wavect.io/software-development-guide/mobile-app-development-cost/#article", "@type": "Article", "about": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "author": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "dateModified": "2026-11-04", "datePublished": "2026-11-03", "description": "Budget the complete mobile product: discovery, design, app, backend, device testing, store release and ongoing operation. This worked EUR example separates assumptions from a quote and shows where offline behavior and platform differences change the estimate.", "headline": "How much should you budget for a mobile app?", "inLanguage": "en", "isPartOf": { "@id": "https://wavect.io/#website", "@type": "WebSite" }, "mainEntityOfPage": "https://wavect.io/software-development-guide/mobile-app-development-cost/#webpage", "mentions": [ { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, { "@type": "Service", "name": "Mobile App Development", "url": "https://wavect.io/services/mobile-apps/" }, { "@type": "Service", "name": "Software Discovery and Requirements", "url": "https://wavect.io/services/software-discovery/" } ], "name": "How much should you budget for a mobile app?", "publisher": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "speakable": { "@type": "SpeakableSpecification", "cssSelector": [ ".cmp-hero__headline", ".cmp-hero__lead" ] }, "url": "https://wavect.io/software-development-guide/mobile-app-development-cost/" }, { "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "item": "https://wavect.io/", "name": "Home", "position": 1 }, { "@type": "ListItem", "item": "https://wavect.io/software-development-guide/", "name": "Software development guide", "position": 2 }, { "@type": "ListItem", "item": "https://wavect.io/software-development-guide/mobile-app-development-cost/", "name": "How much should you budget for a mobile app?", "position": 3 } ] } ] } ``` ```json { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "There is no defensible single price without scope. This hypothetical budget totals EUR 47,520 for an initial build and EUR 72,720 including stated first-year operating assumptions. These are transparent planning inputs, not Austrian market averages or a Wavect offer. Replace the effort, rate and exclusions before using them for procurement." }, "name": "How much does a mobile app cost in Austria?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "No. Reuse can reduce duplicated implementation, while native modules, device requirements, upgrades and testing can consume the difference. Compare the same accepted product, platforms and maintenance period. Validate high-risk integrations before assuming a saving." }, "name": "Is React Native or Flutter always cheaper than native development?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "They should be explicit. A mobile interface may depend on identity, business rules, administration, hosting and monitoring. Separate initial backend work from recurring operation and maintenance, and state whether post-launch feature changes are excluded." }, "name": "Should backend and maintenance be included in the app quote?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "Sometimes. Test the actual journey on the intended devices, including installation, offline behavior, permissions and notifications. Choose mobile web when those capabilities suffice; choose a store-distributed or native implementation when a verified requirement justifies its additional delivery and release responsibilities." }, "name": "Can a PWA replace a mobile app?" } ], "speakable": { "@type": "SpeakableSpecification", "cssSelector": [ ".faq-question", ".faq-answer" ] } } ```