On this page
Key takeaways
- A PWA is a website that installs like an app: one codebase, no store review, and it works on iPhone and Android.
- Native Android is worth it when reliable alerts, background work or a Play Store listing matter.
- On iPhone, web push only works after the user adds the web app to their home screen.
- Many businesses are best served by both: native Android for the majority, the PWA for everyone else.
If your customers or staff need an app, you have three realistic options: a progressive web app (PWA), a native app, or both sharing one backend. For many Nepali businesses a PWA is the cheaper and faster start, and a native Android app becomes worth it when you need dependable notifications, a Play Store listing, or features a browser cannot provide. Here is how to decide.
What a PWA actually is
A progressive web app is a website built to behave like an app. Visitors can install it to their home screen, it opens full-screen without browser bars, it can keep working on a poor connection, and it can send notifications. There is one codebase for every device, no app store review, and an update reaches everyone the moment you deploy it.
For a business, that means a lower build cost and no waiting for store approval. For users, it means nothing heavy to download — useful on phones with little free storage, which is common on mid-range Android handsets.
What native gives you that a PWA does not
- A Play Store listing. Many users trust an app they found on Google Play more than a link, and some will only install from the store.
- Dependable push notifications. Native apps receive notifications through Firebase Cloud Messaging even when closed, and Android gives them more control over sound and priority.
- Call-style alerts. A native app can ring full-screen like a phone call, even on a locked screen. A browser cannot.
- Background work and device features. Scheduled syncs, deeper offline storage, Bluetooth and other hardware access are all easier natively.
- A first-class feel. Native navigation, gestures and system integration feel right in the hand.
The iPhone question
In Nepal most people use Android, but iPhone users are often a meaningful share of business owners and managers. On iPhone, a PWA can receive web push notifications only after it has been added to the home screen (iOS 16.4 and later). In an ordinary Safari tab it cannot. So if you rely on notifications, the iPhone experience needs a clear "Add to Home Screen" step, shown at the right moment.
Side by side
| If you need… | PWA | Native Android | Both |
|---|---|---|---|
| Lowest cost and fastest launch | Best fit | Higher cost | Highest cost |
| To reach iPhone, Android and desktop | Yes, one build | Android only | Yes |
| A Google Play listing | No | Yes | Yes |
| Reliable alerts when the app is closed | Good on Android, limited on iPhone | Strongest | Strongest |
| Ring like a phone call for urgent events | No | Yes | Yes |
| Instant updates without store review | Yes | Store review per release | Web part instant |
The "both" pattern, in practice
For our Sintech wholesale platform we built both, deliberately. Dealers — most of them on Android — use a native Kotlin app from Google Play, which gives them reliable order and repair notifications and in-app calls. Dealers on iPhone or a computer use the same features as an installable PWA. Staff use an admin panel that is itself an installable PWA, plus a small Android staff app whose main job is to ring like a phone call when a dealer calls support.
The key decision was that every one of those apps talks to the same API. Business rules — prices, permissions, order statuses — live in one place, so the native app and the web app can never disagree about what an order costs or who may see it. That is what keeps "both" from costing twice as much to run.
A middle path: wrapping the web app
There is a third route that suits many schools, clinics and smaller businesses: wrap the web app in a thin native shell (for example with Capacitor or a Trusted Web Activity) and publish that to Google Play. You get a store listing and native push from one web codebase. We have shipped school apps this way, built from the same code as the school's website. The trade-off is that the experience is still the web app inside, so heavy native features are harder.
What it costs
A PWA is usually priced like a web application, because that is what it is. A fully native app is a separate build and a separate thing to maintain, which is why our mobile app development starts from NPR 150,000. A wrapped web app sits in between. Whatever you choose, budget for keeping the app updated: Google raises its technical requirements every year, and an app that is not maintained eventually drops out of the store.
Where to start
Start with who will use the app and what must happen when they are not looking at it. If the honest answer is "nothing urgent", a PWA is probably right. If missed alerts cost you money — orders, calls, repairs — plan for native Android, and read our guide to publishing on Google Play from Nepal before you start. We are happy to talk it through and recommend the smallest thing that does the job.
Frequently asked questions
Usually, yes. One codebase serves every device and there is no store submission to manage. A native app is a separate build that also needs ongoing updates to meet Google Play requirements.
Yes, on iOS 16.4 and later, but only after the user has added the web app to the home screen. In a normal Safari tab it cannot receive push notifications.
Yes. A web app can be wrapped in a Trusted Web Activity or a framework such as Capacitor and published to Google Play, as long as it meets Play's quality and policy requirements.
Often not at first. Android is the majority platform in Nepal, and iPhone users can be served well by an installable PWA. Build a native iOS app when there is clear demand for it.
- pwa vs native app
- mobile app development nepal
- progressive web app
- android app nepal