PWAs in Africa: an installable app with no store, working on 3G and offline

Many Senegalese businesses assume they need "an app on the Play Store". Often, what they actually need is a PWA. A Progressive Web App is a modern website that behaves like an application: it installs on the home screen, works offline, sends notifications, and launches full-screen with no browser bar. All of this without going through a store, and at a fraction of the cost of a native app.

In a context of unstable mobile networks and entry-level phones, a PWA is not a gimmick: it is frequently the most pragmatic solution.

What a PWA actually is

A PWA rests on three technical building blocks. The manifest describes the application (name, icon, color, full-screen mode) so the phone can install it. The service worker is a small program running in the background that intercepts network requests: it is what enables caching and offline operation. Finally, HTTPS is mandatory for security reasons.

For the user, the experience is simple. They visit your site, a banner offers "Add to home screen", they accept, and an icon appears just like any other app. On the next launch, the app opens instantly, even with no connection for pages already visited.

The difference from a native app

A native app (Android or iOS) is written specifically for each platform, distributed via the Play Store or App Store, and installed as a full-fledged piece of software. It accesses every phone feature and offers the best performance for heavy uses (3D games, video editing).

A PWA is an enhanced website. It accesses most common features (camera, geolocation, notifications, local storage) but not all of them. In exchange, it installs in two seconds, weighs only a few hundred kilobytes, updates automatically, and runs on both Android and iOS from a single codebase.

Why PWAs make sense in Africa

Unstable networks

On the continent, connections constantly drop between 4G, 3G and even EDGE, and cut out regularly. An app that demands a permanent connection becomes unusable. A PWA service worker caches pages, images and data: your catalogue, your prices, your content stay available even in an elevator or a rural area. When the network returns, the app syncs.

The cost of mobile data

Data plans remain expensive relative to purchasing power. A well-built PWA loads once then serves from cache, saving the user megabytes. A native app instead forces an initial download of 20 to 80 MB, often seen as off-putting.

Limited phone storage

Many users have phones with 16 or 32 GB of storage that fills up fast. They uninstall apps to free up space. A PWA takes up negligible room and almost never gets uninstalled for that reason.

The store barrier

Installing an app via the Play Store requires a working Google account, data credit, and the patience for a download. Many give up along the way. With a PWA, all it takes is a link shared on WhatsApp: one tap, and the user is in the app.

Use cases where PWAs shine

• Commerce and catalogues: a store that wants to be browsable offline and installable with no friction.
• Internal tools: delivery tracking, field order-taking by sales reps, clock-in.
• Media and content: a magazine or news site that wants loyalty without paying the store tax.
• Services and booking: appointment scheduling, case tracking, customer portal.
• Events: schedule, ticketing, maps, all available even in a venue with no network.

Mini case study: DiamLivraison

DiamLivraison, a meal delivery service in Dakar, wanted to equip its couriers with an order-tracking tool. A native app would have been expensive and required installing on each phone, across a wide range of Android models. We delivered a PWA: couriers open a link, add the app to their home screen, and receive orders. The service worker keeps the list of active runs even when a courier crosses a dead zone; status updates queue up and send the moment the connection returns. The result: zero installations to handle on the support side, instant update rollout across the whole fleet, and a tool usable even in poorly covered neighborhoods.

The limits to know

A PWA is not magic. On iOS, support remains more restricted than on Android: some APIs (full push notifications, access to certain sensors) arrived late and remain partial. For intensive hardware use (advanced Bluetooth, complex NFC, heavy video processing), native keeps the edge. Finally, a PWA does not appear in stores, which can be a drawback if store discovery matters to you, even though a PWA can now be published on the Play Store via a TWA wrapper.

The right reflex is to ask: do I need store visibility and advanced hardware features, or do I need a lightweight tool, installable with no friction, that works on poor networks? In most SME projects, the second answer wins.

What it costs

The big economic advantage of a PWA is that a single codebase covers all devices. Indicative ranges in Senegal:

• Showcase or catalogue PWA: 600,000 to 1,500,000 FCFA.
• Business PWA with a logged-in area and offline sync: 1,800,000 to 4,500,000 FCFA.
• Complex PWA (back-office, multi-role, integrations): 5,000,000 FCFA and up.

For comparison, an equivalent native app, built for both Android and iOS, generally costs two to three times more, not counting developer account fees and the maintenance of both platforms.

How implementation works

Step 1: offline-first design

We decide upfront which data must stay available without a network and which can wait. This design decision shapes the whole architecture.

Step 2: development and service worker

We build the interface, then configure the service worker to cache the right elements and manage the queue of actions performed offline.

Step 3: testing in real conditions

We test by throttling the network, cutting the connection, on real entry-level phones. Testing only on a recent iPhone over office Wi-Fi is the classic mistake that hides every field problem.

Step 4: launch and installation

We deploy on an HTTPS domain, verify the install banner, and prepare a simple onboarding message to show users how to add the app to their home screen.

Pitfalls to avoid

The first pitfall is caching everything blindly, which fills the phone and serves stale data. The second is neglecting the update strategy: without care, users stay stuck on an old cached version. The third is promising offline support without truly testing it under a network cut. The fourth is copying native-app logic without rethinking the web ergonomics. A successful PWA is conceived as a PWA, not as a site sprinkled with features.

FAQ

Does a PWA work on iPhone?

Yes, it installs and works on iOS, but with a few limitations compared to Android, especially on push notifications and access to certain sensors. For most everyday uses, the experience remains very good.

Can my existing site be turned into a PWA?

Often yes, if the site is technically sound. We add the manifest, the service worker and the caching layer. If the site is old and poorly structured, a partial rebuild is sometimes more cost-effective than patching.

Does a PWA really work without a connection?

It works offline for everything cached: previously visited pages, the catalogue, content meant for offline mode. Actions requiring the server (payment, submission) queue up and send when the network returns.

Do I need to publish it on the Play Store?

Not required: the strength of a PWA is precisely install-by-link. If store visibility matters, it can be packaged for the Play Store via the TWA technology.

How long does it take to build a PWA?

A showcase PWA ships in three to five weeks. A business PWA with a logged-in area and offline sync generally takes two to four months depending on complexity.

Let's talk about your project. If you are torn between a native app and a PWA, we help you decide based on your real needs and budget. Message us on WhatsApp +221 77 596 93 33.