Quick answer. A good PWA development company shows you installable PWAs, tests on real iPhones, and says plainly what iOS cannot do. Check ten things before you hire, starting with push notifications, which on iPhone need iOS 16.4 or later and a Home Screen install. A PWA suits you if you need no Bluetooth, NFC, background tasks or App Store listing.
Most PWA company pages are written by PWA companies, and they stress the benefits and skip the iPhone limits. This post gives you a six-question test for whether a PWA fits your business, a plain list of what a PWA cannot do on an iPhone, and ten questions that expose whether a company knows the difference. One tip comes first: before you sign, install the company's best PWA on your own phone and try it with the Wi-Fi off.
What is a PWA, in plain terms?
A PWA, or progressive web app, is a website built to behave like an app. web.dev describes it as "a web app that uses progressive enhancement." Once a user installs it, it gets a Home Screen icon, opens in its own window and can work offline.
For a business, that means one codebase that runs in the browser and on a phone, no app store review for updates, and no store accounts to set up. The trade-off is that the phone's browser, not the app store, decides what the app can do. On Android that is rarely a problem. On iPhone it often is, so that is where to test a company.
Does your business need a PWA or a native app?
Answer these six questions before you talk to any company. The first four come from the checklists in Emergen's 2026 guide (updated 14 October 2026) and Toimi's October 2026 guide. Both sell development, so the cut-off below is our own.
# | Question | What a yes means |
1 | Do you need an App Store listing for discovery or trust? | A PWA cannot be listed in Apple's App Store. Google Play accepts PWAs packaged as Trusted Web Activities. |
2 | Do you need Bluetooth, NFC or tasks that run while the app is closed? | Not supported for PWAs on iPhone. Choose native. |
3 | Must iPhone users get push notifications without installing the app first? | Not possible. Push needs a Home Screen install. |
4 | Is heavy animation or graphics central, as in games or video editing? | Native is the safer choice. |
5 | Do you sell digital subscriptions or content? | A PWA avoids store fees (Apple charges 30%, or 15% in its Small Business Program) but you handle payments yourself. |
6 | Do you need to ship in weeks and update often? | A PWA updates on the next page load. Native releases go through store review. |
How to read it. Zero or one yes on questions 1 to 4: start with a PWA. Two or more: build native, or launch a PWA first and add native later. Emergen puts the line at two yeses and Toimi at three, and this version sits between them. Questions 5 and 6 favor a PWA and do not count toward the total.
What can a PWA not do on an iPhone?
This is the table most vendor pages leave out. It combines Apple's own WebKit announcement (16 February 2023) with MobiLoud's 2026 iPhone guide and Toimi's guide. MobiLoud sells app wrappers, so treat its framing as a vendor view. Check the facts against current Apple documentation before you promise a client anything.
Feature | What happens on iPhone |
Install | No install prompt. The user taps Share, then Add to Home Screen. |
Push notifications | Need iOS or iPadOS 16.4 or later and a Home Screen install. The app must ask permission in response to a tap. |
Push content | No images or action buttons, and every push shows a visible notification. |
Background work | Background Sync, Periodic Background Sync and Background Fetch are not supported, so the app cannot refresh or retry while closed. |
Stored data | Safari deletes a site's data after seven days without a visit. Home Screen web apps are treated better. |
Hardware | No Bluetooth or NFC. Camera works. Location works only while the app is open. |
App Store | Not listed. Apple's guideline 4.2 says an app should go beyond "a repackaged website." |
None of this makes a PWA a bad choice. It makes the push opt-in flow, offline behavior and install prompts design work, and a company that has not done that work on iPhone will find out on your budget.
What does a PWA cost?
I found no PWA-specific price range in the vendor pages I opened. Emergen and Toimi say outright that they give none, and Codica's guide gives none. A PWA is a web build, so the closest published figures are web ranges.
Item | Figure | Source |
Web MVP | $15,000 to $80,000 | Helpware, updated 30 Jul 2026 |
Mobile MVP, for comparison | $25,000 to $120,000 | Helpware |
PWA MVP timeline | 4 to 8 weeks | Toimi's own page, a vendor claim |
Apple Developer Program | $99 a year, only if you package for iOS | |
Google Play registration | $25 one time, only if you package for Android | Toimi |
Maintenance | One stack to maintain, against two stacks plus yearly OS upgrades for native | Toimi |
Helpware and Toimi both sell development. Use the table to sanity-check a quote, not to set a budget.
VisualQube prices web apps and PWAs after a scoping call, because scope drives the number more than the technology does.
The 10 questions to ask a PWA development company
Ask them on the first call and again when the written proposal arrives. A good answer is specific. A walk-away answer is vague or too confident.
# | Ask | A good answer | Walk away if |
1 | "Which PWAs have you shipped, and can I install them on my own iPhone and Android phone?" | Live links you install and try | Screenshots only, or no PWA in the portfolio |
2 | "What do you test on real iPhones?" | Home Screen install, push opt-in and offline mode, on named iOS versions | Simulators only |
3 | "How will the push opt-in work on iPhone?" | A tap-triggered prompt shown after the user adds the app to the Home Screen | "Push just works" |
4 | "What works offline in my app, and what does not?" | A written list of cached screens and actions | "Everything works offline" |
5 | "How do you handle Safari clearing stored data?" | A plan to re-sync user data and encourage Home Screen installs | They have not heard of it |
6 | "What speed targets will you commit to?" | Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less, Cumulative Layout Shift of 0.1 or less | No numbers |
7 | "Do you package for Google Play, and what is the App Store plan?" | Trusted Web Activity for Google Play, and a clear statement that a PWA cannot be listed in the App Store | A promise of App Store listing without a native build |
8 | "Which framework and hosting do you recommend, and why?" | A reason tied to your needs | "We always use the same stack" |
9 | "Who owns the code, the domain, the hosting and the push accounts?" | A signed assignment to your company | A license only, or no transfer date |
10 | "What does support cost after launch, and who handles browser and iOS changes?" | A priced monthly or annual plan | "Available upon request" |
On question 6, the thresholds are Google's published "good" targets at the 75th percentile of page loads, listed on web.dev.
How to read the result. Shortlist a company with eight or more good answers. A walk-away on question 1 or 9 ends the search at any total. The cut-offs are our rule of thumb and have not been tested on a sample of projects.
Codica's selection guide covers portfolio, framework and Agile questions, which are a useful base. The questions above add the iPhone, offline and ownership checks it skips.
What should be in writing before you sign?
• Devices and versions tested. Name the iPhone and Android versions, and the browsers.
• Offline scope. Which screens and actions work without a connection.
• Speed targets. The three numbers from question 6.
• Packaging. Whether a Google Play version is in scope, and that an App Store listing is not.
• Ownership. A written assignment of code and design, with your own domain, hosting and push accounts. The US Copyright Office's Circular 30, revised August 2024, says a commissioned work counts as made for hire only if it falls in one of nine listed categories and both sides sign an agreement saying so. Ask for an explicit assignment, and have a lawyer read the contract. This is general information, not legal advice.
PWA first, native later, or both?
Toimi suggests an order that fits most small businesses: make the mobile site fast, build a PWA with an offline catalog and push, wrap it for Google Play with a Trusted Web Activity, and build native iOS only if usage data shows a loyal, repeat group. The advantage is that you spend on native only after the PWA proves demand. If your idea is still unproven, the same logic applies to the whole product, and our guide to MVP development services walks through it.
Score VisualQube the same way
VisualQube is a US team based in South Jordan, Utah, with design and development in-house. Run us through the same ten questions.
• Proof: ask to see a PWA we built and install it on your own phone, as question 1 says.
• iPhone testing: ask which iOS versions and devices we test on before the proposal is signed.
• Ownership: ask for the code, domain, hosting and push accounts to be assigned to your company in writing.
• Support: ask for a priced support plan, with browser and iOS changes named in it.
If we fall short on question 1 or 9, hire someone else. If you already hold a proposal, or just an idea, book a free scoping call and tell us what the app has to do. We will say whether a PWA, a native app or both fits, and score any proposal you bring. You can also read about our website design and development work.
Frequently asked questions
Is a PWA cheaper than a native app?
Usually, because it is one codebase and needs no store accounts. Helpware's 2026 ranges put a web MVP at $15,000 to $80,000 and a mobile MVP at $25,000 to $120,000. No vendor I opened gave a PWA-specific price, so get a written quote and compare scope.
Can a PWA send push notifications on an iPhone?
Yes, with conditions. Apple's WebKit team says push works on iOS and iPadOS 16.4 or later, for web apps the user has added to the Home Screen, and the app must ask permission in response to a tap. Push does not work from a regular Safari tab.
Can a PWA be listed in the Apple App Store?
Not as a PWA. MobiLoud reports that PWAs cannot be listed, and Apple's guideline 4.2 says an app should go beyond "a repackaged website." A native wrapper with real native features is a different build. Google Play does accept PWAs packaged as Trusted Web Activities.
How long does it take to build a PWA?
Toimi's own page lists a PWA MVP in 4 to 8 weeks, which is a vendor claim. Broader MVP guidance from Empat and Frame Sixty is 6 to 16 weeks. Ask any company for a phased schedule with dates tied to deliverables, and agree it in writing.