Progressive Web Apps for Nigerian Businesses: App Store Without the App Store

The conventional wisdom about mobile product strategy is that serious products have native apps. The App Store and Play Store are where legitimate software is distributed. Native apps have better performance, better device integration, and better user engagement.

The conventional wisdom was formulated in markets where free app downloads are the primary app acquisition channel and users routinely have 64–256GB of device storage. It does not perfectly describe the Nigerian market.

Nigerian smartphone users — predominantly on Android, predominantly on mid-range to low-end devices — have specific constraints: more limited device storage (32–64GB is common in the mid-market), data sensitivity (downloading a 50MB app costs money and takes time), and selective trust in app store listings from unfamiliar companies.

Progressive Web Apps address these constraints directly. A PWA is a web application that meets specific technical criteria — service worker, web app manifest, HTTPS — that allow it to be "installed" by the browser, appearing on the home screen like a native app. The installation happens from the browser without going through the app store.

What a PWA Actually Delivers

Install to Home Screen

On Android Chrome (the dominant mobile browser in Nigeria), a well-built PWA triggers an "Add to Home Screen" prompt — or the user can manually add it from the browser menu. Once installed, the app appears on the home screen and in the app drawer, launches in a standalone window without browser chrome, and feels like a native app to the user.

On iOS Safari, PWA installation is also supported (through Safari's Share menu > Add to Home Screen). iOS support for PWA capabilities has historically lagged Android, but Apple has significantly expanded support in iOS 16 and 17 — push notifications now work on iOS PWAs, which was a previous significant limitation.

What the install delivers for a Nigerian business: Distribution without the app store infrastructure. No annual developer program fee. No submission and review cycle (which takes days to weeks). No App Store or Play Store 15–30% revenue take on in-app purchases (significant for subscription products). Updates are immediate — the user always receives the current version without download.

Offline Functionality

As covered in the offline-first article, a service worker can cache the application and data, enabling work without internet connectivity. A PWA can be built to the same offline standard as a native app — with an appropriate local database (IndexedDB) and sync architecture.

The offline capability is not automatic. A PWA that has not been explicitly built for offline operation goes blank when the network is unavailable. The service worker and caching strategy must be deliberately designed.

Push Notifications

Service workers enable web push notifications — the same type of notification that a native app sends, delivered to the device even when the web app is not open in the browser. For PWAs installed on the home screen on Android, push notifications work without distinction from native app notifications.

Use cases for Nigerian business PWAs: delivery status updates, payment confirmations, task assignments for field workers, customer support reply notifications. These replace the use cases that previously required a native app purely for the notification capability.

Device Features

Modern PWAs can access camera (QR code scanning, document capture), geolocation (delivery tracking, field activity logging), file system (document upload), and basic sensors. The feature gap between PWA and native has narrowed substantially.

Features that remain native-only or significantly inferior in PWA: background location tracking (for delivery tracking applications), Bluetooth (for POS or IoT integrations), NFC (for payment or identity applications), deep integration with health sensors, augmented reality. If your use case requires any of these, native is likely required.

Performance at Nigerian Network Conditions

A well-built PWA can be faster than a poorly-built native app on Nigerian networks. The relevant performance lever: asset caching.

A native app downloads its binary once and runs it locally. API calls still require network. A PWA built for performance serves its application shell from cache (sub-100ms) and makes incrementally small API calls for data. The First Contentful Paint — the moment something useful appears on screen — is faster for a well-cached PWA on a returning visit than for many native apps on the same network.

Performance targets for a Nigerian-market PWA:

First Contentful Paint < 1.5 seconds on a Slow 3G simulation
Time to Interactive < 3.5 seconds on Slow 3G
Lighthouse PWA score > 90
Offline functionality for core workflows

These targets require deliberate optimisation: code splitting (load only the JavaScript required for the current route), image optimisation (WebP format, lazy loading), appropriate caching strategies, and a minimal initial payload.

The tools: Lighthouse (built into Chrome DevTools) scores your PWA against all criteria and identifies specific failures. Workbox (Google's service worker toolkit) abstracts the caching strategy implementation.

PWA vs Native App: The Decision Framework

The decision between PWA and native app for a new product:

PWA is appropriate when:

Core feature set maps to web capabilities (forms, data display, document handling, maps)
Offline capability is needed but background location and Bluetooth are not
Distribution speed and cost matter (no app store delay or fee)
Cross-platform development budget is a constraint — one PWA codebase reaches all platforms
Your users are primarily Android (PWA implementation quality is higher on Android)
The organisation does not want to manage separate iOS and Android codebases

Native app is appropriate when:

Background location tracking is required (delivery tracking, fleet management)
Bluetooth or NFC integration is required (POS hardware, access control)
Augmented or mixed reality is part of the core value proposition
Camera capabilities beyond basic capture are needed
Deep OS integration (widgets, app shortcuts, Siri/Google Assistant integration) adds material value
A significant majority of your users are iPhone users (iOS PWA capabilities, while improved, still trail Android)

React Native as a middle path: React Native allows writing one application codebase that compiles to native iOS and Android applications. You get native capabilities without maintaining completely separate codebases. For Nigerian businesses that need native capabilities but cannot sustain two separate engineering tracks, React Native is often the correct answer.

The Business Case for PWA in Nigerian Distribution

The distribution advantage of PWAs is most significant for B2B SaaS products targeting Nigerian businesses and for consumer-facing products where app store friction reduces adoption.

Time to first use: A new user clicking a link to a PWA and adding it to their home screen completes the "app install" in under 30 seconds, with zero data download beyond what the website itself requires. The same user downloading the equivalent native app: finds it in the app store, downloads 50–120MB on their mobile data connection, waits for installation. At ₦2,500 per GB of mobile data, a 100MB app download costs ₦250 in data alone. For a price-sensitive user, this is a real barrier.

Update distribution: When you push an update to a PWA, every user receives it on their next visit — no download required, no "please update your app" notifications, no split user base running old and new versions. This is particularly valuable during active product development phases.

For field worker applications: A company deploying a field data collection or inventory app to 50 warehouse or field staff can deploy a PWA with no IT overhead. Send the URL, the user adds it to their home screen. No MDM, no app distribution software, no corporate Play Store account required.

The limitation to be honest about: PWAs are less discoverable than native apps for companies relying on organic app store search. If your growth strategy depends on users finding you in the Play Store or App Store, a native app provides a distribution channel that a PWA does not. For businesses with existing customer relationships deploying tools to known users, this limitation is irrelevant.

Offline-First Applications for Nigerian Users — Building for unreliable connectivity
Performance Optimisation as Revenue Strategy — How web performance drives business outcomes
Why We Build on the Edge: Cloudflare Workers in Africa — Edge computing for African latency challenges