App vs website: does your UK business actually need an app?

September 10th, 2026 at 09:14 am

Last updated: September 2026 Author: Ronak shah, Nordstone — app development consultancy

Most UK businesses need a website first — it’s cheaper, reaches everyone with a browser, and gets found on Google. Build a native app only once customers use you often enough to want it on their home screen, need offline access, or need hardware features like GPS or camera. A progressive web app (PWA) is often the sensible middle step.

TL;DR

• The short rule: website first for reach and discoverability; app only once frequent use, offline need or hardware access justify it; PWA as a middle ground for many.
• What a website does best: wide reach, low cost, no install friction, works for every visitor via search or a shared link.
• What an app does best: repeat engagement, push notifications, offline functionality, camera/GPS/biometric access, and a home-screen presence.
• The PWA middle ground: installable and offline-capable on both platforms, with push now working on iOS 16.4+ — but no App Store listing and a smaller, weaker push reach than native on iPhone.
• The cost gap: a professional website typically runs £1,500–£10,000; a PWA £8,000–£25,000; a native or cross-platform app £15,000–£100,000+ depending on complexity.
• Decision checklist: the right answer depends heavily on business type — a restaurant’s needs differ sharply from a marketplace’s or a service business’s.

Do you need an app, a website, or a PWA?

The short rule: start with a website, add a PWA once mobile use is heavy, and only build a native app once you have a specific reason a browser genuinely can’t deliver — high-frequency repeat use, offline functionality, push notifications that need to reach iPhone users reliably, or access to device hardware like the camera, GPS or biometric sensors. Most UK small businesses overestimate how much an app will help and underestimate how much a well-built website already covers. A website is discoverable by anyone searching Google, costs a fraction of an app to build and maintain, and needs no install step — which matters, because the average person now has dozens of apps on their phone and opens only a handful regularly. An app earns its cost when it solves a problem a website structurally can’t: a loyalty scheme that needs to live on the home screen, a delivery app that needs live GPS  tracking, or a service that customers genuinely open several times a week.

What a website does better (and cheaper)

A website wins on reach, cost and discoverability by a wide margin. Anyone can land on it from a Google search, a social link or an ad — with no download, no account creation and no storage taken up on their phone, all of which reduce the number of people who ever actually experience what you’ve built. It’s also dramatically cheaper: a professional UK small business website typically costs £1,500–£10,000 to build, against £15,000 or more for even a simple app, and ongoing running costs sit at roughly £50–£300 a month rather than the 15–20% of build cost per year that apps typically demand for maintenance and compliance. Search engine visibility is another structural advantage — Google can’t index the contents of a native app the way it indexes a webpage, so for any business relying on organic search to bring in new customers, a website isn’t optional even if you also build an app.

What an app does better

Where an app earns its cost is engagement and access. Push notifications reach users directly on their lock screen with far higher open rates than an email or a website visit ever achieves, which matters enormously for businesses built on repeat custom — a coffee shop loyalty scheme, a fitness studio booking system, a delivery service. Native apps also get proper offline functionality: data cached locally, forms that work without signal, content available on a train or in a basement gym, which a standard website generally can’t offer without significant extra engineering. Hardware access is the other major differentiator — camera for scanning or photo upload, GPS for live tracking, biometric authentication for secure login, Bluetooth for connected devices — all of which native apps handle natively and browsers either can’t access at all or access with far more friction and weaker reliability. Finally, there’s simple presence: a home-screen icon is a standing invitation to open your product again, in a way a bookmarked website rarely is.

The PWA middle ground

A progressive web app sits between the two: a website built with modern browser technology so it can be added to a home screen, cache content for offline use, and — on Android and desktop — send push notifications directly through the browser, all without going through an app store. On Android, PWAs are genuinely close to a native app in capability. On iOS, the picture has improved substantially but still comes with real limits: push notifications have worked on iOS since version 16.4, but only for PWAs the user has actually installed to their home screen via Safari’s “Add to Home Screen” — a push notification cannot reach a PWA that’s only ever opened as a browser tab, and background sync remains unsupported on iOS even now. A PWA also can’t be listed in the App Store or Google Play, so it misses out on app-store discovery entirely and relies on the business driving people to install it directly. For many UK small businesses — particularly retail, hospitality and local services — a PWA delivers 70–80% of what a native app offers at closer to a website’s cost, which makes it a genuinely sensible middle step rather than a compromise.

 Cost comparison

A decision checklist by business type

For a restaurant or café, a strong website with online ordering and a Google Business presence usually covers 90% of what customers need — a PWA is worth adding once you’re running a loyalty scheme or want repeat order reminders, but a full native app rarely pays for itself unless you’re operating at multi-site scale. For retail, the calculation depends on frequency: a single boutique is usually better served by a well-built e-commerce website, while a retailer with a loyalty programme, frequent restocks customers want to be notified about, or barcode-scanning in-store functionality has a genuine case for a PWA or native app. Service businesses — trades, clinics, salons, consultancies — mostly need a website that converts enquiries into bookings; an app becomes worthwhile only once you’re managing recurring appointments, want push reminders to cut no-shows, or need field staff to work offline on-site. Marketplaces and two-sided platforms are the clearest case for a native or cross-platform app early, since they typically depend on frequent repeat use, push-driven engagement between buyers and sellers, and often GPS or camera access — the categories where a website structurally falls short rather than merely being less convenient.

Frequently asked questions

Not sure? Get free advice

If you’re weighing up a website, a PWA or a full app and want an honest steer rather than a sales pitch, get in touch with Nordstone for a free scoping conversation — we’ll tell you if you don’t need what you think you need.