Skip to main content

Cost Guide

What Decides the Cost of a Mobile App

Six things decide what a mobile app costs: the platforms you ship to, the features inside it, the backend behind it, how custom the design is, the hardware it uses on the phone and the store, support and release work after launch. Features and the backend move the number most.

We don’t publish prices because no two apps need the same work. This guide explains what pushes the cost up or down, how Flutter and React Native compare, what the wider market charges and what to send us for an accurate quote. Quotes are free and come in writing after a scoping call.

By Zubin Souza, Founder & CEO
Last reviewed

The Six Things That Decide the Cost

These apply to a field app for your staff, a dealer ordering app and an app your customers download. Each one adds design, build and testing time, on every platform you ship to.

  • Platforms: Android, iOS or both

    One codebase in Flutter or React Native serves both stores and is the usual choice. Even then, each platform needs its own testing, store listing and release. Native Kotlin or Swift costs more and is worth it when the app leans hard on the device.

  • Features: what people do in it

    Sign-in, roles and permissions, search, chat, notifications, payments, maps and live tracking, offline use and reports. Every screen is designed, built, tested on real devices and then maintained.

  • The backend behind it

    An app is usually the small half. The APIs, database, admin panel and integrations with your ERP, CRM or payment gateway are often more work than the screens people see.

  • Design: patterns or your own

    An interface built from the platforms’ own patterns is quicker and more familiar to users. A custom design system with its own motion and illustration takes a designer and more build time, which is worth it for a consumer brand.

  • What it uses on the phone

    Camera, GPS and background location, Bluetooth, biometrics, offline storage and push notifications each bring permissions, battery questions and device testing. Background location and offline sync are the two that surprise people most.

  • Stores, support and releases

    App Store and Play Store review, privacy declarations, crash reporting and a release every time Apple or Google change the rules. An app is never finished the way a website can be.

Flutter or React Native

We build in both and pick per project, not per fashion. Either one gives you a single codebase for Android and iOS, which is why most business apps should use one of them rather than two native builds. The choice rarely changes the cost much; it changes who can maintain the app afterwards.

Flutter compared with React Native for a business app
FlutterReact Native
LanguageDart, learned for FlutterTypeScript, the same language as your website or web app
Picks itself whenThe design is custom and has to look identical on both platformsYou already have a React web team or want to share code with the web
Look and feelDraws its own interface so it is pixel-identical everywhereUses the platforms’ own components so it feels native on each
Hiring and handoverA smaller pool, though a strong oneAnyone who knows React can read it, which makes handover easier

What Changes the Cost of Each Kind of App

What adds cost and what keeps it down, by kind of app
Kind of appWhat adds the most costWhat keeps it down
Internal app for your staffOffline use, barcode or camera scanning, background location and an admin panel for every ruleOne role and one workflow in the first release, with the admin screens kept plain
Dealer or B2B ordering appPrices and discounts per customer, credit limits, approvals and a two-way sync with your ERPA ready-made ordering platform when your process is standard, rather than a custom build
Customer app for a consumer brandA custom design, payments, loyalty, notifications and the polish a public app store listing needsA first release around the one thing customers actually open the app for
Marketplace or multi-sided appTwo or three apps in one: buyers, sellers and operations, plus payouts and support toolsLaunching one side of the marketplace first, with the other handled manually at the start

How Long a Mobile App Takes

Time is the biggest part of the cost so the timeline is a good guide to the size of the bill. These are typical for our projects and the scoping call turns them into a dated plan for yours.

Typical timelines for mobile apps
ProjectTypical timelineWhat drives it
First release of a cross-platform app8–12 weeks or moreThe number of features and roles and how much backend has to be built with it
App on top of a backend that already existsSooner, once the APIs are readyHow complete and how well documented those APIs are
Dealer ordering on ZunderFlow instead of a custom appLive in 72 hoursYour customer list, your price lists and the connection to your ERP or accounting software
Native Android and iOS builds instead of one codebaseLonger than a single codebaseTwo builds, two sets of tests and two release processes

