PWA or Native App: Which Fits a Small Business?
Short answer: A progressive web app is a website that can be added to the home screen, work offline in part and send notifications, and it costs much less to build than separate iOS and Android apps. It is enough for ordering, bookings, loyalty cards and staff checklists when customers mainly need quick access and a few reminders. Choose native apps when you need deep device features, a presence in the app stores, or reliable background work. On iPhone, a progressive web app has real limits, and those limits should decide the question more than the build cost does.
What a PWA actually is
A progressive web app is a normal website that uses newer browser features. It has a manifest file that gives it a name, an icon and a display mode, so it can open full-screen from the home screen. A service worker lets it store files and some data, so pages load quickly and parts of the app can work without a connection. It can also ask permission to send push notifications.
Nothing about a PWA is hidden from your customers. They reach it through a web address, and they can share links to it. That makes it easy to find, and it is also why it feels less like an app to some people.
Comparing the options
| Factor | Progressive web app | Native iOS and Android apps |
|---|---|---|
| Install | Added from the browser, no store | Downloaded from the App Store and Google Play |
| Store presence | None, unless wrapped in a store app | Listed, searchable, reviewed |
| Push notifications | Supported, with platform rules | Supported, with full control |
| Offline use | Possible for cached pages and data | Full, with local storage |
| Device features | Limited, varies by platform | Full access, such as Bluetooth and background tasks |
| Build and upkeep | One codebase, usually lower cost | Two platforms or a shared framework, higher cost |
| Updates | Immediate, on the next visit | Through store review and user updates |
The table simplifies a lot, and the details change as browsers and operating systems add features. Check the current support on the platforms your customers use before you commit.
A decision grid for common small-business apps
Most small businesses build one of three things first. The grid below shows where a PWA usually fits.
| Use case | Best first choice | Why |
|---|---|---|
| Takeaway or retail ordering | PWA | Customers order once or twice a week, and a fast website with reminders is enough |
| Appointment booking for a salon | PWA | Booking happens in a browser, and reminders can go by email or messaging |
| Loyalty card with stamps | PWA or wallet pass | Fast to show at the counter, and easy to update |
| Field staff app with photos and GPS | Native | Needs camera, location and reliable background work |
| Delivery driver app | Native | Needs background location and strong offline sync |
If your first version is a booking page or an order form, a PWA is the sensible starting point. If the core of the product depends on the camera, Bluetooth or background tasks, plan for native from the start.
iOS limits to know
Apple's web platform has improved, but a few limits affect small businesses directly. Push notifications for a web app on iPhone generally require the user to add the app to the home screen first, and the permission prompt appears only after that step. Some background behaviour, storage rules and device features are more restricted than on Android or on a native app. Test the features you depend on in the browser on a real iPhone, not only on a desktop.
These limits do not rule out a PWA. They do mean that a reminder-based service works well as a PWA, while a service that depends on immediate background alerts needs native.
A worked example: a bakery's ordering system
Imagine a bakery with three shops that wants customers to order cakes for collection. Its needs are a menu, an order form, a payment step, reminders when the cake is ready, and a page for the staff to see the day's orders.
A PWA handles all of that. Customers open the bakery's address, add it to the home screen, and receive a notification when the order is ready. Staff use the same site on a tablet at the counter. The bakery saves the cost of a second codebase and the store review cycle for each update to the menu.
The bakery would need a native app only if it wanted in-shop features such as a loyalty scan through the phone's camera with background wake-ups, or a listing in the stores as a discovery channel. Neither is essential for the first version.
Steps to choose
- Write down the three things a customer must do in your app.
- Write down the three things a staff member must do.
- For each item, note whether it needs camera, background work, Bluetooth or precise location.
- If none of those is needed, build a PWA first and measure use.
- If one is needed, check whether the feature can be done with a web API that works on both iPhone and Android.
- Test the chosen approach on real devices with the features your customers will use.
Upgrading later
A good PWA is a useful stepping stone. Build the core flows on the web first, keep the logic in your backend, and keep the interface components reusable. If the business later needs a store presence or deeper device features, you can wrap the same backend in native shells without rebuilding everything. Keep that path in mind from the first design, because it is much harder to add later.
FAQ
Will a PWA appear in the App Store?
Not as a PWA by itself. Store listings usually require a native wrapper or a native app, which has its own review process. Check the current store rules for the approach you are considering.
Can a PWA send push notifications?
Yes, on supported platforms and browsers, once the user grants permission. On iPhone the user usually has to add the web app to the home screen first, so plan the onboarding step.
Is a PWA good enough for payments?
Yes, for most small businesses, using a standard payment provider's checkout. The payment flow itself is often handled by the provider, so you still need to check its requirements for the platforms you support.
How do I know if a PWA will be enough for my customers?
Launch a simple version, measure how many people add it to the home screen, and ask whether they miss anything. If they keep asking for a feature that needs deeper device access, you have your answer.
If you would like help deciding between the two, tell us what your customers need to do in the app and what your staff need, and we will talk it through with you: get in touch.