PWA vs. native app vs. Flutter: what to choose and what it costs

"We need an app." The first question we ask is not how to build it, but which kind you actually need. The same functionality can be a web app users "install" from the browser, a Flutter app in the App Store and Google Play, or two native projects. The price difference is a multiple — and a wrong choice at the start is expensive to redo later.

At Grow-App we build both natively and in Flutter (we have both in our portfolio), and on some projects we openly recommend starting with a PWA. Here is the comparison we use in initial consultations.

What is a PWA (progressive web app)

A PWA is a web app that behaves like a mobile one: it can be added to the phone's home screen, launches without an address bar, partly works offline and can send notifications. It is one codebase that runs in the browser on iPhone, Android and desktop.

What a PWA can do:

• Run anywhere there is a browser — no store installation.
• One codebase for all platforms; changes go live instantly (no store review).
• Basic offline mode and notifications (full on Android, limited on iOS).
• The fastest and cheapest way to validate an idea with real users.

What a PWA cannot do (or only partially):

• It is not in the App Store or Google Play — users will not find you in a store and the "real app" credibility is missing.
• Notifications on iOS are limited and users must explicitly enable them after adding the app to the home screen.
• Weaker hardware access: Bluetooth, NFC, sensors, advanced camera or background work.
• No Apple/Google in-app subscriptions — monetisation goes through the web.

Native app (Swift / Kotlin)

Native development means a separate project for iOS (Swift) and a separate one for Android (Kotlin). It is the most expensive but most powerful path.

• Maximum performance and smoothness, access to everything the platform offers on release day.
• Ideal for apps with demanding graphics, deep hardware integration or platform-specific features.
• Two codebases = two teams or double the time, and every future change is made twice.

We built our own product Baby-Care natively for both platforms and it has been live in the stores since 2022. It taught us exactly what we tell clients today: native development makes sense when you will actually use its advantages.

Flutter (cross-platform)

Flutter is a framework from Google in which one codebase runs as a full app on both iOS and Android — including store presence, notifications, offline mode and hardware access.

• One codebase, two platforms: development and every further change are cheaper than native.
• A full app in the App Store and Google Play, in-app subscriptions, push notifications.
• Performance is more than sufficient for typical business and startup apps.
• With extreme performance demands or the very latest platform features, a native add-on may be needed.

This is exactly how we are building the platform for local businesses — one codebase, both platforms, test builds for the client every two weeks.

Comparison at a glance

App Store / Google Play presence

• PWA: no
• Flutter: yes
• Native: yes

Notifications

• PWA: Android yes, iOS limited
• Flutter: full
• Native: full

Offline mode and hardware

• PWA: basic offline, limited hardware
• Flutter: full offline mode, hardware access via plugins
• Native: no limits

Number of codebases to maintain

• PWA: 1
• Flutter: 1
• Native: 2

Speed of shipping changes

• PWA: instant
• Flutter: through store review (days)
• Native: through store review (days), twice

Indicative price

• PWA: lowest — one web codebase, no stores
• Flutter: medium — one app for both platforms
• Native: highest — two separate projects

What does it cost?

We leave exact numbers to the pricing page and the budget planner — that is where the from–to ranges we actually work with live. For the decision, the ratio is enough:

• A PWA is usually the cheapest entry point. One web codebase, no store publishing, no Apple and Google fees. If you need to validate an idea, it is often the right first step.
• Flutter costs more than a PWA but far less than two native projects. For that price you get a full app in both stores.
• A native app is the most expensive — you pay for two codebases and make every change twice. Worth it when you will really use its advantages.

Watch out for the hidden line item: maintenance. PWA and Flutter have one codebase, native has two. The difference in monthly update and fix costs adds up over years of operation.

What we recommend when

Start with a PWA if:

• you are validating an idea and want first users in weeks, not months,
• users reach you through the web (link, QR code, campaign), not store search,
• you do not need reliable iOS notifications or hardware access.

Go with Flutter if:

• you need to be in the App Store and Google Play,
• the app has notifications, offline mode, subscriptions or works with the camera/maps,
• you want one codebase and reasonable maintenance costs — which is most business and startup apps.

Choose native development if:

• performance or graphics are critical (games, AR, video processing),
• you need deep hardware integration or the latest platform features on release day,
• you have the budget for two projects and their long-term maintenance.

The most common mistake

Choosing the technology before the goal. We have seen native apps that could have been a PWA for a fraction of the price, and PWAs rebuilt in Flutter after a year because the client needed stores and notifications from day one. That is why in the free consultation we first work out who will use the app and how it makes money — and only then what to build it in.

Summary: PWA for fast validation and simple tools, Flutter for most apps in the stores, native where performance or hardware genuinely require it. Read more about how mobile app development works with us.