Mobile App or Web App? How a Business Should Decide
Most businesses should start with a web app that works well on phones, not with a native mobile app. A native app earns its extra cost when the same people open it often, when it needs phone features a browser can’t reach reliably, or when app stores are where your customers expect to find you. In between sits the progressive web app (PWA): a web app people can install on their home screen, with offline use and push notifications.
Whichever you choose, the app is only the front of the system. Behind it you need the same database, business logic and staff-facing admin screens, and those usually cost more than the app itself.
The short answer
- Web app: one codebase, works on every device, updates instantly, no store fees or review. The right default.
- PWA: a web app that installs to the home screen, works offline and can send push notifications, including on iPhone since iOS 16.4.
- Cross-platform app: one codebase published to both app stores. Good when you need store presence and device features without paying for two apps.
- Native app: separate iOS and Android code. Best performance and device access, highest cost to build and maintain.
- Ask who opens it, how often, and what the phone must do that a browser can’t. The answers usually decide it.
Who opens it, and how often?
Abdulqader Wahiba, founder and CEO of ZAWAT, suggests owners replace “do we need an app?” with three narrower questions.
“Who opens it, how often, and what must the phone do that a browser can’t? If the honest answers are ‘customers, a few times a year, nothing special’, you need a good website, not an app.” — Abdulqader Wahiba
Frequency matters because installing an app is a commitment for the user. A customer who orders twice a year will use your website and will not download anything. A driver who records twenty deliveries a day, or a customer who reorders every week, is worth an installed app, because it saves them time every time they open it.
The four options, compared
| Web app | PWA | Cross-platform app | Native app | |
|---|---|---|---|---|
| How users get it | Open a link | Link, then “add to home screen” | App Store and Google Play | App Store and Google Play |
| Codebases | One | One | One, published twice | Two (iOS and Android) |
| Updates reach users | Immediately | Immediately | After store review | After store review |
| Works offline | Limited | Yes, if designed for it | Yes | Yes |
| Push notifications | Some browsers; not in iPhone browser tabs | Yes; on iPhone once installed | Yes | Yes |
| Deep device features | Limited | Limited | Most | All |
| Store fees and rules | None | None | Yes | Yes |
| Relative cost | Lowest | Low | Medium | Highest |
When a web app or PWA is enough
A web app built to work properly on phones covers most business needs: customer portals, booking, ordering, dashboards, internal tools, approvals and forms. People reach it from a link in WhatsApp, an email or a QR code, with nothing to install.
A PWA adds three things. It can be installed to the home screen and opened like an app. It can keep working with a poor or missing connection, if it is designed for that. And it can send push notifications. Apple’s WebKit team announced in February 2023 that “with iOS and iPadOS 16.4, we are adding support for Web Push to Home Screen web apps”. On iPhone, that applies once the user has added the web app to their home screen.
For staff tools in particular, a PWA is often the best value. You control who uses it, you can show staff how to install it, and every update reaches everyone at once.
When a native or cross-platform app is worth it
Build for the app stores when one or more of these is true:
- Daily, repeated use by the same people, where speed and convenience add up.
- Device features a browser handles poorly, such as continuous location tracking in the background, Bluetooth printers or scanners, or heavy offline work in places with no signal.
- Store presence matters because customers search the App Store or Google Play for businesses like yours.
- Reliable notifications are central to the service, such as delivery updates or appointment reminders.
Cross-platform frameworks let one team publish one codebase to both stores. For most business apps they are the sensible middle path. Fully native development makes sense when performance or device integration is the product, which is rarely true of a business tool.
What the app stores add to the bill
Publishing to the stores brings fees and rules a website does not have. Apple’s Developer Program costs 99 US dollars per membership year. Google Play charges a one-time registration fee of 25 US dollars.
The bigger question is payment. Apple’s App Review Guidelines distinguish two cases:
- Physical goods and services used outside the app, such as a restaurant order or a home-cleaning booking, must be paid for with methods other than in-app purchase, such as Apple Pay or card entry. That means your normal payment gateway; payment gateways in Oman covers which ones integrate.
- Features or content unlocked inside the app, such as subscriptions or premium content, generally must use Apple’s in-app purchase. Apple lists a 30% commission, or 15% under programmes such as its Small Business Program.
The rules differ in some markets, including the United States and the EU, and they change. Apple’s guidelines were last updated on 16 October 2026. Check the current terms before you design a paid feature around them.
Store review also affects how fast you can fix things. A web app update reaches users the moment you publish it. An app update waits for review and then for users to install it.
The part that costs more than the app
Every option needs the same foundation: a server and database, the business rules, connections to your accounting or inventory system, and admin screens where staff manage orders, users and content. That foundation is usually the larger part of the work. It is also why starting with a web app is rarely wasted: if you add native apps later, they talk to the same back end.
Arabic matters here too. Both web and native platforms support right-to-left layouts, but each screen has to be built and tested in both directions. Building bilingual Arabic-English software explains what that involves.
A sensible order for most businesses
- Build the back end and a phone-friendly web app first. It serves every user on every device from day one.
- Make it a PWA if staff or regular customers would benefit from installing it.
- Measure use. How many people return each week? What do they ask for that the browser can’t do?
- Add a cross-platform app only when the numbers and the requests justify it.
This is the order Abdulqader Wahiba recommends to owners who are unsure, because each step stands on its own and nothing built early is thrown away.
Frequently asked questions
What is a progressive web app (PWA)? A web app built so that people can install it on their home screen, use it with a weak or missing connection, and receive push notifications. It is still a website underneath, so it updates instantly and needs no app store.
Do PWAs work on iPhone? Yes. iPhones can add web apps to the home screen, and since iOS 16.4 home-screen web apps can receive push notifications. Some device features remain more limited than in a native app.
Is a cross-platform app as good as a native one? For most business apps, yes: forms, lists, orders, bookings and notifications. Native development is worth the extra cost when performance or close hardware integration is central to what the app does.
Can we start with a web app and add a mobile app later? Yes, if the back end is designed with that in mind, exposing its functions through an application programming interface (API) that a future app can use. That is a decision to make at the start, even if the app comes later.
Do we have to pay Apple a commission on every sale? Not on physical goods or services consumed outside the app; those must use other payment methods. Apple’s in-app purchase and commission apply to digital features and content unlocked inside the app, with different rules in some markets.
Sources: Apple — App Review Guidelines (sections 3.1.1 and 3.1.3(e)) · Apple — Apple Developer Program: what’s included · Google — Get started with Play Console · WebKit — Web Push for Web Apps on iOS and iPadOS (February 2023)
Not sure which one your business needs? ZAWAT builds web applications and the systems behind them, starting with whatever your users will actually open. Book a call.