What does it cost to build an app? An honest answer

It is the first question almost everyone asks us, usually before we have even finished saying hello: what does it cost to build an app? It is a fair question. It is also one I cannot answer in a single number, which I know is annoying. "It depends" is the most honest reply, and also the most useless one. So let me do better than that and walk you through what it actually depends on.

Think of it like asking what a house costs. A studio flat and a five-bedroom place with a sea view are both "a house," and the price tag is not even in the same postcode. An app is the same. So instead of a number, let me hand you the things that move the number — so you can guess your own.

What you are really paying for

Most of the cost of an app is not the app. It is the thinking. Working out what to build, what to leave out, how the screens connect, what happens when someone taps the wrong thing — that is the slow, careful part, and it is where good apps are won or lost. The code is almost the easy bit by comparison. So when you pay for an app, you are mostly paying for time and judgement, not lines of code.

That is also why the cheapest quote is rarely the cheapest app. An app built without that thinking tends to come back to you later — as bugs, as confused users, as a rebuild. You pay either way. You just choose when.

The things that move the price

A handful of choices do most of the work on your budget. How many features you really need on day one — and how brave you are about cutting the rest. Whether it is one platform or both iPhone and Android. Whether it needs accounts, payments, or a backend keeping everyone's data in sync. Whether the design is clean and standard, or something more custom that needs real craft. And whether you have a clear idea or you are still figuring it out as you go, which is fine, but it does cost more to build and discover at the same time.

None of these are right or wrong. They are dials. The point is that every one of them is yours to turn, and turning them is how you steer the cost long before anyone writes code.

So, ballpark?

Okay, I will not dodge it completely. A small, focused first version — one platform, a tight set of features, sensible design — is a different world from a polished product on both platforms with accounts, payments and the works. The gap between those two is large, and most projects land somewhere along that line depending on the dials above. Any studio that gives you a firm price before they understand your idea is guessing, and you should treat that number with a pinch of salt.

How to spend it well

The best money-saver we know is not a discount. It is starting small. Build the smallest version that does one thing people genuinely want, put it in real hands, and learn. Almost everything you were sure you needed turns out to matter less than you thought, and one thing you forgot turns out to matter most. Spending a little to find that out is far cheaper than spending a lot to build the wrong thing beautifully.

So if you are sitting with an idea and a vague worry about the cost, that is the right instinct — and the right next step is a proper chat, not a price list. Tell us what you want to build and we will give you an honest read on what it takes. No brochure, no scary number pulled from thin air. Just coffee and a straight answer. Hej, and thanks for reading.