Mobile app vs mobile website: when do you really need an app?

"We want an app." It is the most common sentence in a first meeting, and it usually arrives before we know what the client sells. Mobile app vs mobile website deserves a straight answer before you spend anything.

So here is ours: we build apps, it is part of how we make a living, and even so most people who ask for one do not need it. A properly built website that works on a phone does the job for far less, shows up on Google, and needs nobody to install anything.

This post is so you can decide for yourself.

Website vs mobile app: what is the actual difference?

A website opens in the browser. Anyone reaches it from a link, Google, an ad or WhatsApp. No download, no store, and every update reaches everyone at once.

An app is installed from the App Store or Google Play. It sends push notifications, uses the camera and location more deeply, and can work offline. But between you and the customer sits a step called "install the app", and that step loses a lot of people.

In between sits the progressive web app (PWA): a website the customer can pin to their home screen, that opens without the browser bar and can send notifications. Not a fix for everything, but it covers more ground than most people expect.

Aspect	Plain mobile website	Progressive web app (PWA)	Store app
How the customer gets there	Link, Google, ad, WhatsApp	The site, then a home screen icon	Store search, then install
Appears in Google results	Yes	Yes	The store listing only
Notifications	No	Yes, once allowed	Yes, once allowed
Device features	Camera and location while open	Same as the site	Full, including background tracking
Offline	No	The pages you choose	Whatever it is built for
Updates	Instant for everyone	Instant for everyone	A new version through store review
After launch	Hosting, maintenance	Hosting, maintenance	Hosting, maintenance, store accounts and their yearly rules

What a mobile website can do today

Many reasons for "we must have an app" were true years ago and are not any more:

• Notifications on iPhone. Since iOS and iPadOS 16.4, a site added to the Home Screen as a web app can send push notifications, as long as the permission request follows a tap by the user (WebKit blog). Android has had browser notifications for years.
• Apple Pay. It works on websites in Safari, with one-touch checkout (Apple Pay for developers). Fast payment alone is no reason for an app.
• Camera and location. A site can take a photo or document from the camera and read the customer's location for a delivery while it is open.
• A home screen icon. On Android the browser can offer to install the site. On iPhone the customer adds it from the Share button, "Add to Home Screen", and since iOS 16.4 other browsers can do it too.

What stays hard for a website: tracking a driver while the app is closed, hours of offline work, and being found by someone browsing the store. And on iPhone, adding to the home screen is a manual step with no prompt offering it, so do not build your plan on customers doing it.

When an app genuinely earns its place

1. Use is frequent and daily

Delivery orders, transport, a driver app, a field staff app: the customer opens it every day or week, so the home screen icon and the notifications matter. The same goes for a loyalty programme whose customers order weekly.

2. You need the device all day

Barcode scanning through a shift, background location tracking, capturing documents in volume, hours offline. The browser can do parts of this while open, but not reliably across a working day.

3. Notifications are the service

"Your order is on its way", "the driver has arrived". If the notification is the service rather than an extra, the app earns its place. But WhatsApp covers many of these cases without one: Odoo notifications on WhatsApp put the invoice and order status on the customer's phone with nothing to install.

4. You have field staff or drivers

A driver or technician app is not a customer app. An employee uses it all day and needs location, camera and notifications, so here the app is the foundation. We explained in the parts of a delivery app the customer never sees why it is three interfaces, not one.

When it does not

The business and services website

A clinic, an office, a restaurant, a services company. The customer wants to know what you do, where, how much, and how to reach you. That is a website; few people install an app for it, and fewer open it again. Clinics, see the pages that bring patients to a clinic website.

The store that is just starting

Before you have repeat buyers, an app costs you twice: building it, then convincing people to install it. A fast mobile store lets the customer arrive from the ad and buy in the same session.

When the reason is "the competitor has an app"

The competitor may be wrong. Ask how many of their customers actually use it. You usually cannot get an answer, and that is the answer.

When you want to show up on Google

Content that lives only inside an app does not appear in Google results the way web pages do, so it brings no new customer from search. A website does, if it is built properly: see why your website is not on Google.

When the brief is "an app that shows our website as it is"

We hear this a lot: an app that opens the site inside a frame. Apple's review guidelines (section 4.2) require an app to offer features, content and interface beyond a repackaged website (App Store Review Guidelines). So that kind of app risks rejection, and even if it gets through it gives the customer nothing the site does not. For a home screen icon and notifications, a PWA does it without a store.

The difference in cost and time

An app is not a copy of the website. It is two builds (iOS and Android), or one on a shared technology like Flutter (which is how we work), and either way it needs:

