Does Your Business Need an App or a Better Mobile Website?
Most businesses need a better mobile website before they need an app. The website is how new customers find you, and a fast, easy mobile site serves everyone who arrives from search, an ad or a shared link – without installing anything. An app is worth building when a defined group of customers comes back often to do something repeated, or when you need things a browser can't do well, such as tracking location with the screen off. Many businesses end up with both, usually in that order.
Two different jobs
A website and an app usually serve different people:
- The website works for people who don't know you yet. They search, compare, read and get in touch. Google says it "uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking", so your mobile site is the version that counts in search. An app does not replace it.
- An app works for people who have already chosen you and want a faster way to do something they do often – reorder, book, check a status, collect points.
Before deciding, look at your analytics: how many visitors use phones, which pages they open, where they give up and how many come back regularly. If mobile visitors leave because of slow pages or awkward forms, an app won't fix that – they would never get far enough to install it.
What a better mobile website can solve
Many reasons for wanting an app are really problems with the mobile site: slow loading, small buttons, long forms, menus that hide what people need. Our articles on mobile problems a responsive layout doesn't solve and what to check on a slow website cover the usual fixes.
A website can also behave more like an app than many people expect. A progressive web app (PWA), as Google's web.dev describes it, is a web app "built and enhanced with modern APIs to provide enhanced capabilities" while still "reaching any web user on any device with a single codebase". Installed PWAs launch from the home screen, and they can be built to cope with slow connections or no connection at all. On iPhone and iPad, Apple added Web Push for web apps added to the Home Screen in iOS and iPadOS 16.4; the permission request has to come in response to a direct user action, such as tapping a subscribe button. The catch is that extra step: the user has to add the site to the Home Screen first, so it works best for customers who are already engaged.
When an app makes sense
- Frequent, repeated use – weekly or daily orders, bookings, account checks, loyalty programmes.
- Device features in the background. The W3C Geolocation specification says position updates "are exclusively for fully-active visible documents" – a web page can't keep logging location once it is hidden. Recording a route with the phone in a pocket needs an app.
- Hardware and heavy offline work – Bluetooth devices, continuous camera processing, field work without coverage.
- Notifications that are central to the service, not just occasional marketing.
One warning for app ideas that amount to "our website, but in the store". Apple's App Review Guidelines say an app "should include features, content, and UI that elevate it beyond a repackaged website", and that if it is not particularly useful, unique or "app-like", it doesn't belong on the App Store. If your app would mostly repeat the website, invest in the website instead.
Website, PWA or app: a quick comparison
| Mobile website | PWA | App | |
|---|---|---|---|
| Found through Google search | Yes | Yes | Through its store page and your website |
| Needs installing | No | Optional (home screen) | Yes, from a store |
| Push notifications on iPhone | No | Yes, after adding to the Home Screen | Yes |
| Location and sensors in the background | No | No | Yes, with the user's permission |
| Publishing a change | Immediately | Immediately | New release, through store review |
| Codebases | One | One | One or two, depending on the approach |
Example: auto-data.net
The car specifications catalogue auto-data.net started as a website and grew through Google search in many languages. The Android and iOS app came later, for people who check car data often and wanted quicker access. The website and the app use the same data through a shared API, so a correction made once appears everywhere – more in one API for a website and a mobile app. The order mattered: the website brought the audience, and the app served the part of it that kept coming back.
What an app costs to keep running
Building the app is only the start. Plan for:
- Developer accounts with Apple and Google, and a store review for every new release.
- Store requirements. Google Play, for example, requires new apps and app updates submitted from 31 August 2026 to target Android 16 (API level 36), and existing apps must target at least Android 15 (API level 35) to stay available to new users on newer Android versions. Updates like these are driven by the store, not by a wish to have the newest version – but they do come round, and they need a budget.
- Testing on real devices – different screen sizes, operating system versions and permission settings.
- An API that keeps working for older app versions, because not everyone updates.
- The website, which you still need for everyone who hasn't installed the app.
Questions to answer before ordering an app
- How often would one customer open it, and what would they do there?
- What could they do in the app that they can't do comfortably on a good mobile site?
- Does it need something a browser can't do, such as background location or Bluetooth?
- Where will the first users come from?
- Is there already a server, database and API, or do they need to be built?
- Who will handle store requirements, reviews and user support?
If the honest answers to the first two are "rarely" and "nothing special", improve the website first and revisit the app once you see people coming back often.
We build both websites and mobile apps, so we have no reason to push you towards one or the other. Tell us what your customers do on their phones, and we'll help you decide where to start.