Stop Building Native Apps for Small Businesses — You're Wasting Their Money

I'm going to say something that will probably annoy a few mobile developers.

Most small and mid-sized businesses do not need a native app. And the people convincing them they do are either uninformed or have a billing incentive to keep them confused.

I've seen this play out too many times. A business owner gets excited about "having an app." They spend $30–80k on iOS and Android development. Six months later, their app has 200 downloads, a 2.1 star rating because nobody wanted to install it in the first place, and a maintenance bill they didn't budget for.

This isn't a failure of execution. It's a failure of the right question not being asked upfront.

The Question Nobody Asks

Before any mobile discussion, someone should ask:

Why does this need to be native?

Not "what features do you need" — that comes later. First: why native specifically?

The honest answers that justify native are actually pretty narrow:

You need Bluetooth, NFC, or deep hardware access
You're building a game with complex rendering
You need background processing that runs independently of the browser
Your users are offline 80% of the time with zero connectivity (not just spotty)

For most SME use cases — field service tools, customer portals, internal dashboards, loyalty programs, booking systems — none of these apply.

What SMEs Actually Need From "An App"

When you dig into what a business owner means when they say "I want an app", it usually comes down to:

Works on mobile, looks good, feels fast
Users can access it without opening a browser every time
Sends notifications when something happens
Works even when internet is slow or drops

That's it. That's the whole list.

Every single one of those is solvable without the App Store.

The Hidden Costs Nobody Mentions

Native development has costs that don't show up in the initial quote.

Two codebases. iOS and Android are different languages, different paradigms, different release cycles. You're either paying for two teams or accepting that one platform will always lag behind.

App Store dependency. Apple can reject your update. A policy change can affect your app overnight. Your release schedule is now partially controlled by a third party.

Update friction. Every time you fix a bug or ship a feature, users have to update. Some won't. Now you're supporting multiple versions in production.

Ongoing maintenance. OS updates break things. Each new iOS or Android version requires testing and often code changes — whether you shipped new features or not.

A web-based solution has none of these constraints. You deploy once. Everyone gets the update instantly. No review process. No two codebases.

"But PWAs Aren't Real Apps"

This one comes up every time.

In 2019, that was a fair criticism. In 2026, it's just not accurate anymore.

PWAs can be installed on the home screen on both iOS and Android. They send push notifications. They work offline with proper caching. They load fast on slow connections. They pass through app stores if you actually need that distribution channel.

The gap between a well-built PWA and a native app — for the majority of business use cases — is negligible to the end user.

What is not negligible is the cost difference and the time to ship.

The Actual Cases Where Native Makes Sense

I want to be clear — I'm not saying native is always wrong. There are legitimate use cases:

Consumer apps where offline hardware access is central to the product (fitness trackers, AR tools, music production)
Apps targeting platforms where PWA support is still limited
High-frequency trading or real-time systems where milliseconds matter
Products where App Store discoverability is a core acquisition channel

If your use case is genuinely in this list, build native. It's the right call.

But if you're a logistics company that needs field workers to log deliveries, or a clinic that needs patients to book appointments, or a retailer that wants a loyalty card on their customer's phone — you do not need to spend six figures on a native app.

Why This Keeps Happening

Developers like building native apps. The work is interesting, the billing is higher, and clients don't know enough to question it.

That's not malicious — it's just the natural result of an information gap. When someone doesn't know the alternative exists and performs comparably, they default to what they've heard of.

The problem is that nobody in the room has an incentive to close that gap.