Most small businesses that come to us asking for "an app" don't need a native one yet. A fast, installable web app reaches the same phone, skips two separate app-store review cycles, and updates the moment we publish instead of the moment a customer remembers to update it. We build these in Flutter specifically so that if the business does outgrow a web app later, it becomes a native iOS and Android app without starting the codebase over — an upgrade, not a rewrite.
The conversation usually starts backwards: a founder assumes "real" means "in the App Store," prices out what feels like three separate builds — iOS, Android, and the web presence they'll want regardless — and only then asks whether any of it needs to be native at all. Flipping that order, starting from what the app must actually do rather than where it must appear, is almost always cheaper and faster to ship.
When a web app is genuinely enough
Staff scheduling, a booking form, an order dashboard, a loyalty card, a simple customer portal — none of these need offline storage or hardware access, and a browser already reaches every phone a customer owns without asking anyone to trust a download first. For a business validating an idea, or one whose "app" is really an internal tool used by five staff on WiFi, a web app is the whole answer, not a stopgap on the way to a "real" one.
When native is worth the extra build
Native earns its cost when the job genuinely needs something a browser can't reach: offline data entry for staff working in basements, lifts, or patchy rural coverage; background location or Bluetooth hardware access; or daily push-driven engagement where every missed notification is a missed booking. A consumer loyalty or rewards app competing for space on a crowded home screen is another real case — but it's a smaller list than most first conversations assume, and it's worth pricing honestly against what a web app already covers.
Once it's clear which side of that line a project sits on, briefing the build itself is a separate step — our guide to briefing a developer covers what we actually need from you to scope it properly, native or not. And whichever you start with, it's covered the same way under our app development work.
Frequently asked questions
Do I need a native app to look credible to customers?
No. A well-built, installable web app looks and feels the same as a native app on a customer's home screen — icon, full-screen launch, no browser bar. Credibility comes from the app working well, not from which store it was downloaded through.
What's the actual difference between a web app and a native app?
A web app runs through the browser engine already on the phone and installs from a link, no store review. A native app is compiled for iOS or Android specifically, gets access to hardware a browser can't reach (background location, Bluetooth, some camera features), and is distributed through the App Store or Play Store, each with its own review process and update cycle.
Can a web app send push notifications?
On Android, yes, and reliably. On iOS, only since Safari added web push for installed web apps in iOS 16.4 — it works, but with more limitations than a native app's notification permissions. If push-driven re-engagement is core to the product, that gap is worth weighing.
Why build in Flutter instead of separate iOS and Android apps?
One Flutter codebase compiles to iOS, Android, and web, so a business that starts with a web app and later needs a native one isn't starting over — the same codebase grows into it. Two fully separate native codebases mean double the review cycles, double the bug fixes, and double the ongoing maintenance for a small business that usually doesn't need two teams doing that work.
How do I know if my business needs offline access?
Ask where the app will actually be used. A delivery or field-service app used in basements, lifts, or rural coverage gaps needs to keep working and sync later — that's a genuine offline requirement. An order dashboard used at a desk with WiFi almost never does, no matter how the pitch is framed.