Does your small business need an app, or is a website enough?

The short answer

Ask what your customers do with you, and how often. Someone who books a boiler service once a year, or a solicitor once in a decade, will never install your app. Someone who books a class three times a week might.

For most small businesses, a website that is fast on a phone covers everything customers want to do: read what you offer, check prices and hours, call with a tap, find you on a map, book, pay and message. It needs nothing installed and works on every phone.

An app of your own makes sense when customers come back every week or more, need something a browser does badly, and you can pay for its upkeep for years. Before that point, two cheaper routes usually do the job: the app your booking or loyalty software already provides, and a web app that customers add to their home screen.

What a website already does on a phone

Many of the things owners want an app for, a website can already do:

• An icon on the home screen. On an iPhone, Safari's Add to Home Screen puts your site there with its own icon, and WebKit says that from iOS 26, every website added to the Home Screen opens as a web app by default, without the browser bars. Android phones can add a site to the home screen from the browser too.
• Notifications. Since iOS and iPadOS 16.4, a web app added to the Home Screen can ask permission to send push notifications, as long as the request follows a tap, such as on a "Notify me" button.
• Accounts. A website can have a login where customers see their bookings, passes, invoices or documents.
• Payments, bookings and messages, through the same tools you would use inside an app.

So a home screen icon, a login and notifications no longer need an app of your own. What a website still does badly is covered in the test below.

When an app is worth it

An app of your own earns its place when most of these are true:

• Customers use you every week or more, not twice a year.
• They need something a browser does poorly: working with no signal, opening a door or a locker with the phone, scanning a pass at the entrance, or following a delivery as it moves.
• Your notifications would be welcome rather than tolerated: a space has opened in tonight's class, the order is ready.
• Someone will keep it updated for years, for new phone software and new store rules.
• You can give people a reason to install it, such as faster booking, a pass at the door or points that pay back.

If only one or two are true, a better website or the app your software already has will do the job for far less.

The real cases tend to be businesses whose customers come back every week: gyms and studios with members, food businesses with regulars who order ahead, and services that happen on the phone itself.

Check the apps your tools already have

Before you pay for an app of your own, look at what your software already gives your customers. Many booking, ordering and loyalty systems come with an app, and some sell a version with your name on it. Two examples:

• Mindbody has its own app where clients book classes and appointments, and sells a branded mobile app as an add-on that puts a studio's business in the iOS and Android app stores without custom development.
• Square Loyalty needs no app at all: customers join and collect points with their phone number at the till, and Square's help pages say they get a text with a link to see their rewards.

Ask your provider what customers can do in its app, whether your name and logo appear, whether other businesses are shown next to you, and what happens to your customers' accounts if you leave. A branded app from your booking software puts you in the stores without the work of building and keeping an app, and for many studios that is the right answer.

What it takes to get into the app stores

An app of your own has to get past two gatekeepers, Apple's App Store and Google Play, each with its own account, fees and checks:

• Apple charges a Developer Program membership every year. Google Play charges a one-time registration fee and asks developers to verify their identity.
• Apple reviews every app and every update. Its guidelines say an app should offer features, content and an interface beyond a repackaged website, and that an app which is not particularly useful, unique or app-like does not belong in the store.
• Google Play requires new personal developer accounts to run a closed test with at least 12 testers, opted in for at least 14 days, before an app can be published.
• Both stores need a link to your privacy policy and a description of the data the app collects, and Google says that applies even to apps that collect none.
• If the app lets people create an account, Apple requires that they can also delete it from inside the app.

The rule about repackaged websites is the one that catches small businesses. An app that shows your website inside a frame runs straight into it.

What it takes to keep an app in the stores

An app is never finished. To stay in the stores and keep working, it needs regular work even when you add nothing new:

