Kief Studio

A Progressive Web App Is the Best-Kept Secret in Small Business Tech

Build

  • Published
  • Updated
  • 11 min read
Violet light ring with a bright gold arc on its right side, cover for a note on progressive web apps for small business

TL;DR: A progressive web app is a website that installs on a phone or computer, opens in its own window, can work offline and can send notifications, all from one codebase and without an app store. For most small businesses whose customers already find them on the web, it is the sensible first step before a native app.

Correction, October 2026: an earlier version of this note said the European Commission fined Apple 500 million euros over web app support. That fine, announced in April 2025, was about App Store steering rules, not progressive web apps. We have rewritten the note around what the regulators, Apple, Google and the browser makers actually publish, and removed cost ranges and case studies we could not trace to a primary source.

A progressive web app answers a question I hear from owners a lot: "Should we build an app?" Usually the honest reply is that they want three things an app gives them. A spot on the customer's home screen, something that still works when the signal drops, and a way to tap a regular customer on the shoulder. A progressive web app can do all three, and it is built from the website they already need.

It has been around for years and still gets little attention outside developer circles. Here is what it is, what it can and cannot do on iPhone and Android in 2026, and how to decide whether your business should build one.

What is a progressive web app?

Mozilla's developer documentation puts it plainly: "A progressive web app (PWA) is an app that's built using web platform technologies, but that provides a user experience like that of a platform-specific app." (MDN Web Docs (opens in a new tab))

The same page lists what that means in practice. A PWA "can be installed from platform's app store or installed directly from the web." Once installed it "gets an app icon on the device" and "can be launched as a standalone app, rather than a website in a browser." It can "Work while the device does not have network connectivity," "Update content in the background," "Respond to push messages from the server" and "Display notifications using the OS notifications system."

The parts underneath a progressive web app

Two pieces turn an ordinary site into a progressive web app. The first is a web application manifest, which MDN describes as "a JSON text file that provides information about a web application," most often "the app's name and icon" that a browser needs to install it. (MDN, web application manifest (opens in a new tab))

The second is a service worker. MDN says service workers "act as proxy servers that sit between web applications, the browser, and the network," and are "intended, among other things, to enable the creation of effective offline experiences." They also run only in secure contexts, meaning the site "is served over HTTPS." (MDN, Service Worker API (opens in a new tab)) So a progressive web app starts with a site that is already secure and well built. That is a good forcing function on its own.

How a progressive web app differs from a website and a native app

MDN frames it as the best of both. A website has a "Single codebase" because "the web is inherently cross-platform," and it is easy to find because "Websites are indexed by search engines, and can be shared and accessed just using URLs." A platform-specific app gets its own icon and can work offline. A PWA aims to keep the reach of the first and add the feel of the second. (MDN Web Docs (opens in a new tab))

The search point matters more than people expect. Your app store listing is one page in someone else's catalog. A progressive web app is your website, so every page you publish can still be found in search and in AI answers.

How do customers install a progressive web app?

On the desktop, Google's web.dev course says "Desktop PWA installation is supported by Google Chrome and Microsoft Edge on Linux, Windows, macOS, and Chromebooks," and those browsers "show an install badge (icon) in the address bar." Installed apps show up in the Start menu, the dock or the launcher, and in system search. It also notes one gap: "Safari for macOS, which does not support installability" in the way the course describes. (web.dev, Learn PWA: installation (opens in a new tab))

Chrome has also made installed apps easier to come back to. Its version 134 release notes, with a stable date of March 4, 2025, describe "User link capturing on PWAs": "Web links automatically direct users to installed web apps." (Chrome 134 release notes (opens in a new tab)) Someone who installed your PWA and later taps a link to your site lands back in the app, not in a browser tab.

What changed on iPhone with iOS 26

On iPhone and iPad, installing has always meant "Add to Home Screen." What changed is the default. Apple's WebKit team wrote that for 17 years a site only opened as a web app if its code asked for it. Then: "Now, we are revising the behavior on iOS 26 and iPadOS 26. By default, every website added to the Home Screen opens as a web app." People who prefer a plain bookmark can turn off "Open as Web App." (WebKit, Safari 26.0 features (opens in a new tab))

