Clients often open with "we need an app". Most of the time a small business needs a good website first, and sometimes a web app (PWA) or a messenger bot covers the rest. Here is the checklist we go through before anyone writes native code.
Three questions that decide it
- How do new customers find you? Search, maps and AI assistants send people to web pages. An app does not show up in those answers, so the website comes first either way.
- How often does one customer come back? Once or twice a year: a website is enough. Every week or month (booking, reordering, loyalty points): an app starts to make sense.
- What would the app do that the site can't? If the honest answer is "nothing yet", wait.
What a PWA can do in 2026
The gap between a web app and a native app is smaller than many clients think:
- Home Screen install on Android and iOS, with its own icon and full-screen window.
- Push notifications on iPhone for web apps added to the Home Screen, since iOS 16.4 (WebKit blog). The user has to add the app to the Home Screen first, and that step needs explaining.
- Offline use through a service worker, enough for a menu, a price list or a booking draft.
Where native still wins: background location, Bluetooth and NFC hardware, heavy camera work, and anything that has to feel exactly like the platform.
The running costs nobody quotes
A native app has costs before the first download:
| Website or PWA | Native app | |
|---|---|---|
| Store fees | none | Apple Developer Program $99 a year, Google Play $25 once |
| Forced updates | browser handles it | Apple: since 28 April 2026 App Store Connect accepts only builds made with Xcode 26 / iOS 26 SDK. Google Play raises the target API level every year |
| Review before release | none | every update goes through store review |
Sources: Apple Developer Programs, Google Play Console Help, Apple upcoming requirements.
So budget at least one technical update a year for a native app, even if you add no features.
A sensible order
- A fast, mobile-friendly website with prices and one-tap contact.
- A Telegram or WhatsApp bot for bookings and repeat orders, if customers already message you.
- A PWA when you need Home Screen presence and reminders.
- A native app when repeat use is proven and you need hardware access or store presence.
We wrote the full comparison table (website vs app vs PWA vs bot, with costs) here: Website or mobile app: what a small business needs first.
What made you choose a PWA over native, or the other way round? Curious what tipped it in real projects.
Top comments (0)