App stores have been the default distribution channel for mobile software for fifteen years. For many apps, that makes sense. For AI assistants, it increasingly does not. Progressive Web Apps — PWAs — offer a compelling alternative: no app store approval required, automatic updates, and an experience that is indistinguishable from a native app for most users.
What Is a Progressive Web App?
A PWA is a website that can be installed on a device and behave like a native app. The technical requirements are: served over HTTPS, includes a web manifest file that declares the app's name, icons, and display mode, and includes a service worker for offline caching. That is all. A well-built PWA runs fullscreen, appears on the home screen, has its own icon, and works offline for previously loaded content.
From a user's perspective, a PWA looks and feels like an app. From a developer's perspective, it is built with web technologies (HTML, CSS, JavaScript) and deployed instantly — no App Store review, no 30% commission, no waiting for approval.
Installing a PWA
On iPhone (Safari): tap the share button, then "Add to Home Screen." On Android (Chrome): tap the three-dot menu, then "Add to Home Screen" or "Install App." After installation, the app appears on your home screen and launches fullscreen, just like a native app.
Hey Friday is built as a PWA. There is nothing to download from the App Store or Google Play. Open heyfriday.co in your browser, follow the install prompt, and the full AI assistant is on your home screen in seconds.
Automatic Updates Without App Store Delays
Native apps must be submitted to app stores for review before updates reach users. This review process takes days, and Apple's review is notoriously inconsistent. Urgent bug fixes can be delayed by days or weeks. Users who do not have automatic updates enabled may be running versions that are months old.
PWAs update automatically. When the developer deploys a new version, every user gets it the next time they open the app — no review, no waiting, no user action required. For AI assistants, which update frequently as models change and interfaces improve, this is a significant advantage.
Privacy Advantages of PWAs
Native apps have access to system APIs that PWAs do not. Push notifications, contacts, location in background, camera and microphone at any time — native apps can request access to these without explicit per-use permission. PWAs have more limited access, which means less attack surface and less risk of background data collection.
PWAs also cannot be tracked by app stores. Apple and Google know which apps you install from their stores. They collect this data for advertising and personalization. A PWA installed from a browser leaves no record with any platform.
Limitations to Know
PWAs are not perfect. On iOS specifically, Apple has historically limited PWA capabilities compared to Android. Push notifications on iOS required iOS 16.4 or later. Some device APIs — like background processing and certain sensor access — are restricted. For AI assistants, these limitations rarely matter: the core functionality (conversation, voice input, image generation) all works well in PWAs on both platforms.
The Future of Mobile AI
The App Store model made sense when distribution was hard and software quality control was a real problem. For web-based AI applications, the App Store creates friction without adding meaningful value. Users pay with their time (downloads, updates), developers pay with 30% of revenue and submission delays, and platform holders collect rent for infrastructure that PWAs do not need.
PWAs will not replace native apps for everything. Games, camera apps, and deeply hardware-integrated software will remain native. But for AI assistants — which are fundamentally web services wrapped in an interface — PWAs are not just adequate. They are better.
What a PWA Can and Cannot Reach
The honest version of the PWA story is that the capability gap has narrowed dramatically but has not closed. What a PWA can do today:
- Microphone and camera access, with permission
- Offline operation and background caching
- Home screen installation with a full-screen, browser-chrome-free window
- Local storage of meaningful size
- Geolocation, clipboard, file picking, and share targets
- Push notifications — including on iOS, though only once the app has been added to the home screen
What remains out of reach or unreliable:
- Always-on background listening for a wake word. This is the substantive limitation for a voice assistant, and it is why wake-word support differs so much between platforms.
- Deep system integration — default handler status, lock screen widgets, system-wide shortcuts.
- Bluetooth and NFC on some platforms.
- Background execution once the app is closed.
For an assistant you open deliberately, none of these matter. For one you expect to summon by speaking across a room, the first one matters a great deal.
iOS and Android Are Not the Same PWA
Guides tend to describe "PWA support" as a single thing. In practice the two platforms differ enough to change what you should expect.
On Android, installation is prompted by the browser, the app gets its own entry in the app switcher, storage limits are generous, and background capabilities are broader. It behaves close to a native app.
On iOS, installation is manual — Share, then Add to Home Screen, a step most users never discover unaided. Storage may be evicted if the device is under pressure and the app has not been used recently. Push notifications work, but only after home-screen installation. And continuous background audio is unavailable, which is precisely why iOS voice assistants delivered as PWAs typically ask you to set up a Siri Shortcut instead of offering a wake word.
Why Developers Choose This
The user-facing case is no download and no store. The developer case is stronger still, and it explains why serious products are shipping this way rather than merely hobby projects.
There is no platform commission on payments taken outside an app store. There is no review queue between finishing a fix and shipping it. There is one codebase rather than three. And there is no possibility of being removed from a store by a policy change outside your control — a real consideration for anything in a category a platform owner also competes in.
The trade is discoverability. App stores are search engines with enormous traffic, and a PWA is not in them. That is a genuine cost, and it is why PWAs work best for products people arrive at through the web rather than by browsing a store.
How to Tell if a Site Is a PWA
Two quick checks. On Android Chrome, open the three-dot menu and look for "Install app" or "Add to Home screen" — if the browser offers installation, the site has declared itself installable. On any browser, add /manifest.json to the site's root URL; a PWA will return a JSON file naming the app, its icons and its display mode.
A third signal is behaviour: put the device in airplane mode and reload. A well-built PWA will still render its shell rather than showing a connection error.