If your business needs a mobile app, the first quote you receive will probably stop you in your tracks. Native iOS and Android development costs between R120,000 and R500,000 for a decent build, and that figure does not include App Store submission fees, ongoing maintenance, or the separate codebase required if you want to cover both platforms. For most South African SMEs, that conversation ends before it begins. Progressive web apps exist specifically to solve this problem, and they do it without the trade-offs most business owners expect.
The mobile reality for South African businesses
Datareportal's 2025 digital report confirms what most business owners already sense: over 70% of internet access in South Africa happens on a mobile device. Your clients are not sitting at desks. They are browsing during lunch breaks, comparing your pricing on the way to a meeting, and making purchasing decisions from a screen that fits in a pocket. If your current web presence delivers a slow, pinch-and-zoom experience on a smartphone, you are losing business every day, not because your product is wrong, but because the experience fails before the product gets a chance.
A mobile-first approach to web design addresses part of this. A responsive website that adapts to different screen sizes is better than nothing. But a responsive website is not an app. It does not sit on the home screen. It cannot send push notifications. It does not work without a reliable internet connection. These are the gaps that keep businesses from building genuine mobile engagement, and they are precisely the gaps a progressive web app fills.
The businesses most affected are service businesses, retail brands, and professional practices where repeat clients are the backbone of the revenue model. A client who installs your app to their home screen is a client who does not need to search for you next time. That is a real commercial difference, and it compounds with every returning client.
What is a progressive web app?
A progressive web app, or PWA, is a web application built with modern browser standards that behaves like a native app on any device. When a user visits your PWA in their browser, they are prompted to install it to their home screen. From that point forward, it launches like an app: without a browser address bar, without the delay of a full page reload, and in many cases without any internet connection at all.
The distinction that matters most for business owners: a PWA is a single codebase. You do not build separately for iOS, Android, and web. You build once, and it works everywhere. That is the core reason the economics are so different from native development, and why businesses that previously could not afford a mobile app are now building them.
Service workers: the offline engine
The technical foundation of a PWA's offline capability is the service worker, a background script that runs independently of the main browser thread. The service worker intercepts network requests and serves cached versions of your app's key content when connectivity drops. In South Africa, where load shedding disrupts mobile data towers and variable bandwidth is a daily reality for millions of users, offline capability is not a premium feature. It is the difference between a client completing a booking and abandoning the process entirely.
The web app manifest
The manifest file is what makes installation possible. It tells the browser what your PWA is called, what icon to display, how the screen should be used, and whether to show a browser address bar. When a user opens your PWA, their browser reads the manifest and presents an "Add to home screen" prompt. After installation, your app launches in a standalone window indistinguishable from a native app. The icon, splash screen, and name you define are what the client sees on their home screen every time they return.
HTTPS as a baseline requirement
PWAs require a secure HTTPS connection. This is a non-negotiable technical requirement, which also means every properly built progressive web app carries the security signals that search engines and browsers expect. For any business still running on an unencrypted HTTP connection, building a PWA resolves a foundational credibility issue at the same time as the mobile capability.
How PWAs compare to native apps and mobile websites
The comparison between PWAs, native apps, and mobile websites is often framed as a trade-off between cost and capability. Here is the honest breakdown of where each approach wins and where each falls short:
- Cost: A well-built PWA typically costs between R60,000 and R180,000. A native iOS and Android app covering both platforms typically costs between R250,000 and R600,000, with ongoing maintenance costs on top. A mobile-responsive website is cheaper upfront but does not deliver an app experience.
- Platform coverage: A PWA works on iOS, Android, Windows, and macOS from a single codebase. A native app requires separate builds, separate teams, and separate update cycles for each platform.
- Distribution: PWAs are installed directly from the browser. There is no App Store approval process, no 30% transaction commission, and no waiting 5 to 10 days for a review that may require changes before approval.
- Offline capability: Both native apps and well-built PWAs can work offline. For the vast majority of business use cases, a properly built PWA delivers a comparable offline experience to a native app.
- Push notifications: iOS support for PWA push notifications was added in iOS 16.4, which means virtually all current devices on both major platforms now support them without requiring a native app.
- Performance for complex applications: High-performance gaming, augmented reality, and applications requiring deep device hardware access still favour native development. For bookings, catalogues, portals, field data capture, and service management, a PWA performs comparably in almost every respect.
The realistic conclusion for most South African businesses: if your use case is repeat-client engagement, bookings, service workflows, or e-commerce, a PWA delivers 90% of the native app experience at 30% to 40% of the cost.
Where progressive web apps work best: real business use cases
Service businesses with repeat clients are the clearest example of where a PWA delivers genuine commercial value. A cleaning company, logistics provider, or healthcare practice where the same clients interact multiple times a month benefits from an installable, home-screen experience. If your app is on the client's home screen, the next booking happens without a Google search and without a competitor appearing between you and the client. A custom web application built as a PWA covers this use case completely, at a cost that is realistic for a growing SME rather than requiring enterprise-level investment.
Retailers and product businesses are another strong fit. An e-commerce PWA with offline product browsing, fast checkout, and push notification support for promotions or order updates performs at a level that was previously only achievable with a native app. Critically, every product page in a PWA is a crawlable URL that search engines index, which a native app cannot provide. You gain the mobile experience and the search visibility in a single build. The hidden costs of off-the-shelf e-commerce platforms often make a custom PWA the better long-term investment for businesses beyond a certain scale.
Field teams and operational workflows represent a third strong use case. Businesses that send staff to sites, including surveyors, safety inspectors, and maintenance teams, benefit from a PWA that captures data and works without connectivity, then syncs when signal returns. Custom software built as a PWA for this use case replaces paper forms and spreadsheet workflows at a fraction of the cost of a native solution, and it works identically on every staff member's existing device without requiring a specific operating system version.
The SEO and GEO advantages of a progressive web app
Progressive web apps carry real search optimisation benefits that go beyond mobile experience. Because a PWA is indexed by search engines as a website, every page of your application earns search ranking. This contrasts sharply with native apps, which are largely invisible to Google. A PWA means your content works for your business in search results while simultaneously delivering an app experience to users who arrive. You do not have to choose between discoverability and experience.
Speed is a major SEO ranking factor, and PWAs are structurally built for it. Served via a modern edge network with a service worker caching key assets, a well-built PWA regularly achieves Core Web Vitals scores that outperform the equivalent traditional website. Website speed directly impacts conversion rates, and the technical architecture of a progressive web app is designed to win on this metric. Google's own data shows that a one-second improvement in page load time can lift conversions by up to 7%.
On the GEO side, generative engine optimisation is becoming a genuine business priority as AI-powered search changes how clients discover service providers. The structured, well-indexed content within a PWA is accessible to AI search engines in ways that content inside a native app is not. Understanding the difference between SEO and GEO is increasingly important for South African businesses competing for discovery in AI-generated answers, and a PWA positions you to benefit from both channels simultaneously.
What a well-built PWA actually requires
Not every PWA is built equally. Many developers claim PWA support but implement only a token service worker that caches almost nothing useful. These are the five things that separate a properly built PWA from one that just passes a checkbox:
- Genuine service worker implementation. A real service worker caches the application shell, key data, and the critical user flows your clients actually use offline. A basic implementation that only caches the homepage is not an offline-capable PWA in any meaningful sense, and it will not perform under real South African network conditions.
- Fast initial load. The PWA promise falls apart if the first load takes 8 seconds on mobile data. Proper code splitting, image optimisation, and edge delivery are required to make the initial experience fast enough that users install rather than bounce.
- Push notification infrastructure. Sending push notifications requires a server-side notification service and user permission management. This needs to be designed from the start, not retrofitted after the app is built and live.
- iOS-specific testing. Safari's PWA support has historically lagged behind Chrome. A competent build requires explicit testing on iOS devices, not just Android, and specific workarounds for Safari limitations that still exist in the current version. An Android-only test is not enough.
- Installed experience quality. The app manifest, icons, splash screen, and standalone display mode all need precise configuration. A PWA where the installed experience looks broken or unbranded on the home screen defeats the entire purpose of building one. The installed experience is often the first impression a returning client has of your business.
How CodeLab One builds progressive web apps
At CodeLab One, we build PWAs as mobile applications for businesses that need serious mobile presence without the cost and complexity of maintaining separate native codebases. Our standard approach uses Next.js on the front end, served via Vercel's global edge network, backed by Supabase for real-time data and authentication. This combination consistently delivers Core Web Vitals scores in the top tier for our clients' categories and works reliably across iOS and Android without the fragmentation that affects lower-budget builds.
Designing for South African conditions is built into our process from the start, not added as an afterthought. Load shedding, variable mobile bandwidth, and mobile-first users are the baseline assumptions we work from. A PWA we build for a Johannesburg service business is tested under constrained connectivity, with service workers configured to cache what that specific business's clients actually use, not just the generic application shell that satisfies a Lighthouse score.
Where a client's business case genuinely requires native development, we say so. If the requirement is for deep device hardware integration, complex background processing, or App Store discoverability as a primary acquisition channel, those are legitimate reasons to build native. For every other use case, a PWA is almost always the better commercial decision. You get the experience your clients expect at a cost that leaves budget for the features and marketing that actually grow the business. Explore our full range of business technology services to understand how a PWA fits into a broader digital strategy for your business.
Frequently asked questions about progressive web apps
What is the difference between a PWA and a mobile-responsive website?
A mobile-responsive website adapts its layout for different screen sizes. A progressive web app goes further: it can be installed to the home screen, works offline, sends push notifications, and loads with app-like speed. They use the same underlying web technology but deliver a fundamentally different user experience. If your website is responsive but clients are not returning to it regularly, a PWA is often the missing layer between a website and a genuine mobile presence.
Can a PWA be listed on the App Store?
Standard PWAs are installed directly from the browser, not from the Apple App Store or Google Play Store. On Android, PWAs can be packaged using a Trusted Web Activity wrapper and submitted to the Play Store, but most businesses do not need this. Direct browser installation avoids the submission process entirely and puts the app in the client's hands faster. If Play Store discoverability is a genuine requirement, a native build is worth considering for that reason specifically.
How long does it take to build a PWA?
A straightforward business PWA with a catalogue, booking flow, and push notification support typically takes 8 to 14 weeks to build and test properly. A more complex platform with real-time data, offline sync, and a custom back-end may take 16 to 24 weeks. The scope of the features required drives the timeline, not the technology itself.
Will a PWA work on older smartphones?
Progressive enhancement is a core principle of PWA development. Users on older devices or older browsers receive a fully functioning website experience. The app-specific features such as installation prompts, offline mode, and push notifications activate only on devices and browsers that support them. Nobody is left with a broken experience, which makes PWAs a safer investment than a native app that simply fails to install on unsupported hardware.
Is a PWA as secure as a native app?
In most business contexts, yes. PWAs require HTTPS, which encrypts all data in transit. The security model of a well-built PWA is comparable to a native app for standard business use cases. The main area where native apps have a broader capability is in requesting hardware-level permissions for biometric authentication or low-level device access. For catalogues, booking systems, client portals, and service management tools, this distinction is not material.
If your business is ready to build, improve, or grow its online presence, book your free website or app audit with CodeLab One today and find out exactly where you stand.
