PWA or native? The honest answer for South Africa
Data costs, device spread and offline reality change the maths. When a Progressive Web App beats a native build, and when it doesn’t.
The PWA-versus-native debate usually gets argued on features. In South Africa, the deciding factors are more practical: data costs, the spread of devices people actually own, and how the app gets discovered and installed.
When a PWA wins
If your audience is price-sensitive on data, on a wide range of Android devices, and you need them to start using the product the moment they hear about it, a Progressive Web App is hard to beat. No store download, no 80MB install, instant updates, and it works offline once cached. Share a link, they tap it, they’re in.
For most marketing-led products, content apps, booking tools and dashboards, a well-built PWA is not a compromise, it’s the right answer.
When native earns its keep
Native makes sense when you lean hard on device capabilities, rich push, background sync, Bluetooth, deep camera or sensor work, or when being in the App Store and Play Store is itself a trust and distribution signal your users expect.
It costs more to build and maintain two codebases, so the bar should be a real capability or distribution need, not “apps feel more legit”.
The honest default
Start with a PWA unless you have a concrete reason not to. You’ll ship faster, reach more people, and you can always wrap or rebuild specific surfaces natively once the product has earned it.