Do you need a mobile app?

A business owner tells us they want a mobile app roughly once a week. About half the time, after a short conversation, they realize they don’t: they want their website to work well on a phone, which is a different and much cheaper thing. Apps are expensive to build, expensive to maintain, and hard to get people to install. Before you spend on one, it’s worth asking whether you need it. Here’s the skeptic’s checklist we walk people through.

The uncomfortable fact about app installs

The biggest reason most businesses don’t need an app is brutally simple: getting people to install one is hard. People are stingy with their home screens. They install apps for things they use constantly, messaging, banking, the handful of services woven into daily life, and almost nothing else. Asking a customer to go to the App Store, search, download, and open an account, just to do something they’d happily do on your website, is a wall most of them won’t climb.

If you can’t articulate why someone would install your app and come back to it regularly, you don’t have an app idea yet. You have a website that needs to be good on mobile.

The questions that decide it

Ask yourself, honestly:

• Will people use this repeatedly? Apps justify themselves through frequent, habitual use. A thing people touch once or twice doesn’t earn a home-screen slot, it earns a good mobile web page.
• Does it need to work offline, or use the phone’s hardware? Camera, GPS, Bluetooth, offline access, notifications you need, these are real reasons to go beyond the web. If none apply, the web probably covers you.
• Is the experience impossible on a website? Modern mobile websites do a great deal, and progressive web apps can even be installed and work offline without the app-store overhead. Be honest about whether your idea genuinely exceeds what the web can do.
• Do you have a way to get people to install it? An app nobody installs is the most expensive kind of nothing. If you don’t have a real distribution plan, the build is the easy part of a problem you haven’t solved.

If you answered “no” or “not sure” to most of these, you probably want a great mobile website, not an app.

What people usually want

When we dig in, the underlying want is almost always one of these:

• “My site looks broken on phones.” That’s a responsive website problem, fixed for a fraction of an app’s cost.
• “I want to send notifications.” A progressive web app can do that without a native build.
• “I want to look modern/serious.” A fast, polished mobile website does that. An app you can’t get installed does the opposite.
• “Competitors have an app.” Maybe they’re getting value from it, or maybe they spent on one nobody uses. Don’t inherit someone else’s mistake.

Real app needs exist, repeated use, hardware integration, offline-critical workflows, app-store discovery as a genuine channel. But they’re rarer than the app-shaped enthusiasm suggests.

The honest recommendation

If you have a real, frequent, hardware-or-offline use case and a way to get people to install it, build the app, and build it well. If you mostly want to be excellent on a phone, build a fast mobile website (or a PWA), pocket the difference, and put it toward something that moves the needle.

We build mobile apps when they’re the right answer, and we’ll tell you plainly when they’re not, because we’d rather build you the right thing than sell you the expensive one. If you’re weighing an app, let’s pressure-test the idea first.