So on current iPhones, the install step is the same gesture people already know. Your job is to make the site worth keeping on the home screen.

Can a progressive web app send push notifications on iPhone?

Yes, with conditions. WebKit announced support in iOS and iPadOS 16.4: "A web app that has been added to the Home Screen can request permission to receive push notifications as long as that request is in response to direct user interaction," such as tapping a subscribe button. Once allowed, the user manages those permissions "per web app in Notifications Settings," the same as any other app. (WebKit, Web Push for web apps on iOS and iPadOS (opens in a new tab))

Two things follow from that. On iPhone, the customer has to add your progressive web app to the home screen first, then tap to opt in. And you cannot ask for permission the second a page loads. I think both rules are good for a small business. The people who say yes actually want to hear from you, so treat that permission with care. One useful message a month beats five a week.

We are not printing an industry opt-in rate here. The figures that circulate come from vendors of notification tools, and we could not trace them to an independent study. Measure your own: how many visitors install, how many opt in, and how many come back.

What happened with Apple, web apps and the regulators?

This part of the story is often told wrong, including by us in the first version of this note.

The 2024 reversal in the EU

In early 2024, beta versions of iOS 17.4 reduced home screen web apps in the European Union to plain shortcuts as Apple prepared for the Digital Markets Act. Apple then reversed course. TechCrunch reported on March 1, 2024 that Apple "will reinstate the functionality in the upcoming public release of iOS 17.4," and quoted a European Commission spokesperson saying "A large number of these stakeholders depend on Home Screen Web Apps to run their business, to communicate with employees and customers and citizens, or to receive crucial information and updates." (TechCrunch (opens in a new tab)) The Register reported the same reversal, quoting Apple: "We have received requests to continue to offer support for Home Screen web apps." (The Register (opens in a new tab))

The April 2025 fine was about the App Store

On April 23, 2025 the European Commission found "that Apple breached its anti-steering obligation under the Digital Markets Act" and fined it 500 million euros. The decision concerns app developers' ability "to inform customers, free of charge, of alternative offers outside the App Store." (European Commission (opens in a new tab)) It is about App Store rules, not web apps.

In the UK, the Competition and Markets Authority confirmed on October 22, 2025 that Apple and Google have "strategic market status (SMS) in each of their mobile platforms," covering "operating systems, app distribution, browsers and browser engines on smartphones and tablets." (GOV.UK, Competition and Markets Authority (opens in a new tab))

What I take from all of this: regulators are paying close attention to how phone platforms treat apps and browsers, and support for web apps on iPhone has grown, not shrunk, since 2023. That is a reasonable basis for a small business to build on the web. It is not a promise about the future, so build in a way you could adjust.

What does a progressive web app cost compared with a native app?

The earlier version of this note quoted dollar ranges. We removed them because we could not find a reputable, independent source for them, and we do not publish our own prices. What we can do is explain the cost drivers, so you can compare quotes on the same terms.

The cost drivers

  • How many codebases. A native app for iPhone and Android usually means two apps plus the website. A progressive web app is the website, so there is one thing to build, test and keep patched.
  • Review and release. Native updates go through each store's review. A PWA updates when you deploy the site.
  • Store fees. Apple's Small Business Program has "a reduced commission rate of 15% on paid apps and Apple In-App Purchases" for developers under 1 million dollars in proceeds. (Apple Developer (opens in a new tab)) Google Play says that of developers subject to a service fee, "99% are eligible for a fee of 15% or less." (Google Play Console Help (opens in a new tab))
  • What you sell. For most local businesses those fees never apply. Apple's guidelines say that if an app lets people "purchase physical goods or services that will be consumed outside of the app, you must use purchase methods other than in-app purchase." (App Store Review Guidelines (opens in a new tab)) A meal, a haircut or a repair is not a digital good. The real saving from a progressive web app is building and maintaining less, not dodging a commission.
  • Device features. The more hardware you need, the more native code you need, and the cost climbs.

For a sense of what custom web work costs in this region, we wrote up what a custom web application costs in Central Massachusetts, cost drivers included.

Is a progressive web app right for your business?

