“We need an app” is one of the most common requests we hear, and one of the most expensive to get wrong. Native apps are powerful, but they are also costly to build, costly to maintain and hard to get installed. A responsive website reaches everyone instantly but cannot do everything an app can. And there is a third option, the progressive web app, that often fits best. Here is how to decide.
Key takeaways
- Choose a responsive website when your goal is reach, information, bookings or purchases.
- Choose a native app when you need offline use, device hardware, push notifications at scale, or daily repeated use by loyal users.
- Consider a progressive web app (PWA) when you want app-like features without app-store costs.
- Apps cost three to ten times more than websites over three years. Make sure the use case justifies it.
Start with the user, not the technology
Ask: how often will the same person use this, and what will they do? Someone looking for a plumber uses you once a year; they will never install your app. A gym member checks in four times a week; an app with a membership card and class bookings makes sense. Frequency and depth of use are the strongest predictors.
When a responsive website is the right answer
- Your main goals are enquiries, bookings, sales or information.
- Customers find you through search and ads; a website is where that traffic lands.
- Usage is occasional rather than daily.
- You need to launch fast and iterate cheaply.
- You want one codebase to maintain.
A modern responsive site can do far more than people assume: online payments, bookings, account areas, chat, push notifications (via PWA) and offline caching. Built well, it feels like an app on a phone.
When a native app is the right answer
- Daily or weekly repeated use by the same users (fitness, banking, delivery, field service, internal tools).
- Heavy use of device features: camera workflows, Bluetooth, GPS tracking in the background, NFC, sensors.
- Offline-first operation (warehouses, sites with poor signal).
- The app is the product or a core channel, with a budget for ongoing development.
- You need the presence and trust of being in the App Store and Google Play.
The middle option: progressive web apps
A PWA is a website that can be installed on the home screen, work offline, send push notifications (on Android and, since 2023, on iOS) and load instantly. It costs roughly what a good website costs, needs no app store approval and updates instantly. For loyalty programmes, ordering, portals and internal tools it is often the sweet spot. Its limits: deeper hardware access and some iOS restrictions.
Cost and timeline comparison
| Responsive website | PWA | Native app (iOS + Android) | |
|---|---|---|---|
| Build cost | $3,000 – $15,000 | $8,000 – $30,000 | $25,000 – $150,000+ |
| Timeline | 3 – 10 weeks | 6 – 14 weeks | 3 – 9 months |
| Yearly maintenance | 10 – 15% of build | 15 – 20% | 20 – 30% + store compliance |
| Reach | Everyone, instantly | Everyone, installable | Only after install |
| Offline / hardware | Limited | Good | Full |
| Discoverability | Search engines | Search engines | App stores + marketing |
Cross-platform frameworks such as Flutter and React Native reduce native cost by sharing one codebase for both platforms; this is how we build most client apps.
A simple decision framework
- Write down the top three things users must do. If all three work in a browser, build a website first.
- Estimate how many users will use it weekly. Under a few hundred, an app rarely pays back.
- List any hardware or offline needs. If the list is empty, a PWA probably covers you.
- Check the budget for year two and three, not only the build.
- If an app still makes sense, launch the website first and let it fund and inform the app.
Common mistakes
- Building an app that duplicates the website, then wondering why nobody installs it.
- Launching on both platforms at once with an untested idea. Start with one.
- Forgetting the backend, admin panel and analytics in the budget.
- Skipping app store optimisation, then relying on luck for downloads.
Frequently asked questions
Can a website be turned into an app later?
Yes. If the site is built with a clean API and modern front end, an app can reuse the backend. We design websites with that path in mind when clients expect to need an app.
Do I need an app to send push notifications?
No. PWAs can send push notifications on Android and iOS. Email and SMS are also effective for occasional contact.
How long does app store approval take?
Google Play typically one to three days; Apple one to seven days, with the risk of rejections that add time.
Do you build both websites and apps?
Yes. We design and build responsive websites, PWAs and native apps for iOS and Android, and we will tell you honestly which one you need.
Not sure whether you need an app?
Describe what your customers need to do and we will recommend the right option on a free 30-minute call.