What’s so great about Progressive Web Apps?

A Progressive Web App (PWA) is a website built to behave like a native app. It installs to a device’s home screen, runs offline, loads on a slow connection, and updates the moment you open it — but it ships from a single codebase that works across iOS, Android, desktop and tablet.

By 2026, PWAs have moved from “the future of mobile” to a settled architecture choice. Starbucks, Spotify, Uber, Pinterest and Twitter all run major PWAs. The question now isn’t whether PWAs work — it’s when they’re the right call versus a native build.

Dependable and low maintenance

The main selling point of progressive web apps is that they are…well, progressive. In essence, they allow you to store an entire website on your device. PWAs can be used without an internet connection and load fast on a slow connection. Unlike native mobile apps, a PWA doesn’t need to be “updated”. Opening the PWA automatically updates any changes instantly. Their small file size mean updates occur in the time it takes to open a browser. Progressive web applications are significantly easier to build than native apps and post-launch maintenance requires less time and less resources.

Flexible and nimble

Progressive web apps require less storage than their native app counterparts. Twitter’s iOS app for example, is currently over 110MB. The PWA, which closely mirrors the native app’s features, is just over 10MB.

Along with reduced size, another advantage PWAs have over their native counterparts is cross-platform interoperability. Because they run in a borderless version of your browser (Chrome, Firefox, Safari, etc.), they can be installed on desktops, tablets and mobile devices with a single codebase. Popular frameworks such as React and Vue can also be used, and the web currently supports device sensors like the ambient light sensor, accelerometer, microphone, magnetometer, and more.

In 2017 Forbes converted its primary mobile site into a progressive web app with a view to deliver users an enriched experience. A responsive PWA was the perfect solution; readers could access content for offline reading and according to Forbes, the new site’s more than 38 million monthly mobile readers are saving anywhere from 2 – 10 seconds with every page view.

Familiar and engaging

PWAs are installed like a regular app via the app store or from a website itself. They open in their own window, and in fullscreen on mobile just like a native app. They send notifications and mimic native app functionality like swiping. Users also seem to be more engaged.

Twitter Lite vs Twitter’s native app:

• 65% increase in pages per session
• 75% increase in Tweets sent
• 20% decrease in bounce rate

Pinterest’s PWA has also outperformed their native app in engagement since launching in 2017. Users are reportedly spending 40% more time on the platform compared to the previous mobile web experience and core user engagements have increased by 60%.

Browser support in 2026

Every major browser — Chrome, Safari, Firefox, Edge — has had full PWA support for years. iOS gained the most-requested PWA features (push notifications, badging, deeper home-screen integration) in Safari 16.4 in 2023, closing the long gap with Android.

Where PWAs still hit limits

PWAs are not a free pass. Three constraints worth knowing before you commit:

• Apple’s App Store still treats PWAs as second-class citizens. They can be wrapped and submitted (via PWABuilder, Capacitor and similar) but Apple’s review guidelines often reject thin wrappers. If App Store discoverability is part of your distribution strategy, factor that in.
• Hardware-deep features like advanced Bluetooth profiles, low-level filesystem access, and the most demanding camera or AR APIs still favour native.
• Page transitions and native-feeling animation are catching up but are not free. The View Transitions API helps; getting it polished still takes deliberate engineering.

When a PWA is the right call

For content-heavy products (publishing, e-commerce, member portals), employee tools, internal applications, and most B2B SaaS, a PWA usually beats a native build on cost, maintenance, and time-to-market. Single codebase, instant updates, no app-store gatekeepers between you and your users.

When native is still the better fit

If you’re shipping a hardware-bound product, a real-time game, an AR/VR experience, or anything where App Store ranking is the channel itself, native is usually still worth the cost.

At Conduct, we’ve built custom web and mobile applications for clients across healthcare, energy, government and member organisations — and the PWA-vs-native architecture call is almost always one of the first decisions we work through with them, because it sets the cost shape of everything that follows.

Frequently asked questions about Progressive Web Apps

What is a Progressive Web App (PWA)?

A Progressive Web App is a website built to behave like a native app. It can be installed to a device’s home screen, run offline, send push notifications, and access many of the same hardware features as a native app — but it ships from a single web codebase that works across iOS, Android, desktop and tablet.

What are the benefits of a PWA over a native app?

Single codebase across all platforms, no app-store gatekeepers, instant updates (no user-side install required for new versions), significantly smaller file size, and lower long-term maintenance cost. Pinterest, Twitter and Starbucks have all reported strong engagement lift after launching PWAs.

What are PWAs good for?

Content-heavy products (publishing, e-commerce, member portals), internal employee tools, B2B SaaS, and customer-facing experiences where SEO and direct linking matter more than App Store discoverability.

When should I choose native over a PWA?

Hardware-bound products, real-time games, AR/VR experiences, and anything where App Store presence is the primary distribution channel. Also: if your product depends on the deepest tiers of native APIs (advanced Bluetooth, system-level integration, the most demanding camera or sensor work), native is still the safer call.

Do PWAs work on iPhone?

Yes. iOS has supported PWAs since iOS 11.3 in 2018, and Safari 16.4 in 2023 added the most-requested features — push notifications, badging, and deeper home-screen integration — closing the long gap with Android.

How much does it cost to build a PWA in Australia?

PWA development typically costs 30-60% less than building separate iOS and Android native apps for the same feature set, because you build once instead of three times. For a fuller breakdown of Australian software costs across architectures, see our software development cost guide.