Guides / Concepts explained

Native Apps vs Progressive Web Apps: Which Do You Need?

Native apps vs progressive web apps (PWAs): what each can do, iPhone limits as of September 2026, costs, and how to choose for your first version.

Mythex Team · 2026-09-29 · 6 min read

A native app is built specifically for iOS or Android and installed from the App Store or Google Play. A progressive web app (PWA) is a website that can be installed to a phone's home screen and opens in its own full-screen window with its own icon, without going through a store. Native apps get the deepest access to the device; PWAs reach every platform from one codebase and one link, and update instantly.

For most first versions — tools, portals, trackers, booking and ordering apps — a PWA is enough. You need native when store discovery or deep device features are central to the product.

Why it matters when you build with AI

Most AI app builders produce web apps. That is not a shortcut; it is what the tools are good at, because a web app can be written, previewed and published in one place. But it means the question "will this be an app on my phone?" has a specific answer: it will be a website that behaves like an app, and can be installed as a PWA if you ask for it.

Knowing what a PWA can and can't do lets you decide early, before you promise a client "it'll be in the App Store", and before you design a feature (say, background location tracking) that the web can't deliver reliably.

An everyday analogy: a food truck vs a shop in the mall

A native app is a shop in a shopping mall. The mall (the app store) brings foot traffic and trust, but you pay rent, follow the mall's rules and wait for approval before you change your shopfront.

A PWA is a food truck with a loyal following. There is no landlord, you can change the menu tonight, and people who know you can find you anywhere. But nobody wanders past you in the mall corridor, and you can't install a walk-in freezer.

What each can do

A few terms from that table:

• Service worker: a small script the browser runs in the background for your site. It lets the app open offline, cache data and receive push messages.
• Web app manifest: a small file that tells the browser the app's name, icons, colours and that it should open full-screen ("standalone") rather than in a browser tab.

iPhone and iPad: the details that trip people up

Apple's platforms are where PWAs differ most from native, so it's worth being precise. As of September 2026, according to Apple's WebKit team and Google's web.dev:

• Installing is manual. Android browsers such as Chrome can show an install prompt. On iPhone and iPad there is no automatic prompt; users tap Share, then Add to Home Screen. Since iOS 16.4, other browsers on iOS can offer Add to Home Screen from their Share menu too.
• Every site added to the Home Screen opens as a web app by default in iOS 26. WebKit announced that from iOS and iPadOS 26, anything added to the Home Screen opens in its own window unless the user turns off "Open as Web App". A proper manifest still matters for your name, icon and behaviour.
• Push notifications need installation. Web push arrived in iOS and iPadOS 16.4 for Home Screen web apps. A PWA open in a Safari tab can't receive push; the user must install it first, then allow notifications, and the permission request has to follow a tap such as a "Turn on notifications" button. Badge counts on the icon arrived at the same time.
• Deep hardware access is thin. Features like Bluetooth accessories and NFC, which some browsers on Android expose, aren't offered in Safari.

The practical upshot: if your whole product depends on reminding people through notifications, many iPhone users who never install the app will never see them. Plan an email or SMS fallback.

Getting into the app stores

If you do need a store listing, know the costs and rules up front. As of September 2026, Apple's developer program costs US$99 a year and a Google Play developer account a one-time US$25, according to their own sites. Every iOS release goes through App Review. Apple's guidelines say an app should offer features and interface that go beyond a repackaged website, so wrapping a PWA in a thin native shell risks rejection.

A worked example: a gym's member app

A small gym wants members to book classes, see their membership, and get a reminder an hour before class.

The PWA route. Build a responsive web app with login, a class timetable and booking. Add a manifest and icons so members can install it; add a service worker so the timetable opens even on poor signal. Send reminders by push to installed users, and by email to everyone else. It ships once, works on every phone and laptop, and the gym can change the timetable layout the same day.

When native would win. If the gym later wants a check-in feature using Bluetooth beacons at the door, Apple Health integration for workouts, or a lock-screen widget with today's class, those are native territory. So is the case where members expect to find "the gym app" by searching the store.

Many teams do exactly this: PWA first to prove members use it, native later if a specific feature or store presence justifies the cost.

Common mistakes and misconceptions

• "A PWA is a lesser app." For forms, lists, bookings, dashboards and content, users often can't tell the difference once it's installed.
• "PWAs don't work on iPhone." They do. The limits are installation friction and notifications requiring installation, not basic functionality.
• Assuming push reaches everyone. On iPhone it only reaches people who installed the app and said yes.
• Promising an App Store app you can't ship. Check what your builder produces before you promise a store listing.
• Building offline editing you don't need. Caching pages to open offline is simple; editing data offline and syncing later is real work.

What to ask your AI builder for

For a PWA, be explicit:

• "Make it an installable PWA: a web app manifest with name, short name, icons (including an Apple touch icon) and standalone display."
• "Add a service worker that caches the app shell so it opens without a connection, and show a clear offline message."
• "Add an 'Install this app' help page with steps for Android and for iPhone (Share, then Add to Home Screen)."
• "If we add notifications, ask permission only after the user taps a button, and fall back to email."

The guide to building a mobile-friendly web app has a full prompt and a phone-first design checklist. If you're still deciding what the first version should include, read what an MVP is, and for budget comparisons see how much it costs to build an app.

PWAs and Mythex

Mythex builds web apps, and you can check every screen in a phone-size preview before publishing. A PWA manifest, icons and a service worker are features you ask for in chat like any other, and the published app works on any phone from a single link. Native App Store and Google Play apps are coming soon on Mythex and not available today. To start, browse app templates or the AI web app builder.