I have spent most of this series making the case for Progressive Web Apps, so it feels only fair to be equally honest about where they fall short. PWAs are a genuinely excellent choice for many applications, but they are not the right choice for all applications, and making an informed decision requires understanding the real limitations rather than the marketing-glossed version.
The PWA community has a tendency to downplay limitations and overpromise capabilities, which does a disservice to businesses that make technology decisions based on incomplete information. So here is the honest assessment of where PWAs struggle in 2026.
iOS Remains a Problem
Apple has been a reluctant participant in the PWA ecosystem from the beginning, and while support has improved, iOS still lags significantly behind Android in PWA capabilities. Push notifications now work on iOS, which was a long-standing gap, but other limitations persist.
Storage quotas are more restrictive. Background sync is less reliable. And Apple’s tendency to make periodic changes that affect PWA behavior without warning creates uncertainty for businesses that depend on these features.
If a significant portion of your user base is on iOS, test extensively on actual iOS devices throughout development. Do not assume that because something works on Android it will work identically on iOS. The differences can be subtle but impactful, like cache behavior that works perfectly on Chrome but causes stale content issues on Safari.
Hardware and Platform Integration Limits
PWAs cannot access Bluetooth, NFC, or USB devices reliably across all browsers and platforms. If your application needs to communicate with physical hardware, native development is still the more reliable path. Advanced audio processing, augmented reality with sophisticated camera control, and background location tracking are also areas where native capabilities significantly exceed what browsers expose through web APIs.
The gap is narrowing year over year, and the Web Bluetooth and Web NFC APIs are making progress, but if you need these capabilities today for your core functionality, building on emerging and partially supported APIs is risky. You could end up with an application that works on some devices and fails on others in ways that are confusing and frustrating for users.
App Store Presence and Distribution
PWAs live outside the app store ecosystem, which is both a strength and a limitation. You avoid the thirty percent revenue cut that Apple and Google take on app store transactions. You avoid the review process that can delay releases. But you also lose the discovery mechanism that app stores provide. If potential users search for solutions in the app store, your PWA will not appear.
For businesses where organic app store discovery is a meaningful customer acquisition channel, the absence of an app store listing is a real business limitation, not just a technical one. Some businesses address this by creating thin native wrappers around their PWA for app store presence, but this adds complexity and maintenance burden.
Making an Informed Decision
A good development partner will be honest about whether a PWA meets your specific requirements rather than advocating for whatever technology they prefer. List your must-have features, identify which platforms your users are on, and evaluate honestly whether PWA capabilities cover your needs. For many businesses, they absolutely do, and the cost savings are substantial. For some, native development remains the better investment despite the higher price. That honesty upfront saves you from expensive pivots later. For more technology decision guidance, visit our blog.
