What Makes a PWA Technically
Progressive Web Apps are not a standalone technology — they are a concept: a combination of existing web technologies that together deliver an app-like experience in the browser. The three foundational pillars are Service Workers, a Web App Manifest, and HTTPS. Service Workers are JavaScript files that run in the background and intercept network requests — they enable offline functionality, push notifications, and fast load times through intelligent caching. The Web App Manifest is a JSON file that tells the browser how the app should look and behave when added to the home screen — including the app name, icons, and launch behavior. HTTPS is non-negotiable: without an encrypted connection, Service Workers won't run, and browsers won't recognize the application as a PWA at all.
The "Progressive" in the name comes from the concept of Progressive Enhancement — the idea that a PWA works on basic devices and browsers, and unlocks additional capabilities on modern ones. Users on older browsers receive a standard website experience; users on modern devices get an installable, offline-capable app experience. This makes PWAs an inclusive technology: they exclude no one, but reward users whose hardware and software can support the full feature set.
What PWAs Can — and Cannot — Do
The capabilities of modern PWAs have expanded considerably in recent years. Offline mode allows users to continue using an application without an internet connection — ideal for services where connectivity cannot be guaranteed. Push notifications work on Android and desktop without a native app; iOS has supported them fully since Safari 16.4. Home screen installation — without an app store, without a review process, without a platform commission — is one of the most commercially attractive aspects for companies seeking direct user access without intermediaries.
Understanding what PWAs cannot do is equally important. Deep hardware access — Bluetooth, NFC, camera with advanced permissions, contacts, or calendar — remains restricted on iOS. Features that require native APIs cannot be fully replicated through the web. Teams building applications that interact intensively with device hardware — fitness tracking, advanced augmented reality, or complex device management — will find that native development or a hybrid approach remains necessary for those specific capabilities.
When PWA Beats Native
The traditional argument for native apps centered on performance and feature depth. Both arguments still hold — but their weight has shifted significantly. For many use cases where deep device access is unnecessary, the performance advantage of native development is modest. The disadvantage, however, is substantial: building and maintaining a separate iOS app and a separate Android app means double the development effort, double the test coverage, and double the store maintenance burden. A PWA is built once, works across all platforms, and requires no app store review process to ship updates.
The Starbucks case is frequently cited in the industry: the company built a PWA weighing 2 megabytes — compared to 148 megabytes for their iOS app. The PWA doubled the number of users placing orders via the web. Twitter Lite, Twitter's PWA, reduced average load time by 30 percent, data consumption by 70 percent, and bounce rate by 20 percent compared to the previous mobile website. These numbers make the argument plainly: PWAs are not a budget compromise — for certain use cases, they are the technically superior choice with measurable business impact.
When Native Apps Remain the Right Choice
There are scenarios where native development holds a clear advantage. Graphics-intensive games benefit from direct hardware access and platform-optimized rendering pipelines that the web cannot yet fully match. Apps relying heavily on Bluetooth or NFC — point-of-sale systems, smart home controls, or medical devices — require native APIs that remain out of reach for web applications. And apps whose monetization strategy depends on in-app purchases through the App Store or Play Store are tied to native platform presence by commercial necessity.
The honest answer to "PWA or native app?" is: it depends on the use case. Organizations seeking to reach a broad user base, optimize development costs, and operate without app store dependencies should take PWAs seriously as a primary strategy. Those who need deep device access, or want to leverage platform-specific features like Apple Watch integration or iOS widgets, cannot avoid native development. For many projects, the best answer is a hybrid model: a PWA for the core use case, supplemented by native features precisely where they create genuine value — not as a default assumption, but as a deliberate choice driven by real requirements.
Performance Advantages and Real-World Results
Beyond the install-and-discovery advantages, PWAs consistently outperform traditional mobile websites on performance metrics that directly affect user behavior. Because Service Workers cache assets aggressively, repeat visits load almost instantaneously — even on slow connections. Time to interactive drops, bounce rates fall, and engagement metrics improve without any change to content or design. These are not hypothetical benefits: the Twitter Lite and Starbucks case studies represent patterns that play out across industries wherever PWAs are deployed thoughtfully, with proper caching strategies and attention to the specific network conditions of their target users.