In 2015, Google Chrome engineer Alex Russell and designer Frances Berriman gave a name to a new kind of website. Progressive web apps would install from the browser, work offline and bring people back with notifications, all without being “packaged and deployed through stores.”
It sounded like the beginning of the end for app stores.
A decade later, most of that promise has come true. A PWA can be installed on Android, iPhone and desktop, work without a connection and send push notifications.
The app stores never went away, though. Until 2025, Google’s own NotebookLM was a web app people could install as a PWA, and a mobile app was one of its users’ most frequent requests.
Google built that app with Flutter and shipped it in seven months.
That’s the real decision behind Flutter vs PWA: a native app in the App Store and Google Play, or a web app people open from a link. This guide explains how each one works, compares them on reach, installation, push notifications, performance and cost, and ends with a clear way to choose.
Flutter vs PWA at a Glance
A Flutter app and a PWA can both put your product on someone’s home screen, but they get there in opposite ways. A Flutter app is downloaded from an app store and runs directly on the device, while a PWA lives at a URL and runs in the browser.
| Flutter app | Progressive web app | |
|---|---|---|
| What it is | A native iOS and Android app, written once in Dart | A website that can be installed and used like an app |
| How people get it | Download from the App Store or Google Play | Open a link, with an optional install from the browser |
| Found through | App store search, your website and ads | Search engines, links, ads and social media |
| Push notifications | For everyone who installs it and allows them | In most browsers, but on iPhone only after it's added to the Home Screen |
| Device features | Anything iOS and Android offer | What the browser supports, so no Bluetooth or NFC on iPhone |
| Offline use | Always opens; data needs local storage | Only what its service worker has cached |
| Updates | Through App Store and Google Play review | Live as soon as you deploy |
| Best suited to | People who use your app again and again | New and occasional visitors |
What Is a PWA?
A progressive web app (PWA) is a website that people can install and use like an app. It still lives at a URL and opens in any browser, but where the browser allows it, it can sit on the home screen, open without the address bar, work offline and send push notifications.
Two files turn a website into a PWA:
- A web app manifest gives the site a name, an icon and a full-screen look once it’s installed.
- A service worker runs in the background to cache pages for offline use and to receive push notifications.
Everything else is the website itself, built with HTML, CSS and JavaScript or any web framework. A PWA isn’t a separate product, just your site with app features switched on where the browser supports them.
Excalidraw, the open-source whiteboard, shows how far that goes. People open it from a shared link, can install it from the browser and keep drawing offline, because its site is a PWA with a manifest and a service worker.
What Is Flutter?
Flutter is Google’s open-source framework for building apps for iOS, Android, the web, Windows, macOS and Linux from one codebase. Its first stable version came out in December 2018, and its apps are written in Dart, a language Google also makes.
Flutter doesn’t use the buttons and lists iOS and Android provide. It draws every pixel of the interface itself with its own rendering engine, Impeller, so an app looks the same on every device.
For release, Dart is compiled ahead of time into native machine code for each platform. While you build, hot reload shows code changes in the running app without losing its state.
A Flutter app for iOS and Android is a native app. You publish it in the App Store and Google Play like any other, and it can use everything the device offers.
Can Flutter Build a PWA?
Flutter can build a PWA, because it builds for the web as well as for mobile. Its web support compiles your Dart code to JavaScript or WebAssembly and draws the interface with the browser’s graphics APIs.
Flutter’s web FAQ lists progressive web apps first among the experiences it suits best. It also explains why its web output isn’t built for search engines to index.

