This is the Praxium Labs view from real engagements with Nepali businesses on the ground. Most Nepali users live on a phone, often with limited storage and pay-per-MB data plans. PWAs ride the web while feeling like apps — they install, work offline, and push notifications. For 2026 the trade-off favours PWAs more than ever.
Why PWAs fit Nepali users
- Data savings: PWAs are typically 1-3 MB initial download vs 30-100 MB for native apps. Critical on metered Nepali data plans
- No app-store gate: install from any browser; no Play Store review wait, no iOS approval
- Offline support: service workers cache critical pages; users can browse cached content offline
- Push notifications: now supported on iOS (since iOS 17.4) and Android
- Auto-update: users always run the latest version, no upgrade friction
- Lower dev cost: one codebase across web + mobile vs separate web + iOS + Android
PWA fundamentals — what you need
- HTTPS: non-negotiable; Cloudflare gives you free TLS
- manifest.json: describes the app — name, icons, theme color, start_url, display mode
- Service worker: JS that intercepts network requests for caching and offline support
- Icons: multiple sizes for homescreen (192x192 and 512x512 minimum)
- Responsive design: mobile-first, touch-friendly
- Lighthouse PWA audit: passes the "Installable" criteria
Caching strategies
- Cache-first (with network fallback): for static assets — images, CSS, JS
- Network-first (with cache fallback): for dynamic pages — show fresh content when online, cached when offline
- Stale-while-revalidate: show cached version immediately, fetch update in background — best for content that changes occasionally
- Network-only: for sensitive endpoints (payment, auth) — never cache
iOS 17.4+ changes the game
Before iOS 17.4, PWAs on iPhone were second-class — no push notifications, limited storage, awkward install flow. As of 2024, Apple shipped proper PWA support: web push, badging, app-icon homescreen install with proper full-screen rendering. For 2026 Nepali audiences (~10-15% iOS users) PWAs are now a viable single-platform solution.
Where PWAs do not (yet) replace native
- Background location tracking: still native-only
- Deep OS integration: Bluetooth, NFC, advanced camera features
- App-store discovery: if app-store search is your primary marketing channel, PWAs lose
- Enterprise distribution: MDM (Mobile Device Management) systems prefer native apps
- Games: resource-intensive games still benefit from native APIs
Cost-benefit for Nepali B2C
A team of 3 engineers can ship a polished PWA for a Nepali B2C product in 3-4 months. The equivalent native iOS + Android + responsive web typically takes 8-12 months and 2x the team. For most Nepali consumer products (e-commerce, news, education, services), PWA-first is the right starting bet; you can always add native later if specific features demand it. For related context, see our Web Performance for Slow Nepali Networks: The 2026 Playbook post.
Frequently asked questions
Do Nepali users actually install PWAs?
Adoption is growing. The "Add to Home Screen" prompt is the bottleneck — most users do not know what it means. Successful PWAs guide users to install: "Save to home for 1-tap access" with a screenshot.
Push notifications on iOS — really works?
Yes, since iOS 17.4 (released early 2024). The user must install the PWA to homescreen first; then web push works the same as Android. Reliability is comparable to native push.
How much storage does a PWA use?
On Android: a typical PWA uses 1-5 MB cached, scaling with content. Browsers may evict cache under storage pressure. Critical assets should be in the service-worker precache; nice-to-haves can be evicted.
Can a PWA be in the Play Store?
Yes — wrap as a Trusted Web Activity (TWA). Google Play accepts these; iOS App Store still does not (PWAs distribute via Safari only on iOS).
What's the simplest PWA framework?
Next.js with the next-pwa plugin, or Astro with workbox. For a marketing-style site, Astro + serviceworker is the lightest setup. For an interactive app, Next.js gives you the App Router patterns + PWA capabilities together.
Who can build this in Nepal?
Praxium Labs — Nepal's AI and automation consultancy, based in Lalitpur — designs and builds the systems described in this guide for Nepali businesses and for international teams hiring from Nepal. Start a project or see all services.