Progressive web app development is the right buy when your customers need an app-like experience but you don't need to be discovered in the App Store. A PWA is one codebase that runs in the browser, installs to the home screen and works offline, so you build once instead of twice. If your users already know your business and arrive from a link, an email or a QR code, a PWA usually wins on cost and speed.
Key Takeaways
- A PWA is a website built to behave like an installed app: home screen icon, offline use, and notifications.
- On iPhone, push notifications work only after the user adds the PWA to the Home Screen, which is the biggest practical limit.
- You can list a PWA on Google Play; Apple rejects apps that are only a repackaged website.
- In our planning numbers a PWA costs close to 40 percent less than covering iPhone and Android natively, with one codebase to maintain.
What a PWA Can and Can't Do
Google's web.dev guide describes PWAs as web apps "built and enhanced with modern APIs to provide enhanced capabilities while still reaching any web user on any device with a single codebase." Mozilla's MDN docs add that, like a native app, a PWA "can be installed on the device, can operate while offline and in the background, and can integrate with the device and with other installed apps."
The catch is the iPhone. Apple added web push in iOS and iPadOS 16.4, but per the WebKit team's announcement, only a web app that "has been added to the Home Screen can request permission to receive push notifications." A customer who never installs it never gets your reminders.
Progressive Web App Development vs Native: The Decision Table
| Your situation | Better fit |
|---|---|
| Customers find you through the App Store search | Native |
| Customers arrive from your website, emails or a QR code | PWA |
| Reminders are the core of the product and most users are on iPhone | Native, or a PWA with a strong "add to Home Screen" step |
| Internal tool for staff | PWA |
| Small budget, need it on both platforms | PWA |
| You want a Google Play listing without a second codebase | PWA via Trusted Web Activity |
That last row is real. Google's Trusted Web Activity lets you open your PWA from an Android app and publish it to the Play Store, limited to websites you own and prove with Digital Asset Links. Apple is stricter: its App Review Guidelines (section 4.2) ask for features, content and UI that go beyond "a repackaged website." Don't count on wrapping a PWA for the App Store.
What It Costs, and the Store Fees You Skip
Build cost depends on screens and features, not on the label. As a planning number, assume a booking-style app with about eight screens takes roughly 300 hours as a PWA, and closer to 480 hours to ship on iPhone and Android with a cross-platform native framework, because of store builds, device testing and review cycles. At an assumed $45 an hour, that is $13,500 against $21,600. These are our working assumptions, not quotes.
The stores also take a cut when you sell digital goods or subscriptions inside the app. (Physical goods and services used outside the app, like a gym class, must be paid with ordinary methods such as a card under Apple's guideline 3.1.3(e), so the commission does not apply there.) Apple's Small Business Program charges 15 percent for developers who earned up to $1 million in the prior year, and 30 percent is the standard rate. Google Play's fees changed in the US on June 30, 2026, so check the current fee page rather than trusting an old number. If you sell digital content, a PWA that takes payments on your own site avoids store billing entirely.
Red Flags in a PWA Proposal
- They promise App Store listing for a wrapped PWA without mentioning Apple's guideline 4.2.
- No plan for getting iPhone users to add the app to the Home Screen, when notifications matter.
- "Works offline" with no list of which screens actually work offline.
- No testing on real iPhones, only Chrome on a laptop.
A Concrete Version
A gym with 900 members wants class booking, a membership card on the phone, and class reminders. Members already have the gym's website and get emails from it, so discovery isn't the problem.
The PWA path: about 300 hours, $13,500 at the assumed rate, one codebase, launched as a link in the welcome email with an "Add to Home Screen" prompt at the front desk. Members who install it get push reminders on both platforms; members who don't still book in the browser.
The native path: about 480 hours, $21,600, two store listings, store review on every update. It buys App Store presence the gym doesn't need, because nobody searches the App Store for one specific local gym.
For this gym the PWA saves $8,100 up front and every future change ships once instead of twice.
The Honest Counterpoint
PWAs lose when the app store is your marketing channel, when your product depends on reminders reaching iPhone users who will never install a web app, or when you need deep device features where native support is stronger. If you are building a consumer app that strangers must discover, native or cross-platform is usually worth the extra money; our comparison of React Native vs Flutter covers that path. Also, users trust store apps more by habit. A PWA asks them to try something less familiar.
Frequently Asked Questions
How much does progressive web app development cost?
It depends on screens and features. For a booking-style app of about eight screens, plan on roughly 300 hours, about $13,500 at an assumed $45 an hour, versus roughly $21,600 for native on both platforms.
Can a PWA be in the App Store?
Google Play, yes, through a Trusted Web Activity. Apple's guidelines reject apps that are just a repackaged website, so plan on the web for iPhone.
Do progressive web apps work on iPhone?
Yes. They install from Safari to the Home Screen, and since iOS 16.4 they can receive push notifications once installed.
The Bottom Line
If your customers already know you, a PWA is usually the faster, cheaper way to give them an app. If you are unsure, Sol's free Honest Read gives you a plain verdict on how to build it, and here is what the report includes. When you're ready to build, our software factory works at a fixed price, you own the code, and you get 90 days of free bug fixes after delivery. Try the numbers in the factory calculator, and read what happens after your app is built before you sign anything.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
