What a PWA can do
Technically, a PWA is a website with a few extra parts: a manifest file that defines the icon and name, and a background script (a service worker) that caches data and receives notifications. This lets the site:
- install on a phone or computer home screen and open without the address bar;
- load fast on repeat visits, because core files are already stored on the device;
- show saved pages and accept data offline, sending it later;
- send push notifications even when the app is closed;
- use the camera and geolocation, and share links through the system share menu.
PWA benefits
- One build for every device. The same code runs on iOS, Android and desktop, so development and maintenance cost less than separate apps.
- No app stores required. No Apple or Google review, no store fees and no waiting for every update to be approved.
- Instant updates. A bug fix reaches every user immediately, not whenever they get around to updating the app.
- Low barrier to entry. People open a link and start using the service right away, without downloading a large file.
- Search visibility. Public PWA pages are indexed by search engines just like a regular website.
Limitations to be aware of
- Fewer capabilities on Apple devices. Apple supports PWAs more cautiously than Google: notifications work only after the app is added to the home screen, and some features are unavailable or behave differently.
- No store listing. People won’t find a PWA by searching the App Store, so your site needs to prompt them to install it.
- Limited hardware access. Background processing, external devices and deep OS integration are native app territory.
- Users aren’t used to “installing a website.” Some people will keep using the PWA in the browser, and the design has to account for that.
When a native or cross-platform app is the better choice
If being on the App Store and Google Play matters for your product, or you need heavy camera use, background geolocation or in-app purchases, cross-platform development with Flutter or React Native is the better option. For games, complex graphics and tasks that demand maximum performance, native apps make sense.
There’s also a middle path: launch a PWA first, validate demand, and only then invest in store apps. The backend code is reused either way.
Where a PWA fits
- Customer portals and online services: bookings, orders, status tracking — where people come back regularly, but not every day.
- Internal business systems: warehouse, field staff, sales reps — when you need to roll out an app to employees quickly without publishing it.
- Online stores: a fast mobile version that can be added to the home screen, with order status notifications.
- Content products: directories, catalogs, restaurant menus that need to open even on a weak connection.
How to help people install the app
The most common PWA problem isn’t technical. Users simply don’t know the site can be added to their home screen, and on iOS the option is tucked away in the Share menu. That’s why we design installation as its own user flow:
- we suggest adding the app not right away, but after a useful action, such as the first order;
- on iOS we show a short visual hint of where to tap;
- we explain the benefit: status notifications, quick access, offline use;
- we don’t keep nagging if someone declines.
We also set up analytics to see how many people installed the app and how often they return compared to those who use the site in a browser.
Technologies we use to build PWAs
We most often build the PWA front end with React, Vue or Angular, and for projects where search traffic matters, with Next.js or Nuxt using server-side rendering. The backend is built on Node.js, Laravel or another platform that suits the project. If you already have a site on a modern framework, it can often be turned into a PWA without a full rebuild.
New PWA or upgrading your existing site
A new product is designed from the start with offline use and home-screen installation in mind: this shapes the data structure and the interface.
An existing site gets analyzed first. If it’s built on a modern framework, adding PWA capabilities is relatively simple. If it’s an older CMS with lots of plugins, it’s sometimes more cost-effective to build a separate app for the customer portal or ordering than to rework the whole site.
Either way, updates need careful planning. Because of caching, users may see an old version for a while, so we set up proper file replacement and, if needed, unobtrusively prompt users to reload the app when a new version is out.
What affects the cost
- Feature scope: how many screens and user flows, and whether there are portals with different user roles.
- Offline mode: just page caching, or full data entry with later sync.
- Notifications: whether you need them, which events trigger them and what settings users get.
- Integrations: CRM, accounting software, payments, maps.
- Starting point: building from scratch or upgrading an existing site.
To give you an accurate estimate, we first define which features must work offline and on which devices — that drives most of the scope.
FAQ
Can a PWA be listed on Google Play? Yes, Google allows publishing PWAs through a special wrapper. The App Store is trickier: Apple requires an app to offer more than a regular website.
Do push notifications work on iOS? Yes, but only after the user has added the PWA to their home screen and allowed notifications. We guide them through it.
Does a PWA affect SEO? The PWA format alone doesn’t boost rankings, but fast loading and a user-friendly mobile experience help both users and search engines.
Can a PWA accept payments? Yes. It works with the same payment providers as your website, including Stripe, PayPal, and Apple Pay and Google Pay in the browser. And there are no app store fees to pay.
How much space does a PWA take up on a phone? Far less than a regular app: only core files and the necessary data are stored.
Why Promodex
We’ve been building websites, web services and mobile apps since 2015, so we can honestly compare a PWA with the alternatives and recommend the option that fits you best. Our portfolio includes the List and Pieme projects. Your project is handled by our in-house specialists — we never hand it off to outside contractors — and after launch we keep shipping updates.
