"We need an app" is one of the most common things I hear at the start of a project. Sometimes it is exactly right. Sometimes what the business needs is a website that works properly on a phone, and an app would add cost, store reviews and a second product to maintain without giving customers anything they would miss.
Both are built for phones. The difference is whether your customers will install something and come back to it, or whether they arrive from Google, WhatsApp or Instagram, do one thing and leave. This article walks through how I make that call with a client, before any design or quote.
What each one actually is
A mobile website is your website, designed so it reads and works well on a phone. People reach it through a link or a search result. Nothing is installed. Every visit loads the latest version, and Google can index every page.
A mobile app is installed from the App Store or Google Play. It sits on the home screen, can send push notifications, can use the phone's camera, location and storage more deeply, and can keep people signed in for months. It also has to pass store review and be updated as the platforms change.
There is also a middle ground, a web app (sometimes called a progressive web app when it can be added to the home screen). It runs in the browser but behaves more like software: logins, dashboards, forms, data. If you are unsure whether you need a simple site or something more interactive, I covered that split in website or web app.
Start with how often people will use it
The single most useful question is frequency.
- Once or a few times a year: a lawyer's office, a clinic's information pages, a contractor, an event venue. People search, read, call or send a form. A mobile website wins. Asking them to install an app to see your opening hours is friction they will not accept.
- Every week or every month: booking a regular service, reordering supplies, checking an account, ordering food. Here an app starts to earn its place, because staying signed in, saved details and one-tap repeat actions save the customer real time.
- Every day or during work: field staff, drivers, sales reps, technicians. These users install whatever their job requires, and an app built around their workflow usually pays off.
If you cannot name a reason a customer would open it again within a month, start with the website.
Signs you need a mobile app
Customers repeat the same action
Booking a cleaner every two weeks, reordering the same groceries, topping up an account. An app keeps them signed in with their address, preferences and payment method ready, so the repeat action takes seconds. Pro Clean+, a home-cleaning booking app I designed and built, is this kind of product: customers book a clean in a few taps with real open slots, clear prices and photo-based quotes, in English or Arabic.
Notifications are part of the service
"Your technician is on the way", "your order is ready", "your appointment is tomorrow at 10". If timely updates are central to the experience, push notifications from an installed app are the most reliable channel you control. They need to be used carefully, or people turn them off; push notifications users keep turned on covers how. For some businesses, WhatsApp messages do this job without an app at all, which is worth weighing before you decide.
You need the phone's hardware
Scanning barcodes all day, taking many photos and uploading them on a weak connection, tracking location in the background, working offline in a basement or a rural area. Browsers can do some of this, but an app does it more reliably, especially offline and in the background. If your users are in places with patchy coverage, read building apps that keep working on unreliable connections.
Being on the home screen and in the stores matters
For some products, being findable in the App Store and Google Play is part of the marketing, and the icon on the home screen is a daily reminder. A discovery or guide app is a good example. Local Meals, which I built for Order of Malta Lebanon, is an iOS and Android app where locals and visitors find local food vendors and artisans, browse photos and menus, and get directions. Being a real app with a map and a call button suits how people use it on the go.
Signs a mobile website is enough
Most visitors come from search or links
If people find you on Google, open your link from Instagram or receive it on WhatsApp, a website opens instantly with no install step. Every product, service or location page can rank in search. App screens do not show up in Google the way web pages do, so if search traffic is how you win customers, the website is your main asset regardless of what else you build. SEO basics for businesses in Lebanon explains how that works locally.
The job is to inform and convert
Explaining services, showing work, answering questions and getting a call, a booking request or a form submission. A well built website does this completely. Speed matters more than anything here: a slow mobile page loses people before they read your offer.
You are still testing demand
If you do not yet know whether customers want the service, a website (or web app) lets you launch faster, change things daily without store review, and learn what people actually use. You can build the app later around the features that proved themselves. That is often the cheapest route to the right product.
Content changes often
Menus, prices, listings, news. Updating a website is immediate. An app can load content from a server too, so this is not a blocker, but if content is all the app does, a website usually does it better.
What drives the cost difference
I do not quote prices in an article, because the scope decides the number. But the drivers are predictable.
A mobile website is one product on one platform, the browser. A mobile app is usually two platforms (iOS and Android), plus a backend and an admin panel to manage it, plus store listings, review cycles and developer accounts. With React Native I build both apps from one codebase, which helps a lot, but there is still more to design, test and release than a website.
Then there is the ongoing cost. Websites need hosting, security updates and backups. Apps need all of that for their backend, plus updates when Apple and Google change their requirements, new phone sizes and OS versions to test against, and releases through both stores. What app maintenance after launch really involves goes through it in detail.
So the question is not only "what does the app cost to build" but "is the repeat use worth maintaining a second product".
You often need both, and in a specific order
For many businesses the honest answer is: website first, app when repeat use justifies it. The website is how new customers find and trust you. The app is how existing customers come back with less effort.
When both exist, they should share one backend. Customers, bookings, orders and content live in one database, the website and the app read and write through the same API, and your team manages everything from one admin panel. That way nothing gets entered twice and a booking made on the app shows up correctly on the website account page. This is how I structure these projects: a Next.js website and admin, a React Native app, and a backend in Next.js or .NET Core with Postgres, deployed with Docker on a Linux server behind a CI/CD pipeline.
Building the backend properly from the start means adding the app later is mostly new screens, not a rebuild.
A quick decision checklist
Answer these honestly:
- Will a typical customer use it more than once a month?
- Is there a repeat action that saving their details would make much faster?
- Are timely notifications central to the service?
- Do users need the camera, barcode scanning, location or offline work as a core feature?
- Is being listed in the App Store and Google Play part of how people will find you?
- Do you already have customers who would install it, or are you still testing demand?
- Do most new customers find you through Google or shared links?
Mostly yes to 1 to 5 and you already have customers: an app is likely worth it. Mostly yes to 6 (still testing) and 7: start with a strong mobile website or web app, and plan the backend so an app can be added.
Bilingual and regional details
If you serve customers in Lebanon or the GCC, decide early whether the product needs Arabic, English or both. This applies to apps and websites alike, and it is much cheaper to build right-to-left support in from day one than to retrofit it. App store listings also need their own text and screenshots per language. Building bilingual Arabic and English apps and websites covers what doing it properly involves.
Where to go from here
If the checklist points to an app, my mobile app development page explains how I take an app from scope to both stores and keep it running. If it points to a website, website development covers how I build fast, search-friendly sites. If you are not sure, that is exactly the conversation worth having before anything is designed.
Send me a short description of your business, who your customers are, and what you want them to do on their phone. Email hello@eliechaaban.com or use the contact section, and we can work out on a call whether you need an app, a website, or a website now and an app later.