• A backend, the same one that serves the website.
• An admin dashboard to run it from.
• Store accounts (Apple and Google) and a review with every update. Apple says it typically reviews at least half of submissions in under 24 hours and 90% in under 48 (App Review), so review is usually quick. What takes days is a rejection, the fix and the resubmission.
• Ongoing maintenance, because the stores raise their requirements every year; an app untouched for a year needs a full update before even a small fix ships.

A website needs only the first two. So the cost difference is not small, and the time to launch differs even more. We broke down what drives the price of a website and mobile app development cost in Saudi Arabia separately, store fees and dated rules included.

Online store: app or website?

A store is a special case, because both sides have a point:

• The website brings the new customer. An ad on Snapchat, TikTok or Google opens a product page and the customer buys in the same session. Send that ad to a store listing first, and you add steps before the purchase.
• The app serves the customer who comes back. A grocery people order from weekly, a points programme, a product that runs out and gets reordered. Here the icon and notification bring the second and third order.

Payment does not settle it: physical goods and services used outside the app go through a normal gateway or Apple Pay with no store commission (see payment gateways in Saudi Arabia). Start with the website; once customers return regularly, the app becomes a loyalty channel on the same store and stock.

How to know whether your customers want an app

Do not ask "would you like an app?"; everyone says yes. Watch what they do:

• How many come back. In Google Analytics or any analytics tool, see how many visitors return and how often one customer orders in a month.
• How many installed the site. With a PWA you can measure who added it to their home screen and how often they open it there. That is the most honest signal.
• What they ask on WhatsApp. If the daily question is "where is my order?", the fix may be an order status message, not an app.
• What repeats. Reordering, booking, topping up. The one action customers take every time is the heart of the app, if its time comes.

The path we recommend to most clients

1. Start with a fast mobile website that does what the customer wants: see, order, book, pay. Make sure it shows up on Google and loads quickly (measure your site's speed yourself).
2. Put WhatsApp in the middle: confirmations, reminders and follow-ups reach the customer without installing anything. That covers most of "we need notifications"; the WhatsApp Business API for shops explains what a store needs from it.
3. Watch usage for two or three months, with the signals above.
4. When you see genuinely repeated use, build the app on the same backend. The site and the system exist; you add the mobile interface.

That way, if you need an app, you build it knowing what people use. And if you do not, you have saved a large sum.

Mobile app vs website: common questions

Doesn't an app look more premium?

What looks premium is a service that works from the first tap. A long install-and-register path impresses less than a site that opens in a second.

Should we build both from the start?

Not at the same time. Start with what brings customers (the website), then what serves repeat customers (the app). The exception is drivers or technicians: their app starts with the site, because the service cannot run without it.

How long does an app take compared with a website?

Clearly longer: it brings a backend, a dashboard, store accounts and review. A business website launches much sooner; an app takes weeks to months depending on its features.

Can I convert my website into an app later?

Yes, and we recommend it. The backend serving the site serves the app too, so the app is a new interface, not a new project. If "convert" means wrapping the site as it is, Android and iPhone differ: Google supports publishing a PWA on Google Play through what it calls a Trusted Web Activity (Chrome docs), while on iPhone a wrapper without real features runs into guideline 4.2.

Is a PWA enough instead of an app?

Often, yes: a home screen icon, a fast start, notifications on Android and iPhone. Not when you need background location, long offline stretches, or an App Store presence because your customers search there.

Which is more secure, an app or a website?

Security lives in the backend, not the interface. Both talk to the same server, where proper permissions, an encrypted connection and regular updates protect the data. An app nobody has updated in a year is not safer than a maintained website.

Will an app sell more than a website?

To customers who already know you and come back, it can, because it sits closer to them. New customers usually arrive from a search, an ad or a WhatsApp link, and those open a website. If most of your sales come from new customers, the website is what sells.

The short version

An app is a tool for a customer who comes back every day, or an employee who works in it all day. A website is a tool for a customer searching for you who wants to reach you quickly. Most small businesses need the second first, and some never need the first.

How we do it

At kerneltics we build both websites and apps. When an app is the right call, we build iOS and Android from one Flutter codebase, publish on store accounts in your name, and hand over the source code, the server and the dashboard. The driver app in our delivery and transport apps solution builds on our work on the Zaiti app; other projects are on our works page. When WhatsApp messages can replace notifications, we run them on K-Message, our WhatsApp platform on the official Cloud API. Not sure where you fall? Book a free consultation: if you do not need an app, we will say so, and it will be the cheapest advice you get this year.