The most expensive apps we’ve seen all started with a single sentence: “we want to be in the App Store.” Not because anyone needed one, but because the competition has one and it looks grown-up. Half a year and a small fortune later, there’s an app sitting in the store that a handful of people download, open once, and never come back to. Before you dive in, it’s worth answering one question honestly: does an app actually solve your problem, or would a plain website solve it better for a fraction of the cost?

App, mobile website, or PWA? What’s the actual difference

People lump “an app” and “a website on your phone” together, when really they’re three different things with completely different price tags and capabilities.

Responsive website. A normal site that adapts to a small screen. You open it in a browser, nothing gets installed. For most businesses this is a perfectly sufficient solution. If someone shows up, finds the information or buys something, and moves on, a website is enough.
PWA (Progressive Web App). Still a website, just smarter. You can add it to your home screen, it can run without a signal, and on plenty of devices it even handles push notifications. It feels almost like an app, but you skip the stores and the two platforms. A great middle step when you want the “app” feel without the full price.
Native app. The thing you download from the App Store or Google Play that installs onto your phone. It has access to everything: camera, GPS, sensors, full performance. It’s also by far the most expensive to build and run.

The rule to follow: start with a website and move up to an app only once the website demonstrably isn’t enough. Not the other way around.

When an app genuinely makes sense

An app pays off when it does something a browser simply can’t, or can only do noticeably worse. Look for at least one of these reasons, ideally several:

People use it often and repeatedly. A bank, public transit, a fitness log, something you open every day. An icon on the home screen only makes sense for things you keep coming back to.
You need push notifications as the core of the service. Food delivery, package tracking, alerts from a smart home. Careful, though: websites and PWAs handle notifications these days too, so the notification alone doesn’t justify an app.
It has to work offline. Maps in the mountains, a field notebook for technicians, an app for the plane.
You touch the hardware. A camera for scanning documents, GPS for navigation, a step counter, NFC payments. This is where the web hits a ceiling.
Real performance matters. Games, photo editors, smooth work with large volumes of data.
Loyalty and payments in your pocket. A coffee shop with stamps, a store where the same people keep buying. An app saves them steps and keeps the customer closer to you.

When an app is money down the drain

Let’s be honest, because the people selling apps won’t tell you this. In a lot of cases an app is just an expensive way to do what a website does better and cheaper.

A one-off or rarely used service. An app for a booking someone makes twice a year? Nobody keeps it on their phone. A website with a form does the job better.
Mostly information. Opening hours, menu, pricing, contact. That belongs on a website that Google can find. Nobody installs an app to read a menu.
“We want to be in the App Store” as a status symbol. Being in the store isn’t a goal, it’s a cost. An empty app with ten downloads tends to chip away at trust rather than build it.
A website does the job cheaper. If you can’t write down a single reason from the paragraph above, the answer is probably no. And that’s fine, put the money you saved into a good website and marketing instead.

Try this trick: if your app could only ever live as a website, would you lose anything essential? If not, you don’t need an app yet.

An app needs one main job

Before we even add up the costs, here’s the one thing that decides whether an app catches on: it has to do one thing, and do it best. Order a coffee. Track a package. Log a workout. An app that tries to do everything does nothing well, and people delete it after a few days.

That single job also helps you decide whether you need an app at all: if you can name it in one sentence and it genuinely requires a phone, you’re on the right track. How to whittle that idea down to a first version worth shipping is what we’ll dig into in the lesson on the path from idea to MVP.

The reality of cost: an app isn’t one thing

This is the most common place where budgets fall apart. “An app” sounds like one line item, but you’re actually paying for several at once.

Two platforms. iOS and Android are two different worlds. Either you build twice (natively) or you go cross-platform and sacrifice something. That’s what the whole next lesson is about; for now just know that “the phone” isn’t one door, it’s two.
Backend. Most apps don’t get far without a server, a database, and logins. That’s a separate project hidden inside the first one.
Store fees. An Apple developer account costs a yearly fee, Google’s is a one-time fee. And on payments made inside the app, the stores take a cut, typically in the low tens of percent. Factor this into your business plan from day one.
Updates forever. Apple and Google change their rules and OS versions every year. An app you don’t update for a year will one day simply stop working or vanish from the store. Maintenance isn’t optional, it’s a permanent cost.

Bottom line: an app is a commitment for years, not a one-time project. Count on running and maintaining it costing you well after it’s “done.”

Fill in the blank with one sentence: “Our app will be used by (who) (how often) to (do what), and it can’t be done without a phone because (camera / offline / notifications / payments…).” If you can’t fill in that last bracket honestly, save yourself a fortune and build a website.

If this lesson left you sure you really do want an app, great. In the next lesson we’ll look at the first big fork in the road: building natively or cross-platform, and what you gain and lose either way.