Server holding a card terminal as a diner taps a card at a candlelit table, the in person side of a restaurant
A progressive web app does not replace the card terminal at the table. It handles the menu, the order ahead and the reorder.

Here is the test I use. If your customers already find you on the web and come back more than once, a progressive web app is worth a look. Think of a café in Grafton that takes orders ahead, a gym with a class schedule, a salon with bookings, or a small shop with regulars. Each needs a fast menu or schedule, saved details, and a reminder that does not feel like spam.

When you still need a native app

Some jobs still call for native code. Deep hardware access is the usual reason. MDN marks the Web Bluetooth API as "Limited availability" and says it "is not Baseline because it does not work in some of the most widely-used browsers." (MDN, Web Bluetooth API (opens in a new tab)) If your product talks to a device over Bluetooth, or your whole business depends on being found inside an app store, build native.

A sensible order of work

  1. Get the website right first. Fast on a phone, secure over HTTPS, clear about what you sell. Our Core Web Vitals guide covers the speed side, and we wrote about how Google already grades your site on a phone.
  2. Add the manifest and a service worker. Name, icon, offline fallback page, cached menu or schedule.
  3. Add one feature that earns the install. Saved order, booking history, a loyalty card.
  4. Ask for notifications only after a real action, and only for things the customer asked to hear about.
  5. Measure installs, opt-ins and return visits for a few months before you consider a native build.

Keep it simple on screen. I study behavioral psychology, and the pattern I see is that every extra choice costs attention. I wrote about how cognitive load hurts conversion rates (opens in a new tab), and an installed web app is a good place to apply it.

Frequently asked questions

Is a progressive web app the same as a website?

Technically yes. It is a website with a manifest and a service worker, so it can be installed, open in its own window, work offline and send notifications. It is still built from one web codebase.

Do progressive web apps work on iPhone?

Yes. On iOS 26, every site added to the Home Screen opens as a web app by default, and since iOS 16.4 home screen web apps can ask for push notification permission after the user taps to subscribe.

Do I need the App Store to publish a progressive web app?

No. Customers install it from your website. MDN notes a PWA can also be listed in app stores if you want that extra channel.

Will a progressive web app hurt my search rankings?

Not by itself. It is your website, so its pages can be indexed like any other. Speed, security and useful content still decide how it does in search.

Can a progressive web app work offline?

Yes, for what you choose to cache. A service worker can keep a menu, a schedule or a saved order available without a connection and send changes when the signal returns.

When should I build a native app instead?

When you need deep hardware access such as Bluetooth, or when being found inside an app store is central to how customers discover you.

This article is general information, not legal advice. Kief Studio is not a law firm, and reading it does not create an attorney-client relationship. Laws and regulations change, so check the current text and talk with a licensed Massachusetts attorney about your situation.

Where we fit

Kief Studio is in Shrewsbury, and our custom web application work is building the website, portal or internal tool your business needs around the process you already run. We map how the work happens today before choosing a screen or a stack, then build the application and the public pages in front of it. The code and the data are yours.

After launch, managed website operations means we host the site on dedicated machines with managed hosting on LTFI and keep it fast, patched and current. You never log into a server. If you only need a simple site to start, kiefstud.io gives you a free website for your business (opens in a new tab), and it is part of the same studio.

First conversation is free. No commitment.

Tell us what you want your app to do

Related articles

  1. Build

    Google Already Grades Your Mobile Website. Most Small Business Sites Still Design for a Desk.

    Google ranks your mobile website, not the desktop one. What it measures, why only 48% of mobile websites pass Core Web Vitals, and the fixes to make first.

    Amelia Gagne

  2. Build

    44% of Websites Fail Core Web Vitals in Real Visits. A Green Lab Score Won't Tell You

    Core Web Vitals come from 28 days of real visits, not a one-time lab test. What Google measures, why mobile scores lag, what small firms should fix first.

    Brian Gagne

  3. Build

    Google Just Taught Chrome How to Read Your Website Like an API. Start With Structured Data

    Chrome is testing WebMCP for AI agents. What a small business needs first: honest structured data, labeled forms and pages machines can read, per Google.

    Brian Gagne