PWA vs native iPhone app in 2026: what iOS still holds back
PWA or native iPhone app? What a web app added to the Home Screen can do on iOS in 2026, what only a native app gets, and how to choose for your idea.
By Sigsten Gustavii· · 8 min read
A PWA is a website that behaves a little like an app once added to the Home Screen, while a native iPhone app is built with Apple's own tools for the phone; in 2026 the PWA has closed some gaps on iOS, but not the App Store, payments or deep device access.
The choice matters because it decides how people find your app, what it can do and how it feels. This guide sets out what a PWA can and cannot do on an iPhone today, from WebKit's and Apple's own pages, where native wins, and how to choose without overbuilding.
| PWA on iPhone | Native iPhone app | |
|---|---|---|
| How people get it | Open a website, then Add to Home Screen | The App Store, or installed directly for testing |
| Listed in the App Store | No | Yes |
| Notifications | Web push for Home Screen web apps, since iOS 16.4 | Local and push notifications |
| Badge on the icon | Yes, since iOS 16.4 | Yes |
| Selling digital features | Your own web checkout | Apple's in-app purchase |
| Stored data | Subject to WebKit's quotas and eviction rules | Stored by the app on the device |
| Device features | What the browser exposes | Apple's frameworks: camera, Face ID, motion, maps, contacts and more |
| Look and feel | Web components styled to look native | Apple's own interface components |
| Updates | Instant, on next load | Through App Review for App Store apps |
What a PWA is
A progressive web app is a website built so it can be installed: it has a manifest with a name and icon, works in its own window, and can keep working offline with stored data. On an iPhone, people open it in Safari and choose Add to Home Screen. From then on it opens like an app, without browser bars.
It is one codebase that runs on any device with a modern browser, which is its great strength: one deployment reaches iPhones, Android phones and desktop computers alike, and nobody needs to visit a store to get it.
What a PWA can do on iPhone in 2026
- Web push notifications. According to WebKit, since iOS and iPadOS 16.4 a web app added to the Home Screen can ask permission to send push notifications, in response to a tap.
- Badges. The same release added the Badging API for Home Screen web apps.
- Storage. WebKit's storage policy gives Home Screen web apps the same quota as a browser, and its heuristics favour them when granting persistent storage.
- Offline use, with service workers caching pages and data.
- Instant updates: change the website and everyone has the new version.
What iOS still holds back from a PWA
- No App Store listing. People have to find your website and know to add it to the Home Screen. There is no App Store search, page or ratings.
- Storage can be evicted. WebKit evicts data by least-recent use, under storage pressure, or when the user has not interacted with a site for some time. Persistence is granted by heuristics, not guaranteed.
- Fewer device features. A PWA reaches what Safari exposes to the web. Native apps use Apple's frameworks directly: Face ID through LocalAuthentication, step counts through Core Motion, Apple Maps, contacts and calendars, haptics and more.
- No Apple in-app purchase. That is fine if you take payments on the web, but it means no App Store subscriptions or Family Sharing.
- It feels like the web. Careful design gets close, but native controls, gestures and system behaviours are hard to match exactly.
What it costs to build and run each
| Cost | PWA | Native iPhone app |
|---|---|---|
| Apple's membership | None | 99 USD a year to publish |
| Store commission | None; your payment provider's fees | Apple's commission on digital sales, 15% for small developers |
| Hosting | A web host for the site | A backend only if the app needs shared data |
| Updates | Deploy the website | A new version through App Review |
| Reaching other platforms | Included | A separate app for Android |
Neither route is free of work. A PWA saves Apple's fee and review, but you still have to bring people to the website and teach them to add it to the Home Screen. A native app pays Apple, but the App Store brings search, ratings and a place people already look for apps. Our post on how much Apple takes from app sales covers the commission side.
Can you put a PWA in the App Store?
You can wrap a website in a thin native shell, but Apple is direct about it. Its App Review page says that websites served in an iOS app, web content not formatted for iOS and limited web interactions do not make a quality app, under guideline 4.2, and lists apps without enough lasting value among common issues. A wrapper that adds nothing beyond the website is a common rejection. If you want to be in the App Store, build something people cannot get from the website alone.
When a PWA is the right choice
- Your product lives on the web, and the phone is one of several places people use it.
- You update constantly and do not want each change to go through review.
- You need every platform at once, including desktop browsers and Android, from one codebase.
- The features are simple: forms, lists, content, a dashboard.
When a native iPhone app is the right choice
- You want to be found in the App Store, with a product page, ratings and search.
- You sell digital features and want Apple's in-app purchase and subscriptions.
- You need the phone itself: the camera, Face ID, motion and steps, maps, contacts, calendar, haptics.
- Data must stay put, saved by the app on the device and in your own cloud.
- It should feel at home on iOS, with Apple's own components and gestures.
| Your idea | Lean towards |
|---|---|
| A dashboard for a web service you already run | PWA |
| A content site people bookmark | PWA |
| A habit tracker or journal used daily on the phone | Native |
| An app that scans, photographs or uses Face ID | Native |
| A subscription app sold to the public | Native |
| An internal tool for a team on mixed devices | PWA, or native for the people on iPhones |
Turning a website into a native iPhone app
If you already have a website or web app and want a real iPhone app, you do not need a wrapper. Borel can read your site's public address and build a native SwiftUI app on its brand: its name, colours, logo and content, with native tabs, lists and screens. See website to iPhone app, and the glossary entries for a PWA, a web-view app and a native app.
How to make a native iPhone app with Borel, step by step
- Sign up at borel.one, free with 5 credits a day.
- Describe the app, or paste your website's address and ask for an iPhone app based on it.
- Borel writes it in Swift and SwiftUI, and Xcode builds it on Borel's Mac.
- Try it on the live iPhone in your browser, then on your own iPhone with Borel Companion, on Pro.
- Use the phone's features: camera, Face ID, offline data, reminders and in-app purchases.
- Publish to the App Store with Pro and Apple's Developer Program.
Make a native iPhone app from my website https://example.com: keep my colours and logo, show the menu as a native list with photos, and add a favourites tab that works offline.Borel's apps use local reminders and notifications on the device; they do not send server push notifications. If push is central to your idea, that is worth knowing before you choose.
The bottom line
On iPhone in 2026, a PWA can install to the Home Screen, send web push and show a badge, which makes it a fine choice for products that live on the web. It still has no App Store listing, no Apple in-app purchase, evictable storage and fewer device features. If your app should live on the phone, build it native: start free on Borel and get a Swift app without writing the Swift.
Questions people ask
Do PWAs work on iPhone?
Yes. Open the site in Safari and choose Add to Home Screen. Since iOS 16.4, Home Screen web apps can also ask to send web push notifications and show badges.
Can a PWA be in the App Store?
Not as a PWA. Wrapping a website in an app shell is possible, but Apple says websites served in an iOS app do not make a quality app (guideline 4.2), so wrappers that add nothing are often rejected.
Can a PWA send push notifications on iPhone?
Yes, since iOS and iPadOS 16.4, if it has been added to the Home Screen and the person allows it after a tap.
Is a PWA cheaper than a native app?
Often, if you already have a website, since there is no App Store fee or review. A native app needs Apple's 99 USD a year to publish; building one with Borel is free to start.
Can a PWA use Face ID or the camera?
A PWA reaches what Safari exposes to the web, such as camera capture for photos. Native apps use Apple's frameworks directly, including Face ID unlock and motion data.
Will my PWA's data be deleted?
It can be. WebKit evicts website data under storage pressure, by least-recent use, or after a period without interaction, though Home Screen web apps are favoured for persistent storage.
Can I turn my website into a native iPhone app?
Yes. Borel reads your public website and builds a native SwiftUI app on its brand. See website to iPhone app.
Is a native app faster than a PWA?
Usually it feels faster, because it uses Apple's own interface components and runs as compiled code on the phone rather than inside a browser engine. A well-built PWA can still be quick for simple content.
Can I have both a PWA and a native app?
Yes. Many products keep a web app for desktop and other platforms and offer a native iPhone app for people who want it on their phone, sharing the same account and data in the cloud.
Does a Borel app support push notifications?
No. Borel apps use local reminders and notifications scheduled on the device, not server push.
I like the web, and a PWA is the right answer for plenty of ideas. When the app needs to feel and work like it belongs on an iPhone, I think native is worth it, and that is why Borel builds nothing else.
– Sigsten
Make your iPhone app in Borel
Describe the app you want and see its first screens before you pay anything.
See your app free