That leaves two catches. Flutter no longer generates a caching service worker for you, so offline support is yours to set up.
And for landing pages, marketing and help content, Flutter recommends plain HTML or Jaspr, a Dart package for traditional websites.
Flutter follows its own advice. The Flutter documentation and marketing sites run on Jaspr, not on Flutter’s web support.
So the framework isn’t the real choice. A Flutter app in the App Store and Google Play is a native app, and a PWA is a web app, whether you build it with Flutter, React or plain HTML.
The rest of this guide compares those two, and the same trade-offs apply to any native app against a PWA.
Reach and Discovery: App Stores vs the Web
A PWA reaches more new people, because it keeps everything the web does well. Every page has its own URL, so it can rank in search, open from an ad and be shared in a message, and nobody has to install anything before their first visit.
That only holds for a PWA built with regular web pages. A Flutter web app, by Flutter’s own account, isn’t indexed the way a normal site is.
A Flutter app is found in the App Store and Google Play, where people are already looking for something to install. Apple says the App Store welcomes over 850 million visitors a week across 175 storefronts.
Your listing works like a landing page. Google’s Gemini Notebook app, which launched as NotebookLM, shows what that gives a Flutter app: ratings, screenshots and a place in the charts, in front of people browsing for apps.

Some stores accept PWAs too. Google Play lists a PWA packaged as a Trusted Web Activity, and the Microsoft Store takes packaged PWAs with no code changes.
Apple’s App Store doesn’t accept PWAs as they are. Its review guidelines expect every app to include features, content and UI that “elevate it beyond a repackaged website.”
Installing a PWA vs a Flutter App
Installing a Flutter app works the way everyone expects. People find it in the App Store or Google Play, check the ratings and tap to download.
Installing a PWA depends on the device. On Android and desktop, Chrome offers to install a site once it meets Chrome’s criteria, such as a manifest with a name, icons and a display mode.
In Chrome, your site can also add its own Install button.
On iPhone, nothing prompts people to install a PWA. They have to open Safari’s Share menu, tap Add to Home Screen and turn on Open as Web App themselves.
Any website can be added this way, whether or not it’s built as a PWA.

