How much does it cost to make an app?

Asking what an app costs is like asking what a building costs. A garden shed and a hospital are both buildings, and if a contractor quoted you the same number for either without asking which one you meant, you'd walk away. Software is the same. The word "app" covers a five-minute utility and a live social network, and the price between them isn't double — it's an order of magnitude. So the useful first move isn't getting a quote. It's figuring out which app you're describing.

Most app ideas fall into one of five buckets. Find yours before you talk price, because it moves the number more than anything else on this page.

• Two platforms, not one. iPhone and Android are separate worlds. Building for both roughly doubles the surface you design, test, and maintain, unless you deliberately choose a cross-platform approach up front.
• The stores themselves. Publishing to Apple's App Store requires the Apple Developer Program at $99 a year; Google Play charges a one-time $25 registration. Both review your app before it goes live, and both can reject it — which is time you have to budget for.
• The invisible half — the backend. Anything with accounts, payments, or shared data needs servers running behind the app. That's a recurring bill and a maintenance job, not a one-time build.
• Staying alive. Phones and operating systems change every year. An app nobody updates slowly breaks. Maintenance isn't a nice-to-have; it's the cost of the app continuing to work at all.

One more lever sits underneath all of this: how polished it has to feel. The same idea can be a plain, functional app or a smooth, animated one that behaves like something from a big brand, and the second costs far more to design and build. Early on, functional usually wins — you're testing whether people want the thing, not whether the transitions are elegant. Save the polish for after they've told you it's worth it.

1. 1Name the single most important thing the app does. The one action a user takes that makes the whole thing worth building. Everything else is secondary.
2. 2Pick one platform for version one. Usually whichever your users actually carry. Doing one first cuts the build roughly in half and lets you learn before you double down.
3. 3Cut every feature that isn't needed to prove that one thing. The extras can wait until the core works.
4. 4Write each screen as a sentence. "A user opens the app, sees today's jobs, and taps one to mark it done." A page of these is a brief a builder can actually price.
5. 5Take that to two or three builders and compare what's included — testing, design, the backend, and support — not just the headline totals.

A lot of "app" ideas are really a mobile-friendly website in disguise. A website skips both platforms, skips the app stores, and skips the review process — which makes it cheaper and faster to put in front of real people. Build the actual app when you genuinely need the phone's hardware — the camera, GPS, offline use, or push notifications — or when the experience has to live as an icon on the home screen. If none of that is core to your idea, a website often does the same job for a fraction of the cost.

If you're not technical and can't yet tell which of the five you're describing, the honest first step is a short scoping conversation, not a build. Some people hire that out as a paid discovery; some bring in a partner who helps define the app and then builds it. Either way, a clear brief is what turns "how much does an app cost" into a number you can trust.