Short answer: If your users mostly work at a desk and the app can run in a browser, a web app is the fastest and most cost-effective solution. If an installable experience on the phone and notifications are enough, a PWA (a web app that can be added to the home screen) is a good middle ground. If the camera, sensors, offline use or a presence in the app stores is critical, you need a mobile app. For many businesses, the most efficient path is to start with a web dashboard and add a mobile app when the need arises.
What's the difference between the options?
| Factor | Web app | PWA | Mobile app |
|---|---|---|---|
| Installation | Not needed; opens from a URL | Added to the home screen | Downloaded from an app store |
| Updates | Instant, for everyone | Instant | App store approval and user update |
| Camera and sensors | Limited | Limited | Full access |
| Notifications | Via browser permissions | Supported (on iOS, once added to the home screen) | Full support |
| Offline use | Limited | Partial | Strong |
| App store visibility | None | None | Yes |
| Development cost | Lowest | Low | Higher |
When is a web app enough?
For work that is mostly done at a computer, such as management dashboards, reporting, accounting and inventory, a web app is the right place to start. A single codebase runs on both computers and phones (with a responsive design), updates reach everyone instantly and no installation is required.
When do you need a mobile app?
- Camera and document scanning: Taking photos, scanning barcodes or documents in the field
- Offline use: Entering data in places with a weak internet connection
- Push notifications: Reliable delivery of task, appointment or approval notifications
- App store presence: Products that serve end users, where being downloadable builds trust
How did we decide in real projects?
- Garaj Defteri: Work orders, invoicing and inventory run in the web dashboard. A separate Android app was developed for the mechanics in the workshop; it reads the vehicle registration document photo to fill in the vehicle form and opens the vehicle's history via a QR code. Camera use and work on the shop floor made the mobile app necessary.
- Bizim Galeri: The system was first built as a web app, and the existing web codebase was then brought to Android with a wrapper app. This put it in the app store without having to build two separate apps.
- FRMNT: As a subscription-based product aimed at end users, it was developed as a mobile app (with Flutter) from the start; in-app purchases and offline tracking required it.
What are the additional costs of a mobile app?
- App store accounts: A one-time developer fee is paid for Google Play, and an annual developer fee for the Apple App Store.
- Review process: Every update goes through app store review; the rules are stricter, especially on Apple's side.
- Two platforms: Instead of writing separate apps for iOS and Android, technologies that ship to both platforms from a single codebase (such as React Native and Flutter) reduce costs.
- Maintenance: Operating system updates and app store policy changes require regular adjustments.
How should you decide?
Start by defining your user: is this an internal tool for your team or a customer-facing product? Then list your needs for the camera, offline use and notifications. If you don't have these needs, starting with a web app saves both time and budget; when the need arises, a mobile app can be added on top of the same backend. For an overview of how the project process works, see our article on how a custom software project works.
Not sure which route to take to bring your app idea to life? With our custom software development service, we review your needs and work with you to choose the right option: web, PWA or mobile.
Sources
Frequently Asked Questions
Yes. A web app with a responsive design works comfortably in a phone's browser, and it can also be added to the home screen as a PWA if desired.
No. With technologies such as React Native or Flutter, apps for both platforms can be built from a single codebase, which lowers development and maintenance costs.
Yes. If the backend (the database and services) is designed properly, a mobile app can be added on top of the same infrastructure later. This is a common and low-risk approach.