Skip to content
PromotEdge International

Home Guides PWA vs native app

Guides · Comparison

Progressive web app vs native app: which to build

Not every app needs the App Store. A progressive web app is a website built to behave like an app: it installs to the home screen, works offline and can send notifications, from one codebase. A native app is built for each platform and installed from the stores. This guide compares the two on what they can do, how they are distributed and updated, and what they cost, from the platforms' own documentation, and says which to build when. It is part of our guide to web apps and mobile apps.

Reviewed by Benjamin SardarUpdated 12 Nov 20264 min read

The short answer

Should I build a progressive web app or a native app?

Build a progressive web app (PWA) when you want one codebase that works in any browser, installs to the home screen, works offline and updates instantly without app store review, and when users mainly view, enter and manage information. Build a native app when you need deep device features, the visibility and trust of the App Store and Google Play, or the most polished performance. Since iOS and iPadOS 16.4, home screen web apps can also receive push notifications.

Key takeaways
  • A PWA is a web app that installs, works offline through service workers, and runs from one codebase on every device.
  • Native apps are built per platform (or with a cross-platform framework) and distributed through the app stores.
  • Since iOS and iPadOS 16.4 (2023), web apps added to the Home Screen can receive push notifications.
  • PWAs skip store fees and review; native apps pay Apple $99 a year and Google Play $25 once, and pass review.
  • Choose by the device features you need, how users will find the app, and how often it changes.

Need this done for your business? A person reads every message and replies.

Ask for a call back

Progressive web app vs native app at a glance

The two compared on what decides most projects. Facts from the platforms' own pages; fit from our working practice.

Sources: MDN and web.dev on PWAs; WebKit (16 Feb 2023); Apple App Store Review Guidelines; Apple Developer Program; Google Play Console help. Fit: our own working guide.
PointProgressive web appNative app
CodebaseOne, built with web technologiesOne per platform, or one cross-platform
InstallFrom the browser to the home screenFrom the App Store or Google Play
OfflineYes, through service workersYes
Push on iPhoneYes, for Home Screen web apps since iOS 16.4Yes
UpdatesLive on deploy; no reviewThrough store review and user updates
Store feesNoneApple $99 a year; Google Play $25 once
Deep device featuresGrowing, but gaps remainFull access
Usually suitsPortals, tools, ordering, dashboardsDevice-heavy, store-led, polished apps

A PWA runs from one web codebase, installs to the home screen, works offline and updates instantly, without store fees or review; since iOS 16.4 it can also send push notifications on iPhone. A native app reaches deeper device features and the app stores. Choose by the features you need, how users will find the app and how often it changes.

What a progressive web app is

MDN's guide to progressive web apps describes a PWA as an app built with web platform technologies that gives a user experience like a platform-specific app. It runs from one codebase on many platforms, can be installed, and can work offline and in the background through service workers. web.dev's introduction adds that a PWA reaches anyone on any device from a single codebase and, once installed, opens in its own window.

What a native app is

A native app is built for iOS or Android with each platform's tools, or for both with a cross-platform framework such as Flutter or React Native, and is installed from the App Store or Google Play. It has direct access to the device's features and follows each platform's design conventions; our guide to Flutter vs React Native covers the shared-code route.

Device features and the gap

The web's capabilities have grown: Chrome's capabilities project describes an effort to close gaps in what web apps can do. Push notifications, once the biggest gap on iPhone, arrived with iOS and iPadOS 16.4: the WebKit announcement (16 February 2023) says Home Screen web apps can receive web push, with permission asked after a user action. Features that reach deep into the device, such as some background processing, advanced Bluetooth use or tight integration with platform services, still favor native apps; check each feature you need on each platform before deciding.

Distribution and updates

