Someone on your team has suggested building an app. Maybe a competitor launched one. Maybe a customer asked for it. Maybe it just feels like the kind of thing a modern business should have. Before you spend tens of thousands of pounds, let's be honest about whether you actually need one.
The short answer for most businesses: you probably don't. And that's completely fine.
When You Don't Need an App
- •Your "app" is really just a website with a home screen icon
- •You have fewer than 1,000 regular users
- •Your use case doesn't need native device features
- •You're hoping an app will fix an engagement problem
Your "app" is really just a website with a home screen icon. If the core experience is reading content, browsing products, or filling in forms, that's a website. Wrapping it in an app doesn't make it better — it just makes it more expensive to build and maintain. Users can already add your website to their home screen if they want quick access.
You have fewer than 1,000 regular users. Apps live and die on usage frequency. If you don't have a large, active user base that would open your app multiple times a week, you're building something that will sit unused on people's phones until they delete it during a storage clear-out. The App Store is a graveyard of apps with twelve downloads.
Your use case doesn't need device features. If your product doesn't require access to the camera, GPS, accelerometer, health data, Bluetooth, or offline functionality, there's nothing an app can do that a well-built responsive website can't. And the website is cheaper to build, easier to update, and works on every device without installation.
You're hoping an app will fix an engagement problem. If people aren't using your website, they won't use your app either. An app is a distribution channel, not a solution to a marketing problem. Fix the value proposition first.
When You Genuinely Need an App
- •The mobile experience IS your product
- •You need native device features (camera, GPS, Bluetooth, offline)
- •You have a loyal user base who'd use it daily
- •Push notifications are core to your engagement model
The mobile experience IS your product. Fitness tracking, food ordering for regulars, habit trackers, ride-hailing — these are products that only make sense as a native mobile experience. The phone isn't just a screen; it's the primary tool. If your product lives in someone's pocket and they reach for it multiple times a day, native is the right call.
You need native device features. Camera access for scanning or AR. GPS for real-time location tracking. HealthKit or Google Fit integration. Bluetooth for connecting to hardware. Offline functionality for areas with poor signal. These are legitimate technical reasons to go native — a website simply can't access this hardware reliably.
You have a loyal user base who'd use it daily. If you already have thousands of engaged users who interact with your service multiple times a week, an app can deepen that relationship. The key word is "already." An app doesn't create loyalty — it rewards and reinforces it.
Push notifications are core to your engagement model. Real push notifications — not the limited web push kind — are significantly more effective for time-sensitive communication. If your business model depends on reaching users at the right moment (delivery updates, time-limited offers, reminders), native push notifications are measurably better than any web alternative.
The Middle Ground: Progressive Web Apps
There's an option that sits between a website and a native app: the Progressive Web App, or PWA. A PWA is a website that can be installed on a user's home screen, work offline, send basic push notifications, and feel like a native app — without the App Store, without the download friction, and at a fraction of the development cost.
| Feature | Native App | PWA | Website |
|---|---|---|---|
| Offline access | Full | Partial | No |
| Push notifications | Full | Limited (iOS) | Basic |
| Device hardware | Full | Limited | Minimal |
| App Store presence | Yes | No | No |
| Install required | Yes | Optional | No |
| Update control | Store review | Instant | Instant |
| Development cost | High | Medium | Low |
PWAs aren't perfect. They can't access all device hardware, they're limited on iOS compared to Android, and they don't appear in the App Store (which, depending on your perspective, is either a drawback or a feature). But for many businesses that want an app-like experience without the app-level investment, a PWA is the sweet spot.
A Simple Decision Framework
Ask yourself two questions. First: how often would someone use this? If the answer is daily or multiple times per week, an app makes sense. If it's weekly or less, a website is fine.
Second: do you need native device features? Camera, GPS, health data, Bluetooth, offline access — if yes, you need a native app. If no, a responsive website or PWA will do the job.
| Signal | You Need an App | A Website Is Fine |
|---|---|---|
| Usage frequency | Daily or multiple times per week | Weekly or less |
| Device features | Camera, GPS, Bluetooth, offline | None required |
| User base | Thousands of active users | Still growing |
| Core experience | Mobile-first interaction | Content or forms |
| Notifications | Time-sensitive, real-time | Email is sufficient |
High frequency + device features = native app. A fitness tracker, a delivery service, a banking app.
High frequency + no device features = PWA or website. A news platform, a SaaS dashboard, a community forum.
Low frequency + device features = think carefully. You might need an app, but consider whether the usage justifies the cost.
Low frequency + no device features = website. Full stop. Save your money.
If You're Not Sure
If you're reading this trying to decide whether you need an app, you probably don't need one yet — and that's genuinely good news.
If you're reading this article trying to decide, that probably means you don't need an app yet. And that's genuinely good news — it means you can invest that budget in a brilliant website that serves your customers well, generates leads, and builds the audience you'd eventually need to justify an app.
When the time comes — when you have the users, the use case, and the clear evidence that a native experience would be meaningfully better — you'll know. Until then, build for the web. It's faster, cheaper, and reaches more people without asking anyone to download anything.