• Apple's membership renews every year. Apple says that if it expires, your apps are no longer available to download, although they keep working for people who already have them.
• Apple sets a minimum version of its developer tools for every upload. From 28 April 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later, so an app that has not been touched in a while needs work before its next update.
• Google Play requires new apps and updates to target a recent version of Android: from 31 August 2026, Android 16. Existing apps that fall behind the requirement can no longer be installed by new users on newer Android phones.
• New phone software each year can break something, so the app needs testing every year on both platforms.
• Reviews, bug reports and support emails arrive through the stores, and someone has to answer them.

Add that up for three years, usually for an iPhone version and an Android version, before you decide. A website needs care too, but one site on the open web is less work to keep than two apps in two stores plus the website you still need anyway.

Payments inside an app

If customers pay for something they use in the real world, such as a haircut, a class or a meal, Apple's guidelines say the app must use a payment method other than Apple's in-app purchase, such as Apple Pay or card entry. So an app for real-world services can take payments much as your website does.

Digital content is different. Apple's guidelines say that when customers pay for extra features or content inside the app, such as access to premium content, the app must use in-app purchase, and the rules on this now differ between the US, the EU and other regions. If you plan an app around something digital, such as a yoga studio's library of recorded classes, read each store's current payment rules before anything is built.

The middle route: a web app

Between a website and an app sits the web app: a website built to behave like an app, which customers add to their home screen from the browser. It can keep people logged in, show a member's bookings and passes, keep showing pages it has already loaded when the signal drops, and send notifications once it is on the home screen.

It goes through no store review, it updates the moment you change it, and one version works on every phone and computer. The limits are real: customers have to add it themselves, it does not appear in app store searches, and some phone features stay out of reach in the browser, especially on iPhone.

For a members area at a gym, a client portal at an accountancy practice or a parents' page at a tutoring centre, a web app is often all the app anyone needs. Customer portals like these are among the web apps we build alongside websites: see websites.

Getting people to install it

An app nobody installs does nothing. People already have the apps they use every day, and a business they visit once a month is a hard sell for one more. Before you build, decide what makes installing worth it for the customer: a faster way to book than the website, a pass that opens the door, points that pay back.

Then count who would really use it. A studio whose members book every week has an audience for an app. A salon whose clients come back every six weeks mostly does not, and the booking software's own app or a link in a text reminder serves those clients better. Booking and calendar automation covers the reminders.

Five businesses, five answers

• A barbershop: no app. A booking link on the website and the Google profile, and reminders by text, cover everything its customers do.
• A yoga studio whose members book every week: the branded app from its booking software, if it offers one, or a web app for bookings and passes. A custom app only for features no tool offers.
• A cafe with regulars: a loyalty scheme that runs on phone numbers at the till, such as Square Loyalty, before any app. An app is worth a look once ordering ahead at several sites is part of it.
• A property management company whose tenants report repairs: a web portal with a login, where tenants send photos and follow progress. A tenant reports a few times a year, which is not app territory.
• A 24-hour gym with keyless entry: a real case, because the phone opens the door. Ask the supplier of the door system first, because it may already provide the app.

If you still want an app

If the test points to an app, answer these before anyone writes code:

• What will a customer do in it each week that the website does not let them do?
• Who updates it, and what does that cost each year, for both stores?
• Which of your existing tools must it talk to, and do their APIs allow it?
• How will you get your first customers to install it?
• Which number will tell you after six months whether it was worth it: weekly users, bookings made in the app, repeat orders?

Build or fix the website first either way. People find you through Google, ads and reviews in a browser, and every app still needs pages on the web for its privacy policy and support.

Where to start

For most small businesses the order is: a fast website that works on a phone, a booking route that takes a minute, reminders by text or email, and a home screen icon for the customers who want one. How to get more bookings from your website covers the first three.

Then listen. If regulars keep asking for something only an app can do, you will know, and by then you will have the website every app needs behind it. Until then, the money an app would cost is better spent on the pages that bring new customers in. If you are not sure a website is needed at all yet, does your small business need a website answers that honestly too.