The website vs mobile app first question comes up in almost every early strategy conversation I have with business owners, and it is almost always framed the wrong way. People ask it as a prestige question. A mobile app sounds serious. A website sounds like the minimum. So they want the app.
The honest answer is that most small and mid-sized businesses asking for an app actually need a fast, well-built mobile website. Not because the app is impossible, but because they have not yet earned the reason to build one.
Deciding between a website vs mobile app first is not about what looks impressive in a pitch deck. It is about one behavioral fact: how often will the same person come back?
The rule: apps earn their place with weekly returns
Here is the filter I use, and it cuts through most of the confusion.
Build a website when people find you occasionally. Build an app when people return weekly.
An app lives on someone's home screen. That real estate is expensive attention. You only deserve it if users open it often enough to remember it exists. Food delivery, banking, daily logistics, fitness tracking, these earn a spot because people return constantly.
Now think about the businesses that ask me for an app: a wedding photographer, a furniture maker, a boutique hotel, a B2B supplier. Their customers buy once or a few times a year. Nobody keeps a wedding photographer's app on their phone. They will Google you, look once, and decide. That is a website job.
Ask yourself honestly: after the first purchase, how many days pass before that same customer needs you again? If the answer is measured in months, an app will sit unused, and the app stores will eventually flag it for inactivity.
The real cost gap nobody mentions
The build cost is only half the story. The maintenance cost is where apps quietly punish underprepared businesses.
Here are realistic ranges for the Indonesian market as of early 2023, for a small to mid-sized project.
| Path | Typical build cost | Ongoing cost |
|---|---|---|
| Good mobile website | 15M to 60M rupiah | Hosting plus occasional updates |
| Progressive web app | 30M to 90M rupiah | Similar to a website |
| Native mobile app (iOS + Android) | 120M to 400M rupiah and up | App store fees, OS updates, two codebases |
A native app is not a one-time expense. Apple and Google update their operating systems every year, and an app that worked last year can break or get delisted if you do not maintain it. You are also paying for two platforms, iOS and Android, each with its own quirks. Many businesses budget for the build and forget the true cost of software maintenance, which is exactly where app projects tend to rot.
If a business cannot commit to that ongoing spend, an app is not a strategic move. It is a liability with a launch party.
The middle path: progressive web apps
There is an option most owners have never had explained to them, and it solves this dilemma more often than not: a progressive web app, or PWA.
A PWA is a website built to behave like an app. It runs in the browser, but it can:
- Be added to the home screen with an icon
- Work offline or on poor connections
- Send push notifications, on supported platforms
- Load fast and feel app-like
You build it once, using web technology, and it works everywhere. No app store approval, no two codebases, no annual OS-update scramble. For a business that wants an app-like experience but does not yet have proven weekly usage, a PWA is often the smart first step. You get most of the feel at a fraction of the cost and risk.
I have steered several clients toward a PWA precisely to test demand cheaply. If usage climbs and people genuinely return every week, you now have real evidence to justify a native app later. You are letting behavior make the expensive decision, instead of ego making it upfront.
A simple decision framework
Run your idea through these questions in order.
- Do customers interact with you weekly or more? If no, build a website or PWA. Stop here.
- Do you need hardware features like camera, GPS, or offline use that a browser handles poorly? If yes, an app moves up the list.
- Can you fund yearly maintenance across two platforms? If no, do not build native yet.
- Are you trying to test an idea or serve proven demand? Testing means web or PWA first. Proven, high-frequency demand can justify native.
Most businesses stop at question one, and that is correct. The app can come later, once the numbers earn it.
Practical takeaway
Do not let prestige decide your first build. The website vs mobile app first choice comes down to frequency of return, not how modern it sounds.
If your customers show up occasionally, build an excellent mobile website. If you want something app-like without the native cost, start with a PWA and let real usage tell you whether a native app is worth the commitment. Reserve the full app build for when people genuinely come back week after week, and when you can fund its long life.
Spend where behavior justifies it, not where your competitors' shiny app makes you anxious. If you are still deciding whether you even need a digital front door yet, these 5 signs your business needs a website are a good gut check. And if you want help matching the build to your actual usage numbers, that is the kind of decision I work through with clients as a technical partner.