Someone told you your business needs an app. Maybe it was a developer, maybe a friend, or maybe a competitor just launched one and it has been bugging you ever since. You can already see the problem: apps sound expensive and slow to build, and you are not sure your customers would even download yours. The mobile app vs website question is really a question about your customers, not about technology. A fast, mobile-friendly website can often do the job, and a web app can now cover several things that used to need the app stores. An app starts to pay for itself when customers come back often for one specific task that an app does better. You can work out which side of that line you are on with your own numbers, in about fifteen minutes.
Key Takeaways
A fast mobile site handles booking, ordering, payments and accounts, and a progressive web app can add a Home Screen icon, notifications and offline use.
A native app earns its cost when customers return often for one task it makes faster, such as reordering, loyalty, bookings or offline work.
Google's own guidance says download numbers are not a good measure of an app's value; repeat use and retention are.
Apple charges $99 a year, both stores review every update, and each new phone operating system brings more work.
Does my business need an app, or is a website enough?
For a business that customers visit now and then, a good website is usually enough. If people find you, check your hours, read about your services, book a slot or pay for an order, a well-built mobile site does all of that without asking anyone to install anything. It is also the thing search engines can find, which an app in a store cannot replace.
An app becomes worth it when three things are true at once. Your customers come back often, weekly or more. There is one specific task they repeat, like reordering the usual, checking a loyalty balance, booking the next class or showing a membership pass. And doing that task in an app is clearly faster or better than doing it on your site, because of notifications, offline access, or a phone feature like a scanner or Bluetooth.
If you cannot name that repeated task, the site is the better place to spend. If you can name it, and you have evidence customers would use it, then it makes sense to look at what an app would cost to build and to keep running.
What can a website or web app do now that used to need an app?
More than you might expect. A progressive web app, often shortened to PWA, is a website built so a phone can treat it like an app. MDN's guide to progressive web apps describes what that covers: a Home Screen icon, a full-screen look without the browser bar, content cached so pages load when the signal is weak, offline use, and push notifications. Browsers also give websites access to the camera, location and payment features, as the MDN Web API reference documents.
The biggest change came on the iPhone. WebKit, the engine behind Safari, announced that iOS and iPadOS 16.4 added Web Push for Home Screen web apps, along with support for other browsers adding sites to the Home Screen. A customer who saves your web app to their Home Screen can now get notifications from it, if they give permission.
There are limits, and they matter for some businesses:
- Install first on iPhone: Web push on iPhone works after the customer adds the web app to their Home Screen, not from a regular browser tab.
- Storage can be cleared: WebKit's storage policy lets the phone remove a web app's saved data under storage pressure or after long inactivity.
- Background work is limited: Web apps cannot run much in the background, and features vary by browser and platform.
- Some hardware stays native: Certain Bluetooth and NFC uses, deep system features, widgets and background processing may be unavailable or weaker on the web.
If your idea for an app is mostly booking, ordering, paying, logging in and getting notified, a website or web app may already cover it. If it depends on the items in that list, a native app has a real advantage.
When does a native app earn its cost?
A native app is the kind you download from the App Store or Google Play and that is built for the phone's own system. It earns its cost when it turns something customers already do often into something faster or better. The examples that fit best share a pattern of frequent, repeated use. Before you spend, it helps to look at what the evidence says about how people actually use the apps they install.
Which businesses fit the pattern?
Look for weekly or daily use tied to one clear job. A cafe or restaurant with regulars who reorder the same thing. A gym or studio where members book classes every week and show a pass at the door. A service business whose customers track a delivery or a technician's arrival. A field team that needs to work offline and scan barcodes or QR codes on site. A business built around connected hardware through Bluetooth or NFC. In each case the app saves the customer time on something they would do anyway, or sends a notification they actually want.
A plumber who is called twice a year, a law office, or a shop that customers visit a few times a year usually has no repeated task for an app to speed up. For those, the money goes further on a better site.
Will customers download it and keep it?
This is the worry behind searches like "build an app for my business", and the evidence supports it. A 2014 Nielsen report found that smartphone users had about 42 apps installed on average, yet used fewer than 10 of them each day, and about half used only 1 to 4 daily. The figure is old, and there is no reliable current number for how many small business apps people keep. It still shows the problem: a phone full of apps does not mean yours gets opened.
Google says the same thing from the developer side. Its guidance on what great core value looks like notes that download numbers can be pushed up by marketing spend and are not generally a good measure of an app's value. Engagement and retention, meaning whether people keep coming back, are the better measures. So, the question to answer before building is not "will people download it" but "what would bring them back every week".
What does an app cost after it is built?
The build is the part you get a quote for. The running costs arrive after launch, and they are easy to miss. Our post on how much it costs to build an app for a business covers the build itself; this section covers what follows.
Apple's developer program is 99 USD per membership year. On sales of digital goods and services inside the app, Apple's commission is generally 30%, reduced to 15% for businesses in its Small Business Program with under 1 million USD in yearly proceeds, and for qualifying subscriptions. Google's Play service fees page says 97% of developers distribute their apps at no charge, and 99% of developers who do pay a fee qualify for 15% or less. These commissions apply to digital purchases; a restaurant order or a service booking paid through the app is handled differently, so check the store rules for your case.
Then there is review and upkeep. Every app and every update goes through Apple's App Review, and Google has its own developer program policies. Since June 30, 2022, Apple requires any app that lets people create an account to let them delete that account from inside the app. Each new version of iOS and Android can mean testing and fixes, and you still pay for crash monitoring, analytics, support and privacy work. Neither store publishes an annual maintenance price, because it depends on the app.
| Option | Store fees | Store review | Ongoing work |
|---|---|---|---|
| Mobile website | None | None | Hosting, updates, security |
| Progressive web app | None | None | Same as a website, plus testing install and push on each platform |
| Native app, iPhone | $99 a year; 15% or 30% on digital sales | Every app and update | OS updates, device testing, privacy and account deletion rules |
| Native app, Android | Fees vary; 99% of fee payers qualify for 15% or less | Policy compliance | OS updates, device testing, Android vitals monitoring |
| Platform app (booking or loyalty service) | The platform's recurring fees | Handled by the platform | Platform rules, limited changes, dependence on the vendor |
Two native apps, one for iPhone and one for Android, means two store listings, two review processes and two sets of devices to test. Cross-platform tools can share much of the code, but the store work and testing still apply to both.
What are the options between a website and a custom app?
You do not have to choose between a plain website and a custom app built from scratch. There are several steps in between, and each one trades cost and speed against control. The right one depends on what you want customers to do and how much you want to own.
A better mobile website with the features built in
A responsive site can take bookings, orders, payments, customer accounts and loyalty signups. It has the lowest barrier for customers, because there is nothing to install, and it can be found in search and shared by link. The trade-off is weaker re-engagement: without an app on their phone, customers come back through email, text or web push, and only if they opt in. If your current site is slow or awkward on a phone, fixing that through better web design often gets you more than a new app would.
A progressive web app
A web app adds the Home Screen icon, offline behavior and push notifications to the website you already have. It skips store review and separate iPhone and Android releases. Its limits are the ones listed earlier: install first on iPhone for push, storage that the phone may clear, and less access to background work and some hardware.
A booking, ordering or loyalty platform with its own app
Some booking and loyalty services give your customers an app as part of the subscription. That is faster and cheaper to launch than your own app. In return you accept recurring fees, the platform's rules, limited changes, and a dependence on another company's plans. Before signing, ask whether you can export your customer data and what happens to it if you leave.
A no-code or white-label app builder
These tools can produce an app faster than a custom build, which is why people searching "make an app for my small business" often land on them. They tend to come with recurring fees, lock-in, limited connections to your other systems, and less control over speed and store compliance. You still face store review and updates.
How can you check which one your business needs in fifteen minutes?
You can do the first screening yourself, with your own data. This is not a full business case, but it tells you whether a deeper look at an app is worth the time.
- Check your mobile share: In your analytics, open the last 30 to 90 days and look at mobile and tablet traffic. Note the share of visitors, bookings, orders and sales that come from phones. Use your own numbers rather than an industry average; the Google Analytics help center explains where to find device reports.
- Name the one app-only action: Write down the one thing customers would do in an app that they cannot already do easily on your mobile site. If the answer is "nothing", there is no app advantage yet.
- Estimate how often: Look at repeat bookings, repeat orders, logins, loyalty activity or visits per customer. Then ask 5 to 10 regular customers whether they would install the app, what they would use it for, and how often.
If phones bring in a large share of your business but the site is hard to use on them, fix the site first. If customers name a repeated task and say they would use it weekly, test that demand before building the full thing. A booking link, a loyalty signup on the site, email or text alerts, or a web app can show whether people use the feature before you pay for two native apps.
If the test shows steady repeat use, and a clear advantage from notifications, offline access or a phone feature, that is the point to ask for a costed plan for a native app.
What should you ask a developer before you build an app?
A good developer should be able to answer these plainly before you sign anything. If the answers are vague, treat that as a warning sign.
- What is the one task this app does better than our site?: You want a specific customer action, not a list of features.
- How will we measure success?: Look for repeat bookings, order frequency or retention, not download counts.
- Could a web app do this first?: A good answer explains which part truly needs native features, if any.
- Who owns the code and the store accounts?: The developer accounts with Apple and Google should be in your business's name.
- What does it cost to keep running each year?: Ask about store fees, OS updates, testing, support and privacy work, not just the build.
- What happens when the next iOS or Android version comes out?: Someone has to test and update the app, and you should know who and at what cost.
The most common ways these projects go wrong are practical ones rather than a measured ranking: an app that repeats the website and gives no reason to install, too little promotion to get downloads, customers who install once and never return, no tracking tied to bookings or sales, a scope that keeps growing, and upkeep nobody budgeted for. Each question above is aimed at one of those.
App or website: which fits your business?
Pick an answer to begin.
1. A customer visits your shop about three times a year. What is the better first spend?
2. Can a website send push notifications to an iPhone?
3. Which number best shows whether an app is working?
Frequently Asked Questions About mobile app vs website
Does every small business need an app?
No. A good mobile website is usually enough unless an app gives customers a repeated, clear reason to open it, such as reordering, bookings, loyalty or offline work.
Can a website be installed like an app?
Yes. A progressive web app can be added to a phone's Home Screen and open full screen, without the browser bar, where the browser supports it.
Can a web app send notifications on an iPhone?
Yes, since iOS and iPadOS 16.4, for web apps the customer has added to the Home Screen, and only with their permission.
Are app downloads a good sign that an app is working?
Not on their own. Google's guidance says download numbers are not a good measure of an app's value; repeat use, retention and completed bookings or orders tell you more.
What does an app cost after launch?
Apple's developer program is $99 a year, both stores may take a commission on digital sales, and every update goes through review. You also pay for testing, OS updates, support, analytics and privacy work.
Should I build an iPhone app and an Android app?
Only after you have shown demand. Two apps mean two store listings, two review processes and two sets of devices to test, so start with the platform your customers use, or with a web app that covers both.
What This Means for You
The mobile app or website decision comes down to one question: is there a task your customers repeat often enough that an app would make it clearly faster or better? A fast mobile site, perhaps with a web app on top, can cover booking, ordering, payments and notifications without asking anyone to install anything. A native app earns its place when you can name that repeated task, show that customers would use it weekly, and budget for the store fees, reviews and updates that follow launch.
Run the fifteen-minute check, fix anything that makes your site hard to use on a phone, and test demand with the tools you already have. If the evidence points to an app, you will go into it knowing what it is for and how to tell if it works.
At Web Leveling, we build both, which is why we start with the question rather than the app. Our application development work begins by checking whether a website or web app would do the job first, and if it would, we will tell you and help you build that instead. When an app is the right call, you own the code and the store accounts outright. We work with small and medium businesses across the country and overseas. Tell us what your customers would use an app for, and we will help you decide whether it is worth building.
Terms
App and website words in this post
Tap a term to see what it means.
Native app. An app built for a phone's own system and installed from the App Store or Google Play.
Progressive web app (PWA). A website built so a phone can install it on the Home Screen and use it like an app, with offline use and notifications where supported.
Web push. Notifications sent by a website or web app, after the visitor gives permission.
App Review. Apple's check of every app and update before it appears in the App Store.
Retention. The share of users who keep opening an app over time after installing it.
Cross-platform app. An app built from one shared codebase for both iPhone and Android, still published through both stores.