Apple’s own guide takes six steps to get there, and few people follow them. When Apple planned to remove Home Screen web apps in the EU in 2024, it pointed to “the very low user adoption of Home Screen web apps.”
Apple dropped that plan soon after, and Home Screen web apps still work across the EU. The low take-up is what matters if you’re counting on iPhone installs.
Can a PWA Send Push Notifications Like a Flutter App?
A Flutter app can send push notifications to everyone who installs it and allows them, on iOS and Android alike. They’re delivered through Apple’s and Google’s own push services, usually with Firebase Cloud Messaging, which supports Flutter apps.
A PWA can send push notifications too, through the web push standard. On Android and desktop, Chrome, Edge and Firefox can ask for permission right on your site, with no install needed.
iPhone is the exception. Apple supports web push only for Home Screen web apps, and the permission request has to follow a tap, such as on a button to turn on alerts.
That limits your iPhone push audience to people who found Add to Home Screen and then said yes. A Flutter app can ask everyone who downloads it.
Web notifications in Safari can also do less. They can’t show images or action buttons, according to MDN, while native notifications on iOS and Android can show both.
Device Features and Hardware Access
A Flutter app can use anything iOS and Android offer. Plugins on pub.dev cover common device features, and platform channels let your Dart code call your own Swift or Kotlin code for everything else.
A PWA can only use what its browser supports. On iPhone, Apple’s App Store rules make every browser run on its own WebKit engine, outside of exceptions in the EU and Japan, so Chrome on an iPhone has the same limits as Safari.
Those limits are real. Safari doesn’t support Web Bluetooth, Web NFC or Background Sync, according to MDN, while Chrome on Android supports all three.
If your app has to talk to hardware, such as a wearable, a smart lock or a card reader, a native app is the only way to reach every user.
Is Flutter Faster Than a PWA?
Flutter is faster on demanding screens, because a Flutter app is compiled to machine code and draws every frame with its own engine. Impeller also prepares its shaders when the engine is built rather than while your app runs, so animations don’t stutter the first time they play.
A PWA runs inside the browser’s engine, which on iPhone is always WebKit. A well-built PWA is fast enough for reading, browsing, booking and shopping, and for apps like those, the quality of the build matters more than the technology.
Native pulls ahead on heavy animation, graphics and camera work, and on the feel of an app people open every day.
BMW’s team weighed exactly that for the My BMW app. It tested several cross-platform frameworks, and Flutter was the one left standing once the team “decided against web-based content for a better user experience,” according to Flutter’s showcase.
Working Offline
A Flutter app has a head start offline: its code is installed on the device, so it always opens. Data is another matter, and Flutter’s docs describe offline-first apps that keep data in local storage and sync when the connection returns.
Gemini Notebook’s mobile app shows the difference. People can download its Audio Overviews, podcast-style summaries of their sources, to play offline and keep listening in the background, two features Google highlighted when the app launched.
A PWA works offline only if its service worker has cached what people need, such as pages, images and data. On iPhone, Safari deletes that cache after seven days of Safari use in which the person hasn’t interacted with your site, although Home Screen web apps keep their own count.
Anything live needs a connection either way. Payments, bookings and messages all depend on your servers, whichever you build.
Cost, Updates and Maintenance
A PWA almost always costs less. It’s built with the web skills most teams already have, and if you run a fast, responsive website, adding a manifest and a service worker is a small project.
There are no store accounts to manage either. Apple doesn’t even require its developer program to send web push.
A Flutter app is a separate product. Flutter is free and open source, and one codebase covers iOS and Android, but you need Dart developers, two store listings and upkeep for each new version of iOS and Android.
Updates follow the same split. A PWA changes as soon as you deploy, and people get the new version the next time they open it.
A Flutter app update goes through store review first. Apple reviews 90% of submissions in under 48 hours, and devices with automatic updates turned on install the new version in the background.
Content your app loads from your servers, like products or articles, can change without a release. Flutter has no built-in way to ship code over the air, but third-party services such as Shorebird add one, within Apple’s rules on downloaded code.
Engagement and Repeat Use
A native app is better at bringing people back. It sits on the home screen, opens in a tap and can reach everyone who allows push notifications, while a PWA only gets that place with the people who install it.
In our research, app users at three ecommerce brands had 1.75 to 4.3 times as many engaged sessions as mobile web visitors, and apps delivered 1.7 to 3 times higher conversion rates than mobile web.
App users chose to install the app, so they were keen to begin with. An app’s job is to give those loyal users a faster way back, while the web keeps bringing in new ones.
Flutter or PWA: Which Should You Choose?
The right choice depends on who you’re building for. A PWA serves people who find you on the web and visit now and then, and a Flutter app serves the ones who use your product every week.
Many products run both. Gemini Notebook pairs its web app with apps built in Flutter, and X runs a PWA at x.com alongside its native apps.
Choose a PWA If
- Most of your users arrive from search, ads or shared links.
- People use your product occasionally rather than every day.
- Most of your audience is on Android or desktop, where PWAs get the most support.
- You want to launch quickly with the web skills your team already has.
- Your app needs nothing beyond what browsers offer.
Choose a Flutter App If
- People will use your app again and again, and you want it on their home screen.
- You need push notifications that reach iPhone users without an extra install step.
- Your users expect to find you in the App Store and Google Play.
- Your app needs Bluetooth, NFC, background work or other device features.
- Smooth animation and graphics are central to the experience.
Do You Need a Flutter App If You Already Have a Website?
If customers already use your website or online store, a Flutter app means rebuilding your catalog, checkout, accounts and integrations in Dart, then keeping two codebases in step. A PWA avoids the rebuild, but keeps you out of Apple’s App Store and limits push notifications on iPhone.
MobiLoud transforms the website you already run into a custom native app for iOS and Android, powered by the same underlying code, with an interface designed for your brand and push notifications built in. Our team builds, publishes and maintains the app, and you can go live in a few weeks.
Your customers get a native app they can’t tell apart from a custom build. When Vero Moda, Bestseller’s women’s fashion brand, swapped its custom-coded iOS and Android apps for apps built by MobiLoud, its shoppers kept buying as normal, and app users still spent more and came back more often than shoppers on the website.
If your app is a new product with no website behind it, Flutter is the right tool.
Final Thoughts
Flutter vs PWA matters because it decides where people find you and how easily you can bring them back. A PWA makes your website installable for everyone who finds it, and a Flutter app gives you a native app in the App Store and Google Play.
Choose a PWA if most of your users arrive from the web, visit occasionally or use Android and desktop. Choose Flutter if you’re building a new app for people who’ll open it every week, need push notifications on iPhone or depend on device features.