What works on iOS today
iOS has come a long way. A PWA installs to the home screen, opens full-screen with its own icon, runs offline through service workers, and — since Safari 16.4 — can even receive web push once it's installed to the home screen.
For a large share of products — content, tools, booking, dashboards, storefronts — an installed PWA feels genuinely app-like on an iPhone. The gaps only start to matter for specific advanced features.
- Add to Home Screen with full-screen, standalone launch
- Offline support and caching via service workers
- Web push notifications after the user installs (iOS 16.4+)
- Camera and geolocation access with permission
- Fast, smooth performance for most app categories
What still doesn't work or is limited
Here's the honest part. iOS has no automatic install prompt — users must tap Share, then 'Add to Home Screen,' which many don't know to do without guidance. Some hardware APIs available on Android (like Web Bluetooth and NFC) aren't there.
Storage can also be evicted when the device is low on space, and certain background capabilities are more limited than native. None of these are usually dealbreakers, but you should know them before you build.
- No one-tap install prompt — users must add it manually via Share
- Web push requires install first, and a recent iOS version
- No Web Bluetooth or NFC access in Safari
- Cached data can be evicted under storage pressure
- Background sync and background tasks are more limited than native
- In-app purchase through Apple's billing isn't available to a pure PWA
How to decide if iOS gaps are dealbreakers
The right question isn't 'is a PWA perfect on iOS' — it's 'does my feature list hit any of these limits.' If you don't need Bluetooth, NFC, or heavy background processing, iOS constraints rarely block you.
If you do need those, we'll say so plainly and may recommend a hybrid wrapper or native build for iOS while keeping the web app everywhere else. Bring your must-have features to a free consultation and we'll give you a clear yes, no, or hybrid answer.
- Map your must-have features against the iOS limits above
- Web-first products (content, commerce, tools) usually pass cleanly
- Hardware-heavy or background-heavy apps may need a wrapper on iOS
- You can ship a PWA everywhere and wrap only iOS if needed
- We give a straight recommendation, not a one-size pitch
More on progressive web apps
Frequently asked questions
Do PWAs actually work on iPhones?
Yes. They install to the home screen, run full-screen, work offline, and can send push notifications once installed on iOS 16.4 or later. The main catches are a manual install step and a few missing hardware APIs — which most apps never need.
Why doesn't my iPhone show an install button?
Apple doesn't support the automatic install prompt that Android has. On iOS, users install by tapping the Share icon in Safari and choosing 'Add to Home Screen.' We build clear in-app guidance so iOS visitors know how, since it isn't obvious on its own.
Should I just build native for iOS instead?
Only if your app genuinely needs what iOS PWAs can't do — deep Bluetooth/NFC, heavy background work, or Apple in-app billing. For most products the PWA is enough. If not, a common answer is a PWA everywhere plus a thin native wrapper for iOS. We'll help you pick.