Most app quotes cover the screens you can see. The parts that make those screens work, such as servers, integrations, store accounts, test devices, and the update cycle that never stops, often show up later as change orders. A shipping iOS and Android MVP from an experienced team typically costs $30,000–$120,000. Here's what to add to that number so your budget survives the first year.
1. The backend nobody drew in the mockups
Unless your app only displays static content, it needs somewhere to store accounts, orders, and content, plus APIs to read and write them. That's a server, a database, an admin panel for your staff, and authentication. Sometimes this is as much work as the app itself. Ask every vendor whether the backend is in the quote, and whether it's custom code or a platform like Firebase or Supabase.
2. Integrations with the systems you already run
Connecting the app to your eCommerce platform, POS, ERP, CRM, or loyalty program is where estimates slip the most, because it depends on how good those systems' APIs are. When we built GET Nursery App, real-time sync of inventory, pricing, and orders across multiple physical locations was a core part of the work, not an add-on. Budget for it explicitly.
3. Developer accounts and store fees
Apple's developer program costs $99 per year, and a Google Play developer account is a one-time $25. Those are small. The larger cost is commission: apps that sell digital goods or subscriptions generally pay the stores a 15–30% commission, depending on program and region. Apps selling physical goods, such as a store or a nursery ordering app, use your normal payment processor and avoid it.
4. App Store review and rejections
Apple and Google both review submissions, and a rejection over a login flow, privacy disclosure, or account-deletion requirement can cost a week of rework. Budget time for at least one resubmission at launch, and keep your privacy labels and data-safety forms accurate. Changing them later can trigger another review.
5. Annual OS updates
New versions of iOS and Android come out every year, and they deprecate APIs, change permission prompts, and raise minimum SDK requirements. Google Play requires apps to target a recent Android API level to keep receiving updates. An app that nobody touches for 18 months is often an app that can't ship a bug fix without upgrade work first.
6. Third-party services billed monthly
- Push notifications (often free to start, but they need a provider and backend logic)
- Maps, geocoding, and address autocomplete
- SMS verification and transactional email
- Crash reporting and performance monitoring
- Search, image hosting, and CDN
Each is cheap on its own and they add up together. Get a list with expected monthly costs at your projected user count.
7. Cloud hosting that grows with usage
Server, database, file storage, and bandwidth costs grow with users and with how chatty the app is. A small business app might run tens of dollars a month. One with media uploads or real-time features can run hundreds or more. Ask for an estimate at launch volume and at 10× launch volume.
8. Real-device testing
Simulators miss problems that only show up on real phones: older devices with little memory, small screens, specific Android manufacturers' quirks, and poor network conditions. Budget for a device lab or a cloud device-testing service, and for QA time on every release, not only the first one.
9. Design for two platforms, three screen sizes, and accessibility
iOS and Android users expect different navigation patterns. Tablets, large text settings, dark mode, and screen readers all need to be considered. Cross-platform frameworks like React Native share most of the code (typically 30–40% cheaper than two native apps), but they don't remove the design and testing work for each platform.
10. Analytics, attribution, and the marketing launch
Downloads don't happen just because the app is live. Budget for store listing screenshots and copy, app store optimization, analytics events that show where users drop off, and the campaign that tells your existing customers the app exists. For businesses with an existing customer base, that last one matters most.
11. Ongoing maintenance and the feature roadmap
A common planning figure is 15–20% of the initial build cost per year for maintenance: OS updates, dependency upgrades, crash fixes, and small improvements. New features come on top of that. If the app is working, you'll have a roadmap. If it isn't, you'll want budget to fix it.
A realistic first-year budget
| Line item | Typical first-year cost |
|---|---|
| Design and build (iOS + Android MVP) | $30,000–$120,000 |
| Backend and admin, if not included | Often 25–50% of the app build |
| Integrations (eCommerce, ERP, POS) | $5,000–$40,000+ |
| Developer accounts | $99/yr Apple + $25 one-time Google |
| Hosting and third-party services | $50–$1,000+ per month |
| Maintenance after launch | 15–20% of build cost per year |
How to keep costs under control
- Start with a paid discovery. A few weeks of scoping turns guesses into a fixed-price build.
- Cut the MVP down. Launch with the one job customers need most, and let usage tell you what comes next.
- Consider a PWA first. If you don't need push notifications on iOS, offline mode, or hardware access, a progressive web app may be enough. See native app vs. web app.
- Reuse what you have. If your store already has a good API, the app can use it instead of a new backend.
Want a number for your app? Our app development team quotes fixed-scope after discovery, so the number in the proposal is the number you pay.