How users get the app, and how fast you can change it, differ sharply:

  • PWA: found on the web and through search, shared by link, installed from the browser; updates go live when you deploy, with no review.
  • Native: found in the App Store and Google Play; each release passes store review, and users update through the store.
  • Store fees: the Apple Developer Program costs $99 a year and Google Play charges a $25 one-time fee; a PWA needs neither.
  • Store rules: Apple's App Store Review Guidelines (4.2, minimum functionality) reject apps that are little more than a repackaged website, so a thin wrapper around a site is not a shortcut into the store.

Cost and maintenance

A PWA is one codebase, built and maintained by web developers, so it usually costs less to build and change than two native apps. A cross-platform native app narrows that gap. Native apps also need yearly updates to meet store requirements; our guide to app maintenance cost sets those out.

Which to build

A rule of thumb from our own working practice:

  • Build a PWA for portals, internal tools, booking and ordering, dashboards and content apps, where users mainly view, enter and manage information, change is frequent, and reach by link matters.
  • Build a native app when you need deep device features, store visibility and trust, offline-first work in the field at scale, or the most polished interaction.
  • Start with a PWA, add native later when demand is unproven: the web app's back end and APIs can serve a native app built afterwards.

Conclusion

A progressive web app installs from the browser, works offline, updates instantly and, since iOS 16.4, can send push notifications on iPhone, all from one web codebase with no store fees or review. A native app reaches deeper device features and the app stores, at the cost of separate releases, review and yearly platform updates. Choose by the features you need, how users will find the app and how often it changes.

PromotEdge International is an international strategy, technology, marketing and design company, and our delivery team is in India. Our web application team builds progressive web apps and portals, and our mobile app development team builds native and cross-platform apps, in your own accounts.

Facts we rely on: see our company facts for what we state about ourselves and where each fact comes from.

Common questions

  • A progressive web app is built with web technologies, runs from one codebase, installs from the browser, works offline through service workers and updates as soon as you deploy. A native app is built for each platform or with a cross-platform framework, installed from the app stores, and has full access to device features.

  • Yes, since iOS and iPadOS 16.4. WebKit announced in February 2023 that web apps added to the Home Screen can receive web push, with permission requested after a user action. Notifications appear on the Lock Screen and in Notification Center.

  • Usually, because one web codebase serves every device and there are no store fees or review cycles. Apple charges $99 a year for its developer program and Google Play a $25 one-time fee. A cross-platform native app narrows the gap, and native apps also need yearly platform updates.

  • Not simply by wrapping it. Apple's App Store Review Guidelines (4.2, minimum functionality) reject apps that are little more than a repackaged website. A PWA is distributed through the web instead, by link and search, and installed from the browser.

  • When the app needs deep device features, such as heavy background processing or advanced hardware access, when store visibility and trust matter to your users, or when interaction must be as polished as possible. Check each feature on each platform before deciding.

  • Yes. Our web application team builds progressive web apps, portals and internal tools, and our mobile app development team builds native and cross-platform apps, all in your own accounts. We recommend one in writing after seeing what users need, and publish no rate card.

Brands we have worked with

  • Fine Organics
  • Weichai
  • Novozymes
  • Dozco
  • SANY
  • Prezent
  • Honest AI
  • SCENNE
  • Sara International
  • Vega MPS
  • Desi Machine Pvt. Ltd.

Work delivered from India. Results are shared one to one, under NDA.

See all clients

Talk to us

Tell us what you need

We use these details only to reply to you.

Phone or WhatsApp (optional)
Who is it for? (optional)

Rather talk now?

How we work

  1. 01

    Tell us the goal

    A rough note through the form on what you sell and what needs to change.

  2. 02

    We study your market

    How people find you today, where inquiries get lost, then a call in your working day.

  3. 03

    A written plan

    The work, who does it and how it is measured. Nothing starts until you approve it.

  4. 04

    The work starts

    Our team in India does the work, with calls set in your working hours.

  5. 05

    Reports and visits

    Every number we report shows its source and date range, and we travel to our clients every 3 to 4 months.

Chat with us