Mobile app development cost: what sets the number
How many platforms. iOS and Android are two audiences, two review processes and, if you build natively, two codebases. Shipping one first is the single largest saving available, and which one depends entirely on where your customers actually are rather than on which phone the founder carries.
What the app holds. An app that displays things is small. An app where people have accounts, data that syncs, content that has to work with no signal, and payments moving through it, is four systems with a shared icon. Each of those is a decision that touches every screen.
What it touches on the device. Camera, location, Bluetooth, notifications, background activity, health or payment APIs. Each one adds build time, a permission flow, an explanation to the user and a paragraph in the store review. None of them are hard on their own; the fourth one is where a timeline stops being linear.
And how wrong it is allowed to be. A tool for forty staff who can be told to update is a different budget from something a stranger installs, distrusts, and deletes the first time it fails. Correctness costs, and on mobile the punishment for getting it wrong is a one-star review that outlives the bug.
Most businesses asking for an app need a website
An app has to be installed. That is not a detail, it is the whole economics: a website costs a visitor one tap from a search result, and an app costs them a decision, a store visit, a download and a permission dialogue before they have received anything at all.
So the honest first question is not what the app will do. It is how often the same person will come back. Apps earn their install through repeat use, and something a customer needs four times a year is a website that person already knows how to reach.
The cases where an app genuinely wins are consistent: frequent repeat use, work that has to continue with no signal, real hardware access, notifications as a channel you have actually earned, or a logged-in relationship that is the product rather than a feature of it.
Everything else — a catalogue, a booking, a quote, a portal people visit occasionally — is a website's job, and it reaches everyone rather than the fraction who installed something.
Native or cross-platform
Cross-platform — one codebase running on both — covers the large majority of business apps and roughly halves the build. Forms, lists, accounts, payments, maps and notifications are all solved territory, and the result is indistinguishable to a user who is not looking for the seam.
Native, two codebases, is worth it when the app is doing something the device is doing: heavy graphics, camera or sensor work at the edge of what the hardware allows, deep integration with the operating system, or performance that is itself the product.
The trap is choosing native for prestige. Two codebases is not a better app, it is two of everything — two builds, two bugs, two release cycles — and that cost is paid every month for as long as the app exists.
The other trap is choosing cross-platform for a thing that was never an app. A wrapper around a website will be rejected by review, or accepted and then ignored by users, and both outcomes cost the same.
The cost that starts at launch
A website left alone keeps working. An app left alone stops. Apple and Google ship a major OS release every year, and an app that is not updated against them eventually breaks, gets flagged as outdated, or is removed from the store.
That makes maintenance non-optional rather than a nice-to-have, and it is the line most first-time buyers leave out of the business case entirely. Budget for it in the first year, not the second.
The store itself has a running cost: a developer account with each — Apple's is billed annually, Google's is a one-off — plus a review process that can and will reject a release for a reason nobody predicted, usually in the week you promised it.
And if anything digital is sold inside the app, the platform takes a commission on it, at a rate that depends on which programme you qualify for. It is a business-model decision, not a technical one, and it belongs in the spreadsheet before the first screen is drawn.
None of this is an argument against building. It is an argument for pricing the whole obligation, the same way an app's cost is set by its states rather than its screens.
PawSpot is the shape this question usually arrives in: a marketplace connecting breeders and buyers, with a community around it, which is the exact profile where somebody in the room will ask for an app. It is a website, and the reason is the first question in this post. Buying a puppy is not a weekly habit, and an install has to be repaid in visits that were never going to happen.
Questions we get asked
How much does it cost to make a mobile app?
A genuinely narrow cross-platform app — one kind of user, one job, no hardware beyond notifications — starts where a large website ends and goes up from there. Multiple user roles, offline sync, payments or real device access each move it materially. Any figure quoted before someone has asked how many platforms, what the app holds and what it touches on the device is a guess.
Should I build native or cross-platform?
Cross-platform for the large majority of business apps: one codebase, roughly half the build, and no difference a user will notice. Native when the app is doing something the device is doing — heavy graphics, sensor work, deep OS integration, or performance that is itself the product.
Do I need a mobile app or a mobile website?
Ask how often the same person will come back. An app has to be installed, which costs you most of your audience before they see anything. It earns that back only through repeat use, offline work, hardware access, notifications as a real channel, or a logged-in relationship. A catalogue, a booking or a quote is a website's job.
What are the ongoing costs of a mobile app?
Developer accounts with both stores, and mandatory maintenance. Both platforms ship a major OS release every year, so an app that is not updated eventually breaks or is removed. If you sell anything digital inside it, the store also takes a commission. Price the first year of upkeep alongside the build, not after it.