What It Costs to Run After Launch

  • Developer accounts

    Apple charges a yearly fee for its developer programme and Google a one-off fee, each billed by the store.

  • Backend and services

    Hosting, the database, file storage, push notifications, maps, SMS and payment gateway fees, each billed by its provider.

  • Keeping up with the platforms

    Android and iOS release a new version every year and both stores change their rules. An app that isn’t updated eventually stops being accepted or stops working.

  • New features and support

    Crash reports, user questions and the features people ask for once they’re using it. Budget for this from the start.

Ways to Keep the Cost Down

  • One codebase, both stores

    Unless the app leans hard on the device, Flutter or React Native halves the build and the testing.

  • Ship the one workflow that matters

    Pick the thing people will open the app for, launch that and let real usage decide the rest.

  • Reuse the backend you have

    If your web app or ERP already has APIs, the app can use them instead of paying for a second system.

  • Say no to offline until you need it

    Offline use and background sync are among the most expensive features to build and test. Add them when a real user is losing work without them.

How to Get an Accurate Quote

We quote each app in writing after a scoping call. Quotes are free. The more of this you can tell us, the closer the quote gets to the final bill.

  • Who will use it

    Your staff, your dealers or the public and roughly how many of each.

  • The main workflows

    What someone opens the app to do, from signing in to getting the result. A sketch or a list is enough.

  • Android, iOS or both

    And whether the people using it are on company phones or their own.

  • What exists already

    A backend with APIs, a web app, designs or an older app we’d be replacing.

  • What it uses on the phone

    Camera, location, Bluetooth, offline use or notifications.

  • Your deadline and the reason for it

    A season, a trade show or a funding round changes how we plan the first release.

What the Market Charges for Mobile App Development

Market data, not our prices. We quote every project on its own scope.

Buyers ask for a number before they ask for a quote so here is published market data from Clutch, the business directory where clients review the firms they hired. These are other firms’ figures, not ours. Read them as the range your quotes are likely to sit in, then judge any quote on scope rather than on the rate.

Market figures for app development firms, as published by Clutch
FigureWhat Clutch reportsHow to read it
Where most projects landBetween US$10,000 and US$49,999The band most app projects reviewed on Clutch fall into. Start here, not at the average
Average project costUS$90,780, over an average of about 11 monthsLarge, long-running platforms pull the average well above a typical first release
Most common hourly rateUS$25 to US$49 an hour for Android, iOS and cross-platform work alikeThe same band for all three so the platform is not what moves the rate
Firms in IndiaUnder US$25 an hour on averageLower than every other country Clutch lists a figure for

Source: Clutch, App development pricing guide, published . We last checked it on .

Client results

Produpak

  • +30%revenue
  • 60%faster order-to-delivery

Apps are judged on what they change in the business. The ordering apps we built for Produpak, a fruit and vegetable wholesaler, grew its revenue 30% and cut order-to-delivery time by 60% in under 90 days.

What Produpak’s ordering apps changed

Frequently Asked Questions

It depends on the six things in this guide and the features and the backend move the number most. We don’t publish prices because no two apps need the same work. Tell us what you need and we’ll send a written quote after a scoping call. Quotes are free.

Both give you one codebase for Android and iOS. Flutter suits a custom design that must look identical on both platforms. React Native suits teams that already work in React and TypeScript and makes handover easier. We build in both and recommend one after looking at your design and your team.

Usually, yes, because one codebase replaces two builds and two sets of tests. Native Kotlin or Swift is worth the extra when the app leans hard on the device, such as heavy camera or Bluetooth work or needs the newest platform features the day they ship.

The first release of a cross-platform app typically takes 8–12 weeks or more, depending on its features and how much backend has to be built with it. An app on top of APIs that already exist is quicker. Dealer ordering on ZunderFlow can be live in 72 hours.

Almost always. Accounts, data, notifications, reporting and integrations live on a server, not on the phone. If your web app or ERP already has APIs, the app can use those instead, which takes a large piece out of the quote.

Offline use, background location, a second user role added halfway through and a backend that turns out to need building too. We map the workflows, the roles and the integrations before we quote, which takes most of the guesswork out.

Apple and Google developer accounts, the backend and the services it uses such as notifications, maps and payments, plus the updates each new Android and iOS version needs. Ask for all three to be listed in any quote you get.

You do. Full ownership and the source code are handed over at launch and the apps are published under your own developer accounts.

Want a Quote for Your App?

Tell us who will use it, what they need to do and whether a backend already exists. We’ll set up a scoping call, then send a written quote.