Contents

A business needs a mobile app when customers use the service often — several times a week — and push notifications, offline use or phone features add real value. If people visit rarely, from search or a link, a responsive website is enough: it is cheaper, faster to launch and needs no install. To test demand, starting with a website is almost always sensible.

Here are the selection criteria, the hidden costs of an app and the options in between.

When is a responsive website enough?

A responsive website is enough when customers use the product occasionally and arrive from search, ads or links. Making them install an app for a single purchase or enquiry is an extra hurdle that loses part of the audience.

Signs a website will do:

  • customers use the product once a month or less;
  • the main path is find, choose, enquire or pay;
  • the product must be searchable and open from a link in a messenger;
  • no flows need the camera, background location or offline mode;
  • the budget is tight and demand must be tested quickly.

A modern website can do a lot: payments, sign-in, location while in use, photo uploads from the camera. That covers most of what used to require an app.

When is an app actually justified?

An app is justified when it reinforces frequent use: customers come back regularly, push notifications bring them back even more often, and the icon on their home screen acts as a constant reminder. Add to that flows that work poorly or not at all in a browser.

Criterion Favours a website Favours an app
Frequency of use Rare, occasional Several times a week or more
Customer source Search, ads, links Already loyal customers
Notifications Email and messengers suffice Push is critical to the flow
Offline use Not needed Needed: couriers, field staff
Device features Basic Background location, Bluetooth, NFC, advanced camera
Budget and timeline Limited Resources for two platforms and upkeep

Typical cases where an app pays off: delivery and ride-hailing, banking and finance, fitness and habit tracking, field staff tools and products with frequent repeat orders.

A person using a smartphone Photo: Unsplash

What does a mobile app cost?

A mobile app costs more than a website not only to build but also to maintain: two platforms, store publishing, mandatory updates for new OS versions and a slower release cycle for fixes. These costs continue for as long as the app lives.

What you add compared with a website:

  1. Two platforms — iOS and Android; cross-platform tools reduce the cost but do not remove it.
  2. Publishing and review — stores review every update, so an urgent fix is not instant.
  3. Mandatory updates — stores regularly raise SDK requirements; see the deadlines in our news piece on iPhone Duo and iOS 27.
  4. Old versions in the wild — the API must support apps that have not been updated for months.
  5. Store commissions on in-app digital purchases.
  6. Install marketing — users have to be persuaded to download the app.

The order we recommend

For a new product: a responsive website or web app first, test demand and usage frequency, then an app for the most active customers. The website stays the entry point from search. We covered first-release budgets in how much an MVP costs.

Are there options in between?

There are: progressive web apps (PWAs), mini-apps inside messengers and super-apps, and cross-platform development. They deliver some of an app's advantages without the full cost of two native versions.

  • PWA — a website that can be installed on the home screen, with offline support and notifications; its capabilities on iOS are more limited than on Android.
  • Messenger mini-apps — quick access without installation where your audience already spends time.
  • Cross-platform development — one codebase for iOS and Android when an app is needed after all.

How do you make the decision?

Decide based on customer behaviour data, not because "competitors have an app". Answer a few questions and the choice usually becomes obvious.

  1. How often will customers use the product?
  2. Which flows do not work, or work poorly, in a browser?
  3. Where do new customers come from — search or your existing base?
  4. Can the budget cover two platforms and ongoing maintenance?
  5. Do you already have a website that shows how mobile users behave?

In short

  • An app is justified by frequent use, important push notifications, offline mode and device features.
  • For occasional visits and customers from search, a responsive website is enough.
  • An app costs more not just to build but to maintain across two platforms.
  • In-between options are PWAs, mini-apps and cross-platform development.
  • For a new product, start with a website and add an app when data confirms frequent use.

FAQ

  • Can we build an app for only one platform?

    Yes, if your audience clearly skews to iOS or Android. But most products need both, so one version usually ships first and the second follows, or a cross-platform approach is used.

  • Do we still need a website if we have an app?

    Almost always: the website brings new customers from search, opens from links and serves as an entry point for people who do not want to install an app.

  • How long does publishing an app to the stores take?

    Update reviews usually take from a few hours to a few days; the first release takes longer because of account and listing setup. Build this time into your release plan.