Web app vs native app: the decision in plain words
In plain words: a web app is software your users open with a link, in any browser, on any device. A native app is software they download from the App Store or Google Play. The web app costs USD 900 when I build it and ships in 2 to 3 weeks; a native app costs approximately USD 30,000 to 150,000 at market rates and ships in months, twice, because iOS and Android are separate builds. For most business ideas, the honest recommendation is the first one, and here is how to know if you are the exception.
The test: what must your app do?
Write down the actions your app performs. Log users in, show them their data, let them book, buy, upload, scan, message, get notified? Every item on that list works in a browser today. Cameras, GPS, QR scanning, file uploads, payments, push notifications: the modern web platform handles all of it, and a web app can be added to the phone’s home screen with its own icon, opening full screen like any other app.
The genuine native cases are narrow: apps that must work fully offline with heavy data sync, games pushing serious graphics, products built around deep hardware access, or businesses whose acquisition strategy is literally being discovered in app store searches. If your list has none of those, native buys you nothing but cost.
What each path costs, honestly
Native means two codebases, two app store review processes, developer accounts, and every future feature built and tested twice. That is why market quotes start around USD 30,000 and climb, and why native maintenance bills stay heavy forever.
A web app is one codebase reaching every device instantly. Mine cost USD 900 fixed, with 2 revision rounds included, hosting and domain billed at cost in your name, and updates deployed the moment they are ready, with no store review standing between you and your users. Complex multi-role products move to the custom system tier from USD 2,500.
Proof this holds under pressure
The systems I run in production for SOMOS DER, an event production company with more than 150,000 attendees, are all web apps doing jobs people assume need native. PASE (pase.somosder.ar) scans QR accreditations at event doors using the phone camera. At the Cerro Catedral ski resort, skiers buy their photos from the slopes at fotos.somosder.ar. Staff on a mountain and lines at a venue door are hostile conditions, and the browser handles them.
The middle path people forget
If you truly need a store presence later, a well-built web app can be wrapped into a store app afterwards, reusing nearly everything. Starting native, by contrast, forecloses the cheap path permanently. Start web, earn the evidence, and let real usage justify any native investment. The cost side of this decision is expanded in how much an app costs.
Frequently asked questions
Do push notifications work on web apps?
Yes, on both Android and iOS, once the user installs the web app to their home screen and accepts notifications. For messaging-heavy products, WhatsApp integration is often the better channel anyway, and I build automations and bots from USD 300.
Will users take my product less seriously without an app store listing?
Users take products seriously when they work instantly. A link that opens in one tap converts better than a store detour that loses a share of users at the download step. Distribution by link is a feature, not a compromise.
Can a web app work offline?
Partially, yes: caching lets a web app open and show data without a connection, and sync when it returns. Fully offline-first products with heavy local data are one of the few legitimate native scenarios.
What if investors or partners expect a native app?
Show them the math and the working product. A USD 900 web app in users’ hands in 3 weeks is a stronger position than a USD 60,000 native build arriving in two quarters.
Describe what your app must do and I will tell you which one you need: Message me on WhatsApp and you will have a written price and delivery date within 48 hours.