Apple's decade-long resistance to Progressive Web Apps has cracked. EU Digital Markets Act compliance forced Apple to support PWA installation in the EU, web push notifications arrived on iOS 16.4, and the growing capability of the web platform has made the argument for mandatory native app distribution increasingly difficult to sustain. Enterprises that previously had no choice but to maintain separate iOS and Android applications are now evaluating whether PWAs can meet their requirements.
What PWAs Can Do in 2024
The web platform capability surface has expanded dramatically. Service Workers enable offline functionality and background sync. Web Push enables notifications on desktop and (now) mobile. WebAssembly enables near-native computational performance for CPU-intensive workloads. Web Bluetooth, WebUSB, Web NFC, Web Serial, and the File System Access API enable hardware integration that was previously exclusive to native apps.
For enterprise use cases — internal tools, field service applications, knowledge bases, communication tools — PWAs can now deliver 90%+ of the functionality that previously required native development. The 10% gap is narrowing with each browser release cycle.
The Total Cost of Ownership Argument
The TCO argument for PWAs is compelling. A single codebase maintained by a web team versus separate iOS (Swift/SwiftUI) and Android (Kotlin/Jetpack Compose) codebases requires substantially different team structures. Native app development requires platform-specific expertise, app store submission processes (2-7 day review cycles for updates), and platform SDK upgrade work with each major OS release.
For enterprises deploying 50+ internal applications, the maintenance burden of native apps is significant. A PWA-first strategy with progressive enhancement for native capabilities reduces this substantially. The applications that genuinely require native — camera-intensive workflows, AR/VR, intensive sensor access — can remain native while the majority of the portfolio migrates to the web.
Implementation Patterns for Enterprise PWAs
Enterprise PWA architecture typically uses a Next.js or Remix app shell with a service worker managed by Workbox. The service worker strategy — cache-first for static assets, network-first with cache fallback for API responses, background sync for offline mutations — defines the offline experience.
Authentication is the most complex area for enterprise PWAs. MSAL.js (Microsoft Authentication Library) and Auth.js provide SSO integration with Azure AD and enterprise identity providers. Secure token storage in service workers and PKCE flow support are required for mobile PWA scenarios where redirect-based authentication is the default browser behavior.
Key Takeaway
"The post-app store era is arriving gradually, then suddenly. Enterprises that proactively build PWA capabilities into their web applications will be positioned to reduce platform dependency, accelerate update delivery, and simplify their application portfolio — without sacrificing the user experience that end users expect from modern business applications."
Topics
