You've probably thought about building an app for your business. And then you looked at the price tag. $50K minimum for a native iOS and Android app. Probably closer to $100K+ if you want it to actually work well. So you didn't build it. Totally reasonable.
But what if I told you there's a way to get push notifications, offline access, and an app-like experience on your customers' phones for a fraction of that cost? And you don't need Apple's or Google's permission to do it?
That's a Progressive Web App. And most small businesses have never heard of one.
What a PWA actually is
A PWA is a website that behaves like a native app. Your customer visits your site, and their browser offers to "install" it on their home screen. From that point on, it opens full-screen, works offline, can send push notifications, and feels exactly like something they downloaded from an app store.
Except there's no app store involved. No 30% cut to Apple. No review process. No waiting two weeks for an update to get approved. You push a change to your website, and every user gets it instantly.
The technology has been around for years. Google's been pushing it hard. Chrome 134 added link capturing earlier this year, so supported web links now open directly in installed PWAs. Even Apple -- reluctantly, after a 500 million euro fine from the EU -- has been forced to improve PWA support. iOS 26 now defaults every site added to the Home Screen to open as a web app.
The numbers that matter
Here's where it gets interesting for small businesses specifically.
PWA development runs $8K-$85K depending on complexity. Native iOS plus Android runs $30K-$200K+. That's a 3-8x cost difference, and you only maintain one codebase instead of three (web, iOS, Android). One distribution company replaced their native apps with a single PWA and saw a 57% cost reduction with 98% user adoption. Their revenue went up $2.8 million.
Time-to-market drops about 40% compared to building native apps for two platforms. Single codebase, no app store review process, instant updates.
And the performance data from bigger companies tells the story pretty clearly. Pinterest launched a PWA and saw a 103% increase in weekly active users. Starbucks built one that's 99.84% smaller than their iOS app and doubled daily web orders. MakeMyTrip hit a 3x conversion rate.
But here's the stat I really like: Lyft found that users on older devices take 11% more rides through their PWA than native app users. PWAs actually perform better on budget hardware because they're lighter. Your customers aren't all walking around with the latest iPhone. They're real people with real phones, and a PWA respects that.
Push notifications: honest assessment
Can PWAs do push notifications? Yes. Are they as good as native? No. Let's be honest about it.
Web push opt-in rates average 2.7-6.6%, compared to 67.5% for native apps. That's a real gap. But the engagement from people who do opt in is strong -- 12% average click-through rate, up to 30% for targeted campaigns. Jumia saw 9x more conversions on abandoned carts from web push. Lancôme's PWA drove a 17% conversion increase with 12% cart recovery from notifications.
The reframe here is simple: for a business that was never going to build a $100K native app, web push gives you engagement you'd otherwise never have. The comparison isn't "PWA vs. native app." It's "PWA vs. no app at all." And that's where most small businesses actually sit.
The Apple situation
I should address the elephant in the room. Apple doesn't want PWAs to succeed. They make billions from the App Store, and PWAs bypass that entirely.
Apple tried to kill PWA support in the EU in early 2024. The European Commission hit them with a 500 million euro fine in April 2025. The UK CMA designated Apple with Strategic Market Status over browser restrictions. Apple's "alternative browser" framework is so restrictive that zero browsers have adopted it as of early 2026.
Here's why this is actually good news: if PWAs were irrelevant, Apple wouldn't be fighting this hard. The regulatory pressure is only going one direction. PWA capabilities on iOS have been getting better, not worse, because governments are forcing the issue.
And about 55% of US web traffic comes from Android, where PWAs are first-class citizens. For local services, creators, and small retailers, your customer base probably skews even higher toward Android.
What this looks like in practice
A real example: an auto repair shop in Colorado rebuilt their site as a PWA after their old site loaded in 4-6 seconds with a 63% bounce rate. Customers started browsing more pages, checking promotions, and booking online instead of calling. A small local business, not a tech company, getting real results from technology that's been sitting right there.
A retail brand called Butcher of Blue saw mobile users jump 154% and conversions jump 169% after going PWA.
The PWA market is projected to hit $21-72 billion by the mid-2030s. E-commerce and retail already make up 31.4% of adoption. But almost all the case studies are still from enterprise brands. The SMB adoption gap is the real opportunity.
Who this makes sense for
PWAs aren't the right answer for everything. If you need deep hardware access -- Bluetooth, NFC, advanced camera controls -- you still need native. If your entire business model depends on being discovered in the App Store, a PWA won't help with that.
But if you're a local service business, a creator selling digital products, a small retailer, a restaurant, a gym, a salon -- basically any business where your customers already find you through the web -- a PWA gives you app-level engagement without the app-level budget.
You get offline access. You get push notifications. You get a home screen icon. You get instant updates. You get one codebase. And you skip the 30% app store tax entirely.
The "PWA first, native only if you prove you need it" approach has become standard advice from development shops in 2025-2026. For good reason.
We build these
At Kief Studio, we build PWAs for clients who want app-level capability without burning their entire tech budget on a native build. One codebase, installable, push-capable, works on everything from the latest flagship to a three-year-old budget Android.
First conversation is free. No commitment. Hit us up at kief.studio/contact.