Does Your Business Actually Need a Mobile App?

Here's a question business owners ask us constantly: "Should we get an app?" My answer surprises most of them. In roughly nine out of ten cases, the honest answer is no. Not because apps are bad, but because what they actually need is a better website. Or possibly a Progressive Web App (PWA), which gives you most of the benefits without the eye-watering price tag.

Before you commit tens of thousands of pounds to native app development, let's get crystal clear on what you're actually choosing between and what each option genuinely delivers.

Native Apps vs PWAs: What's Actually Different

A native app is software built specifically for a mobile operating system. If you want to reach both iPhone and Android users, you're typically looking at two separate codebases written in different languages: Swift for iOS, Kotlin or Java for Android. These apps live on the device, live in the App Store or Google Play, and have direct access to the phone's hardware.

A Progressive Web App, on the other hand, is a website that behaves more like an app. It runs in a web browser but can be added to your home screen, work offline, and send push notifications. Crucially, it uses standard web technologies: HTML, CSS, and JavaScript. One codebase works everywhere.

The distinction matters more than most people realise. Because a PWA runs in a browser, it faces certain restrictions that native apps don't. But for the vast majority of business use cases, those restrictions are irrelevant.

The average user downloads zero new apps per month. Your customers already have your website. Do they really need another icon on their home screen?

App Store Distribution: The Hidden Costs Nobody Talks About

Native apps require distribution through the App Store or Google Play. This sounds simple until you factor in the reality.

Apple charges $99 per year for a developer account. Google charges a one-time $25 fee. But the real cost isn't the account fee, it's the submission process itself. Both stores have review guidelines that can delay your launch by weeks. Apple in particular is known for rejecting apps that don't meet their exacting standards, sometimes for reasons that have nothing to do with functionality.

Once your app is live, updates become a two-step process. You push code to your servers and separately submit an update to both stores, waiting for review each time. For a small business without a dedicated development team, this becomes a logistics nightmare.

PWAs completely bypass this pipeline. There's no App Store to submit to, no review process to wait through, and no developer account fees. You update your website and every user sees the new version instantly. This alone can save weeks of delay and hundreds of pounds in annual fees.

When App Store Presence Actually Matters

There are genuine scenarios where being in an app store provides real business value. If visibility in the Apple App Store or Google Play drives discoverability for your product, native makes sense. Some users specifically search stores rather than the web. App Store search can be a legitimate discovery channel.

However, for most businesses, the app store is a distribution channel you don't need. Your website already reaches anyone who wants to find you.

Capability Comparison: What Can Each Actually Do?

Capability	Native App	PWA	Mobile Website
Hardware access (camera, GPS, Bluetooth)	Full access	Limited access	Limited access
Push notifications	Yes, always works	Works on most devices	No
Offline functionality	Full	Partial (via service workers)	No
Background processing	Yes	No	No
Install on home screen	Automatic	User-initiated	No
App Store presence	Yes	No (but discoverable via web)	No

This table tells the real story. The only columns where native apps genuinely win are deep hardware integration and background processing. For everything else, a well-built PWA delivers 90% of the experience at a fraction of the cost.

Development Costs: The Numbers That Matter

Here's where the difference becomes stark. Let's look at realistic development costs for each approach.

These figures represent realistic budgets for a business-quality implementation, not bare-bones prototypes. A mobile website costs the least because it reuses existing web infrastructure. A PWA builds on that foundation but adds app-like features. A single-platform native app requires dedicated mobile development. And cross-platform native development doubles or triples your costs because you're essentially building the same thing twice.

But the initial build is only part of the picture. Annual maintenance costs tell an even starker story.

Native apps demand constant attention. iOS and Android release new operating system versions roughly annually, and your app needs to stay compatible. Bug fixes require separate submissions to both stores. Feature updates take longer to reach users. Over five years, the total cost of ownership for a native app can easily exceed £100,000 for a cross-platform build.

A PWA, by contrast, updates instantly and works across all devices. Your maintenance costs stay flat because you're maintaining one codebase, not two.

So What Does Your Business Actually Need?

Let's be specific about when each option makes sense.

You probably only need a mobile website if:

• Your primary goal is informational: hours, location, contact details, services
• Users don't need to log in or access personalized data
• You update content frequently and need changes to go live immediately
• Your budget is tight and you need the fastest path to mobile accessibility

A PWA makes sense if:

• You need app-like features: push notifications, home screen installation, offline access
• You want to reach users across all devices from a single codebase
• Your users are spread across iPhone and Android equally
• You value speed of iteration over deep hardware integration

Consider a native app only if:

• Your app requires intensive hardware access: advanced camera features, Bluetooth Low Energy, AR/VR
• Background processing is essential: fitness tracking, music playback, navigation
• You're building a gaming app or something graphically intensive
• Your business model depends on App Store discovery and you're prepared to invest accordingly

The Honest Answer

Most businesses we work with come to us thinking they need an app. After discussing their actual requirements, a solid PWA or an improved mobile website solves their problem at a fraction of the cost.

The mobile app industry has spent decades convincing businesses that they need native apps. The technology has caught up to a point where, for most use cases, that investment isn't necessary anymore. A well-designed PWA delivers the experience your users want without the maintenance burden you don't need.

If you're still unsure, ask yourself this: what exactly does my app need to do that my website can't? If you can't answer that question clearly, start with the website. Your bank balance will thank you.