Every few months a client asks me some version of: “Do we need a mobile app?” The honest answer is almost always one of three things — and rarely the one they were expecting.
This guide walks you through the same decision framework I use in client discovery calls. By the end you'll know whether you actually need a native app, whether a Progressive Web App (PWA) is the smarter starting point, or whether your existing responsive website is doing the job already.
The Quick Answer (For People In A Hurry)
Most UK SMEs don't need a native mobile app. A fast, well-built responsive website covers 80% of use cases at a fraction of the cost. A Progressive Web App (PWA) covers another 15%. Native apps are the right answer for the remaining 5% — but when they are, nothing else will do.
The three signals you actually need a native app: push notifications are core to your model, offline use is critical, or you need deep device features like camera, GPS, biometrics, or in-app purchases. If none of those apply, keep reading — there's probably a cheaper path.
What Each Option Actually Is
Responsive Website
Your standard website that adapts to phone, tablet, and desktop screens. Lives at a URL. Discovered through Google. No installation. Today this is what 95% of UK SMEs need.
Typical cost: £1,500 – £8,000 to build, £20 – £100/month hosting.
Timeline: 2 – 8 weeks.
Progressive Web App (PWA)
A website with extra superpowers: installable to the home screen, works offline, can send push notifications (with limitations on iOS), runs full-screen like a native app. Built on the same web tech as your website. Lives at a URL. Discovered through Google AND your home screen.
Typical cost: £3,000 – £15,000 to build (often added to an existing website), £30 – £150/month hosting.
Timeline: 4 – 10 weeks for a focused PWA.
Native Mobile App
A “real” iOS and Android app, distributed through the App Store and Google Play. Modern apps are typically built cross-platform with React Native or Flutter — one codebase, two platforms — which is roughly half the cost of building separate iOS and Android apps in Swift and Kotlin.
Typical cost: £8,000 – £40,000 to build, plus £150 – £500/month ongoing maintenance and OS update releases.
Timeline: 6 – 16 weeks for a focused MVP, plus 1 – 2 weeks for App Store and Google Play review.
The Decision Framework
Here are the questions I work through with clients. Yes answers point you toward native; no answers point you back toward web or PWA.
1. Are push notifications core to your business model?
By “core” I mean: if push notifications didn't work, your business model would meaningfully change. Examples where this is genuinely true: ride-hailing (drivers need real-time job alerts), delivery (couriers and customers need status updates), social apps (the whole point is interruption), live odds and betting, time-sensitive flash sales.
Push notifications on iOS via PWA exist (since 2023) but are limited — they only work after the user installs the PWA to their home screen, and reliability is patchier than native. If push is genuinely core, go native.
2. Do your users need to work offline?
Field workers in rural areas, hospitality staff in basement venues, delivery drivers in tunnels, anyone working on planes or trains. If “your app stops working without signal” is a deal-breaker, you need native (or a properly architected offline-first PWA, which is doable but harder than people think).
3. Do you need deep native device features?
Camera with custom processing (not just “upload a photo”), Bluetooth/NFC, biometric auth (Face ID, Touch ID), in-app purchases through Apple/Google billing, background location tracking, AR/VR. PWAs can do some of this; native handles all of it smoothly.
4. Will App Store presence drive trust or discovery?
For consumer-facing brands (especially DTC retail, fitness, health, finance), being on the App Store is a credibility signal. Customers expect serious brands to have apps. For B2B or service businesses, this matters far less — your customers find you through Google and referrals, not App Store search.
5. Is your usage frequent and habitual?
Native apps win when users open them daily. The home screen icon, the muscle memory, the push notifications — they all compound. For occasional use (booking a restaurant once a month, getting a quote, reading articles), users will tap your website link or search Google. They won't install your app — and if you make them, they'll abandon it.
Common UK Business Scenarios
Local Service Business (plumber, electrician, accountant)
Verdict: Responsive website. People find you via Google, book a callback, get a quote. They will never install your app. Save the £10,000+ for SEO and Google Ads instead.
Independent Retailer or Boutique
Verdict: Responsive ecommerce site, with PWA upgrade later if you build a loyal repeat-customer base. Native apps make sense only at scale — once you have thousands of monthly customers and meaningful repeat purchase rates.
Restaurant or Hospitality
Verdict:Responsive website with booking integration. PWA if you do delivery direct (not via Deliveroo / Just Eat). Skip native unless you're building a multi-location chain.
SaaS or B2B Software
Verdict:Web app (responsive). Add a native companion app only if mobile-specific workflows (field data entry, mobile approvals, on-the-go dashboards) drive meaningful usage. Many successful B2B SaaS companies never ship a mobile app and don't need to.
Booking or Marketplace Platform
Verdict:Depends on whether you're aggregating supply (sellers, drivers, hosts) or just demand (customers). Supply-side users open the app constantly and need push notifications — go native for them. Demand-side users book occasionally — a responsive web flow is enough. Many platforms ship a native app for sellers and a website for customers.
Field Service or Logistics Operation
Verdict: Native, no debate. You need offline mode, push notifications, GPS, camera, and an icon on the home screen. This is one of the strongest cases for going native.
Fitness, Health, or Habit App
Verdict:Native. Daily use, push notifications, biometric auth, integration with HealthKit / Google Fit. The category sets the expectation — users will judge a web app as “not real.”
The Cost Reality (UK Pricing, 2026)
Let's talk specifics — these are real UK ranges for May 2026, not glossy SaaS landing-page numbers.
- Responsive website (5 – 10 pages): £1,500 – £4,000 with a freelance developer, £4,000 – £15,000 with a small agency.
- Custom web app (booking system, portal, dashboard): £3,000 – £15,000 with a freelancer.
- PWA upgrade for an existing site: £2,000 – £6,000.
- Cross-platform mobile app (React Native, focused MVP): £8,000 – £25,000.
- Complex native app with backend integrations: £25,000 – £60,000+.
- Ongoing maintenance (native app): £150 – £500/month for OS-update compatibility, dependency upgrades, bug fixes.
Red Flags When Someone Says “You Need An App”
- “Apps get higher engagement”— true on average, but causation is the other way round. People install apps they were already engaged with. Building an app first doesn't create that engagement.
- “Everyone has an app these days” — not a reason. The graveyard of UK SME apps with 12 downloads is enormous.
- “It's only £5,000 with [overseas builder]”— possible, but check what you're actually getting: ownership of the codebase, App Store account in your name (not theirs), ongoing maintenance access. Cheap upfront often becomes expensive in year two.
- “App Store presence will get you customers” — only if you spend on App Store Search Ads. Organic App Store discovery is brutal for unknown apps.
The Smart Middle Path: PWA First, Native Later
For most businesses sitting on the fence, this is the smart move. Build a Progressive Web App as an upgrade to your existing site — installable, offline-capable, push notifications where supported. Cost is a fraction of native development. You learn whether users actually want to install your app at all.
If real installs and engagement justify it, you graduate to a native app with React Native, reusing much of your existing backend. If they don't — you saved £15,000 to £30,000 and shipped something useful regardless.
How To Decide In Five Minutes
Score yourself: one point for each “yes” answer.
- Are push notifications core to my business model? (Y/N)
- Do my users need to work offline? (Y/N)
- Do I need deep device features (camera, GPS, biometrics, in-app purchase)? (Y/N)
- Is App Store presence material to my brand or category? (Y/N)
- Will users open this daily or weekly, not monthly? (Y/N)
0 – 1 yes: Responsive website. Spend the difference on marketing.
2 yes: Progressive Web App. Get the benefits without the build cost.
3+ yes: Native app. The investment is justified.
Bottom Line
Most UK businesses asking “should we build an app?” would get more value from improving their website. The few that genuinely need a native app know it because the use case forces the answer.
If you're in the “not sure” bucket — that's usually a signal you don't need one yet. Start with a better website or a focused PWA, prove people want what you're offering, then graduate to native if and when the data justifies it.
Thinking About Building An App?
I'm happy to talk through your situation before any commitment. Sometimes the answer is “yes, native is right” — sometimes it's “your existing website needs work first.” Either way, you'll get a straight answer.