As of Safari 17.4, iOS has finally shipped Web Push, home-screen installability with badging, and proper service worker background sync — the last three holdouts that made Apple the reason every small business was quoted $40,000 for a native app they didn’t need. According to web.dev case studies, businesses that ship a progressive web app instead of a native build routinely see 3x-6x higher install conversion, because nothing stands between “I like this site” and “it’s on my home screen now” — no App Store review, no 30% tax, no 150MB download.
If you’ve been putting off the mobile app because the numbers never worked, 2026 is the year the numbers work. Progressive web apps for small business are no longer the compromise option. For most service businesses, shops, and local brands, the PWA is the app. At TheBomb®, we’ve been shipping installable web apps since 2018 — back when iOS would politely ignore half of them — and the difference now is night and day.
What Is a Progressive Web App, Really?
A progressive web app is a website that meets three technical criteria: it’s served over HTTPS, it ships a valid web app manifest, and it registers a service worker. That’s it. Once those three boxes are checked, browsers let the site behave like a native app — installable to the home screen, runnable offline, able to receive push notifications, and launchable in its own window without browser chrome.
The “progressive” part is the important bit. Every PWA is first and always a website. If a visitor lands on it in an old browser or skips the install prompt, it still works. But on a modern phone or laptop, the same URL can tap into capabilities that used to require a native binary: camera access, geolocation, file system handles, Bluetooth in many cases, payment request APIs, and background sync. One codebase. One deploy. Every platform.
The Three-Pillar Checklist
- HTTPS — non-negotiable; service workers refuse to register otherwise.
- Web app manifest — a JSON file declaring name, icons, theme colour, display mode, and start URL.
- Service worker — a background script that intercepts network requests and enables offline and push.
What’s Changed in 2026 — iOS, Push, Badging, App Stores
For a decade, the honest answer to “can my small business skip the native app?” was “on Android yes, on iPhone no.” Apple treated PWAs as second-class citizens — no push, no badging, no install prompt, aggressive 7-day storage eviction that wiped your login if users didn’t return within a week. That era is over.
According to Apple’s WebKit release notes, iOS now supports Web Push notifications for home-screen PWAs, badging on app icons, and the Declarative Web Push proposal for reduced battery drain. Chrome Platform Status confirms that Chromium browsers (Chrome, Edge, Brave, Arc, Opera) now ship the full Web App API surface including File System Access, Window Controls Overlay for desktop PWAs, and protocol handlers that let your app register as the default for mailto:, tel:, and custom schemes.
The practical effect: the 2020 list of “things PWAs can’t do on iPhone” has collapsed to a handful of edge cases. If your shortlist of required features is push notifications, offline mode, camera, location, payments, and a home-screen icon, you can ship a PWA today and stop paying the app-store tax.
What Still Has Gaps
- Bluetooth Low Energy — Safari still doesn’t ship Web Bluetooth; Chrome/Edge do.
- Deep OS integration — widgets, Live Activities, Siri shortcuts remain native-only.
- App Store discovery — PWAs can be listed via Microsoft Store and Google Play (through Trusted Web Activities), but not the iOS App Store directly.
When Should a Small Business Ship a PWA Instead of a Native App?
Ship a PWA when your mobile experience is mostly content, commerce, or a simple utility, and ship native only when you genuinely need OS-level integration. That’s the 134-word version. Here’s the longer answer.
The honest test is this: write down every feature your app actually needs. If the list is “browse a catalogue, take a booking, send push reminders, work offline in a sketchy rural cell signal, let the customer pay” — that’s a PWA. If the list includes “read the user’s health data from the Apple Watch, integrate with CarPlay, run a custom ML model on the Neural Engine” — that’s native. Most small businesses, including nearly every local service business we’ve built at TheBomb®, fall firmly in the first bucket. See our development services for what we typically scope.
PWA Wins When
- Your users are mostly on the web already and you want to convert them to repeat visitors.
- You update the product often and don’t want to wait for App Store review.
- You serve a region with flaky connectivity — offline-first is a killer feature.
- Your team is small and you can’t justify paying for iOS + Android + web in parallel.
- Budget is under $50K and timeline is under 4 months.
When Native Still Wins
There’s no point being ideological about this. Native apps still win in specific scenarios, and pretending otherwise wastes client money on the wrong direction.
Native wins when you need reliable Bluetooth Low Energy (fitness trackers, IoT hardware, POS hardware), tight OS integration (Siri shortcuts, iOS widgets, CarPlay, Wear OS tiles), heavy on-device ML (custom CoreML or TensorFlow Lite models using the Neural Engine or Tensor cores), or discovery-driven distribution where being found in the App Store search is itself the business model — games, dating apps, and anything where the category is crowded and SEO doesn’t reach the audience.
Native also still wins for regulated industries where app store review is effectively a compliance layer your buyers expect — healthcare, banking, and anything HIPAA-adjacent in the US.
For a local plumber, dental clinic, restaurant, coffee shop, home builder, or boutique retailer — native is overkill. You’re building a discoverability and retention tool, not a platform product. Put the money into web design and SEO instead.
The Minimal PWA Recipe (Manifest, Service Worker, Install Prompt)
A complete PWA has three files and roughly fifty lines of code. Here’s the skeleton we reach for when converting an existing marketing site.
1. The Web App Manifest
/manifest.webmanifest — referenced from the <head> via <link rel="manifest" href="/manifest.webmanifest">.
{
"name": "Your Business",
"short_name": "Business",
"start_url": "/",
"display": "standalone",
"background_color": "#0a0a0a",
"theme_color": "#8422dd",
"icons": [
{ "src": "/icons/192.png", "sizes": "192x192", "type": "image/png" },
{ "src": "/icons/512.png", "sizes": "512x512", "type": "image/png", "purpose": "any maskable" }
]
}2. The Service Worker
/sw.js — the tiny stale-while-revalidate cache that gives you offline for free.
const CACHE = 'site-v1';
self.addEventListener('install', (e) => {
e.waitUntil(caches.open(CACHE).then(c => c.addAll(['/', '/offline.html'])));
});
self.addEventListener('fetch', (e) => {
e.respondWith(
caches.match(e.request).then(hit =>
hit || fetch(e.request).catch(() => caches.match('/offline.html'))
)
);
});Register it from your site’s main script: if ('serviceWorker' in navigator) navigator.serviceWorker.register('/sw.js');
3. The Install Prompt
Chromium browsers fire a beforeinstallprompt event you can capture and re-trigger from a button. iOS ignores it and uses Share → Add to Home Screen — still fine, but design your site copy accordingly.
For anything beyond this skeleton — push subscriptions, Workbox precaching strategies, background sync — graduate to web.dev’s Learn PWA course, which remains the definitive free resource.
Distribution — Microsoft Store, Play Store, and Direct-Install
Skipping the App Store doesn’t mean skipping discovery. There are three legitimate channels for getting a PWA in front of users in 2026, and smart operators use all three.
Direct install from the web is the default and the best one. A visitor browsing on their phone gets a subtle “Install” prompt after meeting engagement heuristics (or tapping your custom button). On desktop, an icon appears in the omnibar. No store review, no 30% cut, no waiting.
Google Play accepts PWAs via Trusted Web Activities — a thin Android wrapper around your live site that qualifies as a “real” app for Play listing purposes. Tools like PWABuilder (Microsoft’s open-source PWA packaging tool) generate the wrapper for you in a few clicks.
Microsoft Store goes further — it accepts PWAs directly, no wrapper needed. Submit your manifest URL, fill in the metadata, and you’re in the Windows store alongside native apps.
iOS App Store remains the holdout; Apple doesn’t accept pure PWAs. The workaround is Capacitor or a similar wrapper if you truly need App Store presence — but honestly, for most small businesses, the answer is to drive iPhone users to “Add to Home Screen” from your site and skip the store entirely.
TheBomb® Ships PWAs, Not Shelfware
We’ve watched too many small businesses burn $40K-$80K on a native app that hit the store, got 400 downloads, and then sat abandoned after the quarterly iOS update broke something nobody was paid to fix. A progressive web app skips all of that. It’s the same codebase as your website, it updates instantly, and it costs a fraction of a native build to maintain.
Ready to stop paying the app-store tax?
- Custom Development — We build PWAs with offline-first, push, and install flows baked in.
- Web Design — Because the PWA is only as good as the site behind it.
- Ongoing Maintenance — Service workers, cache busting, and push key rotation handled.
Book a free strategy call and we’ll tell you straight whether a PWA or a native build is the right move for your business. No pitch decks, no 40-slide proposals — just the answer.
Key Takeaways
- iOS caught up in 2026. Web Push, badging, and home-screen install now work on iPhone. The last honest reason to skip PWAs for Apple users is gone.
- PWAs beat native for most small businesses. Service businesses, local retailers, and content-first brands don’t need the Neural Engine — they need install conversions and fast updates.
- Native still wins for hardware, OS integration, and app-store-discovery businesses. Bluetooth LE, CarPlay, widgets, and regulated industries are legitimately native territory.
- The minimal recipe is three files. A manifest, a service worker, and an install-prompt hook. Under 50 lines of code will get you 80% of the benefit.
- Distribute through direct-install, Play Store (via TWA), and Microsoft Store. Skip the Apple App Store queue entirely — drive iPhone users to “Add to Home Screen.”
