Key Takeaways
- PWAs use Service Workers, Web App Manifests, and HTTPS to deliver app-like experiences — instant loading, offline functionality, and home screen installation — from a standard website.
- Development cost is significantly lower than building separate native iOS and Android apps — one web codebase serves all platforms.
- Android Chrome support for PWAs is mature; iOS Safari support (added in iOS 11.3) is improving but still lacks push notifications.
- PWAs are indexed by search engines — unlike native apps, they benefit from SEO and are discoverable through organic search.
- The best use cases are content-heavy applications, task-based internal tools, and e-commerce stores where fast load times and offline reliability directly affect outcomes.
The mobile experience of most business websites in 2017 follows a familiar pattern: the page loads slowly on a mobile connection, the user waits, some give up, the ones who stay encounter a responsive layout that works but doesn't feel native, and when they leave and come back they wait again because nothing was cached. Progressive Web Apps are a response to this pattern. Coined by Google engineers Alex Russell and Frances Berriman in 2015, the term describes a set of web technologies — primarily Service Workers, Web App Manifests, and HTTPS — that enable websites to behave like native mobile applications: loading instantly on repeat visits, functioning offline or on unreliable connections, living on the device home screen, and sending push notifications. The promise is compelling: the distribution reach of the web (no app store, no install friction, indexed by search engines) combined with the user experience quality of a native app. The reality, as of late 2017, is that PWAs deliver most of this promise on Android and an increasing (but still limited) portion of it on iOS. For the right use case, they represent a genuine step forward in mobile web experience.
Definition: Service Worker
A Service Worker is a JavaScript file that runs in the background of a browser, separate from the web page, and acts as a proxy between the web application and the network. Service Workers are the core technology enabling PWA capabilities: they intercept network requests and serve cached responses when the network is unavailable (offline support), enable push notifications by listening for push events even when the browser isn't open, and manage background sync to defer actions until connectivity is restored. Service Workers run only on HTTPS connections and are supported in Chrome, Firefox, Edge, and Safari (from iOS 11.3). They do not have access to the DOM — they communicate with the page through the postMessage API.
What a PWA Can Do That a Responsive Website Cannot
PWAs add four capabilities to standard responsive websites: instant loading on repeat visits, offline functionality, home screen installation, and push notifications — each with meaningful implications for user experience and engagement.
Instant loading on repeat visits is the most universally impactful PWA capability. A Service Worker caches the application shell — the HTML, CSS, and JavaScript that forms the structural skeleton of the app — on first visit. On subsequent visits, the shell loads from cache immediately (often in under 100ms), then fetches fresh content from the network in the background. The result is an experience that feels instant, even on slow connections. Google's Lighthouse tool measures this as Time to Interactive — the interval from page load to a fully usable interface — and well-implemented PWAs score dramatically better than standard websites on mobile networks.
Offline functionality means the app works — at least partially — when the user has no network connection. For a news app, this means previously loaded articles remain readable on the tube. For a field inspection tool, it means inspectors can continue working in locations with no signal, with data syncing when connectivity returns. For an e-commerce catalogue, it means product browsing remains available even when the network drops. The offline experience is limited to content the Service Worker has pre-cached or content the user has previously loaded — a PWA cannot load new server data without a network connection. But for many applications, a graceful offline experience is dramatically better than a blank 'No connection' screen.
Home screen installation ('Add to Home Screen') allows users to install the PWA to their device's home screen, creating an icon that launches the app in a standalone window without browser chrome. The experience on Android Chrome is native-feeling: the browser prompts eligible PWAs with an install banner, and installed PWAs launch in their own window with custom splash screens and app icons. On iOS, the user must manually trigger 'Add to Home Screen' from Safari's share menu — automatic install prompts are not supported on iOS as of 2017. Push notifications (not yet available on iOS Safari) allow the app to send messages to a user's device even when the browser is closed — enabling re-engagement campaigns, delivery updates, and real-time alerts.
- Instant loading — Service Worker caches app shell, enabling sub-100ms repeat loads
- Offline support — users access cached content when network is unavailable
- Home screen installation — no app store friction, installs from browser on Android
- Push notifications — re-engagement without native app (Android only as of 2017)
- Search engine indexable — unlike native apps, PWA content is crawlable and rankable
When to Build a PWA vs a Native App vs a Responsive Website
Choose a PWA when fast mobile experience, offline support, and broad reach matter more than deep device hardware access or iOS push notifications.
A responsive website remains appropriate for content-focused businesses where the primary need is accessibility across devices: blogs, service business sites, portfolio websites, marketing pages. A responsive website built with good performance practices (fast hosting, image optimisation, minimal JavaScript) delivers an adequate mobile experience without the additional development complexity of Service Workers and PWA infrastructure. Upgrading a well-performing responsive site to PWA capabilities is incremental — add a Service Worker and a manifest — rather than a rebuild.
A PWA is the right choice when: your business relies on repeat mobile visits and fast loading directly affects engagement or conversion (news, e-commerce, task-based apps); your users operate in environments with poor or intermittent connectivity (field workers, travellers, commuters); you need a home-screen-installed experience without the cost and friction of app store distribution; and push notifications on iOS are not a core requirement. Several major brands have published compelling PWA case studies: Twitter Lite saw 65% increase in pages per session, Flipkart saw 70% conversion rate increase after replacing their native app with a PWA, and AliExpress saw 104% conversion rate increase for new users.
A native app remains necessary when: you need push notifications on iOS as a core feature; your app requires access to device hardware not yet available to web APIs (AR, NFC in some contexts, Bluetooth, advanced camera controls); your target platform is iOS and you need the full range of PWA features that Safari doesn't yet support; or your user experience requires performance characteristics that even the best web application can't match (complex 3D graphics, intensive computation). The native vs PWA decision is increasingly case-by-case as browser capabilities expand — features that required native apps in 2015 are available to PWAs in 2017.
What Does Building a Progressive Web App Cost?
Adding PWA capabilities to an existing modern web application is incremental; building a PWA from scratch costs significantly less than equivalent native iOS and Android apps.
If you have a modern responsive website built on a JavaScript framework (React, Vue, Angular), adding Service Worker support and a Web App Manifest is a 2–5 day development task that delivers the core PWA capabilities — offline support, home screen installation, and caching strategy. Tools like Google's Workbox library handle the boilerplate Service Worker logic and reduce implementation time. The incremental cost of making a well-architected existing site into a PWA is low relative to the user experience improvement.
Building a PWA from scratch — a full application with complex functionality, real-time data, and sophisticated offline behaviour — is more comparable in cost to a complex web application than to a native app. A PWA that replaces a native app might cost $25,000–$100,000 to build, compared to $40,000–$200,000 for equivalent native iOS and Android apps (built and maintained separately). The single codebase advantage compounds over time: updates are deployed once to the web and immediately available to all users, rather than requiring separate iOS and Android releases submitted to app store review.
PWA development cost savings are most significant for businesses that would otherwise need to maintain separate iOS and Android codebases. A B2B field service app that previously required separate iOS and Android native apps — each requiring their own development team and release cycle — can potentially be replaced by a single PWA that serves both platforms, with dramatic ongoing maintenance cost savings.
Experience Signal
The projects where we've seen the clearest case for a PWA are businesses with significant mobile traffic and measurable drop-off at page load — where a 3-second load time on 3G is directly costing conversions. After adding Service Worker caching and an app shell architecture, repeat visits become near-instant and the conversion rate improvement is often visible in the first month of data. The projects where PWA is harder to justify are those where the primary value proposition is push notifications on iOS — which still aren't supported — or where the existing website's performance is already strong and the incremental PWA features (home screen install, offline) don't address a real user need.
Frequently Asked Questions
A Progressive Web App (PWA) is a website built using modern web technologies that delivers an app-like experience in a mobile browser. Key characteristics include: loading instantly on repeat visits (via service worker caching), working offline or on poor connections, being installable on a device's home screen without going through an app store, and — on supported platforms — sending push notifications. PWAs are built with standard web technologies (HTML, CSS, JavaScript) and served over HTTPS, but they use the Service Worker API, Web App Manifest, and other modern browser APIs to provide capabilities previously only available to native apps.
A native app is built specifically for a platform (iOS using Swift/Objective-C, Android using Kotlin/Java) and distributed through the App Store or Google Play. It has full access to device hardware and OS APIs. A PWA is built with web technologies and runs in the browser — but on supported platforms (Android with Chrome, increasingly iOS with Safari) it can be installed on the home screen and access a growing set of device capabilities. Native apps still have advantages in performance, device API access, and iOS support; PWAs have advantages in development cost (one codebase for all platforms), distribution (no app store friction), and discoverability (indexed by search engines). The gap is narrowing as browser capabilities expand.
Partially, and improving. Apple added basic PWA support to Safari on iOS in iOS 11.3 (March 2018), enabling home screen installation and basic offline support via service workers. However, iOS Safari still lags behind Chrome on Android in PWA capability: push notifications are not supported on iOS Safari as of 2017, background sync is limited, and the level of offline capability is less robust than on Android Chrome. For most use cases, a PWA provides a meaningfully better experience than a responsive website on both iOS and Android — but if push notifications on iOS are a core requirement, a native iOS app remains necessary.
Sources
Interested in Building a Progressive Web App?
Webnixon builds Progressive Web Apps and upgrades existing websites with PWA capabilities — improving mobile performance, enabling offline access, and reducing the cost of maintaining separate native apps.
Talk to Us About PWA DevelopmentAbout the author
Jai Paek
Creative Director
Jai leads brand identity and UX design at Webnixon, bringing 20+ years of experience building digital design systems for agencies and enterprise teams. He has shipped design systems and visual identities for over 200 brands across Canada and the US, with deep expertise in conversion-focused UI, WCAG 2.1 accessibility compliance, and responsive web design for service businesses and ecommerce brands.
Related Articles
Web Design
What Is Responsive Web Design? A Plain-English Guide for Business Owners
More Canadians are browsing the web on their phones than ever before, and that number is accelerating fast. Responsive web design is how your website automatically adapts to any screen size — and in 2012, it's becoming essential.
SEO
Google's Mobile-First Indexing: What It Means and What Your Website Needs to Do
Google has shifted to evaluating and ranking websites based primarily on their mobile version rather than their desktop version. If your mobile site has less content, slower performance, or different structured data than your desktop site, your rankings are at risk — regardless of how strong your desktop version is.
Web Design
How to Improve Website Page Speed: A Practical Guide for Ontario Businesses
Every extra second your website takes to load, you lose visitors. Studies show a one-second delay in page load time reduces conversions by 7%. This guide walks through the specific fixes that will make the biggest difference for a typical Ontario small business website.