The article
Your customers already use your service on their phones, through the browser: from a link in a text message, a search, a bookmark. A progressive web app lets that same web app sit on the home screen, open without a connection and send notifications, with no app store between you and them. Whether that is enough for your product is the first question; the second is how to tell a progressive web app development company that can build one from a company that only says it can.
In October 2026 I read the five company pages Google showed me for this search. Not one says what a PWA cannot do on an iPhone, and not one explains how users get a new version once the app sits cached on their phones.
I also loaded each of the five pages, switched the browser offline and reloaded it. None opened: none of them registers a service worker, the part of a PWA that works without a connection, and only one has the manifest that makes a site installable. Our own company site is not a PWA either, and it has no need to be: people read it once and then call. The test belongs on the app you are buying, and a five-minute version of it is below. Five pages are a small sample; the test works on any app.
The short version
| Question | Our answer |
|---|---|
| What it is | A web app that installs from the browser, opens offline and can send push notifications, from one codebase for phones, tablets and desktops |
| Where it fits | Ordering, booking, client portals and field work |
| Where it does not | Deep background work, hardware a browser keeps closed, a product that must sit in the App Store |
| Price | A first version from $5,000; the screens, the offline work and the integrations set the rest |
| How it ships | On your domain with https, installed from a link, updated without a store review |
| Who builds it | Our developers near Kyiv, on a contract with our US company |
What makes a web app progressive
Three parts, and each has one job:
- https. The app travels encrypted, and browsers allow the other two parts only on a secure address.
- A manifest. A small file with the app's name, icon and colors, which lets a phone or a laptop install it with its own icon and window.
- A service worker. A script between the app and the network that keeps screens and data on the device and receives push messages when the app is closed.
With those in place, users get:
- Its own icon on the home screen, added from the browser.
- Its own window, without the browser's address bar.
- Screens and data kept on the device, so it opens offline.
- Push notifications, on iPhone too once the app is on the home screen.
- New versions on the next launch, with no store review.
- A link anyone can open, and pages search engines can index.
PWA, native or cross-platform
The choice follows from what the app needs from the phone and from the stores:
| What the app needs | What to build | Why |
|---|---|---|
| One app for every screen, installed from a link, updated without store review | A progressive web app | One codebase; fits ordering, booking, client portals and field work |
| Deep background work, hardware access, the newest system features | A native app in Swift or Kotlin | Browsers hold these back |
| A listing in both the App Store and Google Play, from one codebase | A cross-platform app in Flutter or React Native | The App Store expects more than a wrapped website |
| A listing on Google Play only, for the PWA you have | The PWA packaged as a Trusted Web Activity | Google Play accepts that package |
Forward this table to whoever decides the budget: it answers the "do we need a store app" question in one read.
What works on iPhone, and what does not
iPhone is where most PWA plans meet their limits, so here they are in one place:
- Installing. Safari adds the app to the home screen, but it shows no install banner of its own; the app should show people how to add it.
- Notifications. Push works once the app is on the home screen and the user allows it, not from a tab in the browser.
- Hardware. Some device features, Bluetooth and NFC among them, stay closed to web apps on iPhone.
- The App Store. It expects more than a wrapped website. When a store listing matters, a mobile app is the honest answer.
Android is more open: Chrome offers to install a PWA, and Google Play takes one packaged as a Trusted Web Activity.
Offline is a list of decisions
A PWA does not work offline by itself: someone decides, screen by screen, what it does without a connection. We settle that in discovery, together with what each notification says:
- What must open with no connection: today's orders, the day's schedule, the last screens a person used.
- What may be read but not changed: a catalog, the history.
- What waits to sync: a form or an order made offline stays on the device and goes out when the connection returns, and the user can see that it is waiting.
- What must refuse: payments, and anything that depends on a live price or live stock.
- Who wins a conflict: two people changed the same record while both were offline.
Even a plain website should not fall apart when the signal drops. On our own company site, the page stays on screen, a note says the next page opens once the connection is back, and that page then opens by itself. A PWA goes one step further: it opens with no connection at all.
Notifications people keep
A notification claims that its message is worth an interruption, and people tend to switch them off once that claim turns out false. Three rules keep them on:
- Ask when it helps. Request permission after the first order or booking, when a reminder obviously serves the person, not on the first screen.
- Send what they asked for. Their order is ready, their appointment is tomorrow, their turn has come; a newsletter belongs in email.
- Let them choose the kinds. Someone who wants order updates but not offers should be able to keep one and drop the other.
On iPhone each permission is worth more, because only people who added the app to the home screen can receive notifications at all. What every notification says, and when, is part of discovery, not an afterthought before release.
New versions without a store
A new version reaches users on their next launch, with no store review in between. The other side of that freedom: a service worker that keeps files too eagerly keeps showing people the old app. We met the same trap on a personal site we built: phones went on showing an old version until we stopped caching the pages themselves and kept long caches only for files whose names change with every release. In a PWA the fix has three parts: every file carries its version in its name, the app's own page stays out of long caches, and the app tells users when a new version is ready instead of swapping it under their fingers.
Progressive web app development services, front to back
Our progressive web app development service takes in the screens and everything behind them:
- The app in React, Next.js or Vue, designed for the phone first.
- Offline rules: what is cached, and what waits to sync when the connection returns.
- Push notifications and the server that sends them.
- The backend and the admin on Django, FastAPI or Laravel, with PostgreSQL.
- Sign-in, payments with Stripe and text messages with Twilio.
- Your current web app, made installable and ready for offline use.
The parts of a PWA are things we ship on other projects. The players of Raina Music answer a manager's phone at once over a two-way WebSocket, and SaneBox's Android app brings people back with push notifications through Firebase Cloud Messaging. If you already have a web app, we read its code first and tell you what turning it into a PWA involves.
How a PWA project runs
- Call. Who uses the app, on which devices, and what it must do without a connection.
- Rough estimate, free. Enough to decide whether to go ahead.
- Discovery. Which screens work offline, and what each notification says.
- Sprints. Two weeks each, ending with a demo you open on your own phone.
- Release. Live on your domain with https; users install it from the browser.
A first version starts at $5,000; how many screens, how much offline work and which integrations decide the rest, and the rough estimate costs nothing. One codebase serving every screen is a PWA's economy; the iPhone list above is its price. Where each of our services starts is on the pricing page.
What a PWA project needs from you
Most of what decides a PWA lives on your side, so these are the things we ask for at the start:
- The devices your users carry. Your analytics show the share of iPhones, and that share decides how much the app must explain about the home screen and how far it can lean on notifications.
- The screens that matter without a connection, in order of importance.
- The words of each notification, and the moment each one helps.
- A short name and an icon. On a home screen the name sits under the icon, and a long one gets cut.
- Access to your current web app and its hosting, if we are making an existing app installable.
- One person who opens the demo on their own phone every two weeks and says what feels wrong.
How to test a progressive web app development company in five minutes
Whether you hire a progressive web app development agency, a studio or one freelancer, ask for a live PWA they built and run this on your own phone:
| Step | What to do | What you should see |
|---|---|---|
| 1 | Open the link in Chrome on Android or Safari on iPhone | Chrome offers to install it, or the app shows how to add it to the home screen |
| 2 | Add it and open it from the icon | Its own window, without the browser's address bar |
| 3 | Switch on airplane mode and open it again | The app opens and says what works offline, not a browser error |
| 4 | Fill in a form offline, then reconnect | The entry waits, then goes, and you can see that it went |
| 5 | Wait for the notification request | It comes after you did something a notification would help with, not on the first screen |
| 6 | Ask how a new version reaches you | On the next launch, with a note that something changed |
| 7 | On a laptop, open Chrome's developer tools and the Application tab | A manifest and a running service worker |
Seven green rows mean the PWA was built on purpose, not switched on in a settings panel.
Progressive web app developers on a US contract
You sign with our US company, and the developers work near Kyiv, usually seven hours ahead of Miami, so the end of their day overlaps with your morning. Every progressive web app developer on your project is someone you know by name and write to directly. Clients rate us 5.0 on Clutch from 26 verified reviews as of September 2026, and none of them is negative.
Tell us what the app must do on the phone and offline, and you get a rough estimate, free. A PWA is one of our web application development services; if your app is mostly a process of your own, read about custom web applications; if many departments will use it, about enterprise web apps; and if it is a first version to test an idea, about web apps for startups.
