The PWA Landscape Has Changed Dramatically
When Google first championed Progressive Web Apps back in 2015, the concept felt aspirational. Service workers were new, browser support was inconsistent, and iOS treated web apps as second-class citizens. Fast forward to 2021, and the picture looks remarkably different. Service workers enjoy near-universal browser support, the Web App Manifest specification has stabilized, and even Apple has grudgingly improved PWA capabilities on Safari and iOS.
At StrikingWeb, we have been building PWAs for clients since 2019, and the technology has evolved from experimental to production-ready. But the question enterprises keep asking us is not whether PWAs work. They want to know whether PWAs can replace their native mobile apps, whether the investment makes business sense, and whether their specific use case fits the PWA model.
The honest answer is nuanced. PWAs are not a universal replacement for native apps, but for a significant number of enterprise use cases, they are not just ready but superior to the alternatives.
Understanding the Core PWA Technologies
Before evaluating enterprise readiness, it helps to understand what makes a Progressive Web App progressive. At its foundation, a PWA is a web application that uses three key technologies to deliver an app-like experience.
Service Workers
Service workers are JavaScript files that run in the background, separate from your web page. They act as a programmable proxy between your application and the network, enabling features that were previously exclusive to native apps.
The most important capability service workers provide is offline functionality. By intercepting network requests and serving cached responses, a service worker can keep your application functional even when the user has no internet connection. This is transformative for enterprise applications used by field workers, warehouse staff, or anyone who operates in areas with unreliable connectivity.
Service workers also enable background sync, which allows your application to queue data changes made offline and automatically sync them when connectivity returns. For enterprise use cases like inventory management, inspection reports, or sales order entry, this capability alone can justify the PWA approach.
Web App Manifest
The Web App Manifest is a JSON file that tells the browser how your application should behave when installed on the user's device. It specifies the app name, icons, theme colors, display mode, and start URL. When configured properly, a PWA installed from the browser looks and feels indistinguishable from a native application, complete with its own icon on the home screen and a splash screen on launch.
Push Notifications
The Push API, combined with the Notifications API, allows PWAs to send push notifications to users even when the browser is closed. This is a critical feature for enterprise applications that need to alert users about approvals, deadlines, system events, or incoming communications. As of 2021, push notifications work reliably on Android and desktop browsers, though iOS support remains the notable exception.
What PWAs Can Do in 2021 That They Could Not Before
The capabilities available to PWAs have expanded significantly over the past two years. Several new APIs have reached stable status or are in active development, making PWAs viable for use cases that previously required native development.
- File System Access API: PWAs can now read and write files on the user's local file system with their permission, enabling document editing workflows that were previously impossible.
- Web Share Target API: Your PWA can register as a share target, allowing users to share content from other apps directly to your application, just like a native app.
- Periodic Background Sync: Applications can periodically sync data in the background, keeping content fresh without requiring the user to open the app.
- Badging API: PWAs can display notification badges on their app icon, providing at-a-glance information about unread items or pending actions.
- Contact Picker API: Access the device's contact list with user permission, useful for communication and CRM-type applications.
- Screen Wake Lock API: Prevent the screen from dimming or locking, essential for kiosk-mode applications, presentations, and warehouse scanning tools.
The Enterprise Case for PWAs
For enterprise organizations, the decision between a PWA and a native app involves several factors beyond pure technical capability. Here is where PWAs offer compelling advantages.
Deployment and Updates
Native enterprise apps face a painful distribution challenge. Getting an app into the hands of thousands of employees through an MDM solution or enterprise app store is complex and slow. Updates require users to download new versions, and version fragmentation is a constant headache for support teams.
PWAs eliminate this entirely. Deploy to a web server, and every user gets the latest version on their next visit. Service worker update mechanisms ensure that the transition is seamless. There is no app store review process, no waiting for employees to update, and no supporting multiple versions simultaneously.
Cross-Platform with a Single Codebase
An enterprise PWA works on Windows, macOS, ChromeOS, Android, and iOS from a single codebase. For organizations that support a diverse device ecosystem, this dramatically reduces development and maintenance costs. Instead of maintaining separate iOS, Android, and desktop applications, a single team can build and maintain one PWA that reaches all platforms.
Cost Efficiency
Building and maintaining separate native apps for iOS and Android typically costs two to three times more than building a single PWA. For internal enterprise tools where the app store discovery advantage of native apps is irrelevant, this cost differential is hard to justify. Our clients who have switched internal tools from native to PWA have reported 40 to 60 percent reductions in ongoing development costs.
The Honest Limitations
We would be doing a disservice to our clients if we did not address the areas where PWAs still fall short of native apps in 2021.
iOS Restrictions
Apple's Safari continues to lag behind Chrome and Edge in PWA support. The most significant limitation is the absence of push notifications for PWAs on iOS. Service worker support exists but has quirks, including a tendency to evict cached data after a period of inactivity. If your enterprise heavily relies on iOS devices and push notifications are critical, a hybrid approach may be necessary.
Hardware Access
While web APIs have expanded dramatically, some hardware capabilities remain native-only. Bluetooth Low Energy access is still limited. NFC support is emerging but not universal. Advanced camera controls, biometric authentication beyond basic WebAuthn, and certain sensor APIs are either unavailable or unreliable in the browser context.
Performance for Intensive Applications
Applications that require intensive graphics processing, complex animations, or heavy computational workloads will still perform better as native apps. Games, video editing tools, and augmented reality applications are not ideal PWA candidates. However, for the vast majority of enterprise applications, which are primarily data-driven CRUD operations, the performance difference is negligible.
Our Recommended Approach for Enterprises
Based on our experience building PWAs for enterprise clients, we recommend the following evaluation framework.
Choose a PWA when your application is primarily data-driven, needs to work across multiple platforms, requires frequent updates, benefits from offline capability, and does not depend on iOS push notifications or advanced hardware access. Internal tools, dashboards, field service applications, inventory systems, and employee portals are excellent PWA candidates.
Choose native when your application requires deep hardware integration, depends on iOS push notifications, needs access to platform-specific APIs like HealthKit or ARKit, or demands the highest possible graphics performance.
Consider a hybrid approach when you need the broad reach of a PWA for most users but also require native capabilities for specific platforms or features. Tools like Capacitor can wrap a PWA in a native shell, giving you app store distribution and access to native plugins while maintaining a shared web codebase.
The best technology choice is the one that serves your users and your business goals, not the one that sounds most impressive in a meeting.
Getting Started with Your Enterprise PWA
If you are considering a PWA for your enterprise, start with a pilot project. Choose an internal tool that would benefit from offline capability and cross-platform access. Build it as a PWA, deploy it to a subset of users, and measure the results against your existing solution. The data will speak for itself.
At StrikingWeb, we have helped organizations across healthcare, logistics, and education deploy enterprise PWAs that reduced development costs while improving user adoption. If you are evaluating whether a PWA is right for your organization, we are happy to share our experience and help you make an informed decision.