PWA

We turn a website into an app that installs to the phone screen: manifest, service worker, offline cache and push notifications. No app store required.
Project order

What PWA development includes

We build on top of the site you already run: manifest, service worker and notifications, without rewriting the project. The code stays in your repository.

Web App Manifest and installation

Icons for every screen size, the name, colours, splash screen and the standalone mode without an address bar. This is the file that makes a browser offer to install the site.

ManifestIconsInstall

Service worker and offline mode

The shell and static assets are pre-cached, data comes from the network with the cache as a fallback. With no signal a visitor sees stored pages instead of a browser error.

Service workerOfflineCache

Push notifications

Web Push subscriptions, segments and scenarios: abandoned cart, order status, restocked item. The permission prompt appears after a user action, not on the first screen.

Web PushSegments

Speed on repeat visits

The second visit is served from cache, so the interface appears almost instantly even on a weak connection. It shows up in mobile Core Web Vitals.

CacheCore Web Vitals

PWA on an existing site

Works on WordPress, OpenCart or a custom build. There is no content migration and no CMS change — what changes is the file delivery layer, not the site.

WordPressOpenCartIntegration

Measuring installs

Install events, launches from the icon and push reactions are sent to GA4. You see not only how many people installed the app but how many actually use it.

GA4Events

Our clients’ results

We build long-term partnerships — and the numbers speak for themselves: our average client relationship lasts 5 years, and our partners' financial results grow quarter after quarter.

Reviews

We build long-term partnerships — and the numbers speak for themselves: our average client relationship lasts 5 years, and our partners' financial results grow quarter after quarter.

How we work

A PWA does not fix a website's problems, so we do not start one while the foundation performs badly.

A fast site first, the PWA second

Caching speeds up return visits, but the very first load stays as it was. If a page is slow to open, that is where we begin.

Versioned cache

The most common implementation mistake is a user seeing an old price because the service worker served a stored copy. Cache versioning is built in from the start.

No nagging to install

A banner over the content on the first screen hurts conversion and mobile metrics. We show the invitation to people who have already come back.

Request a consultation or audit

Tell us about your task and we will suggest a solution and show how it adds up in numbers. The consultation is free, with no obligations.
Error: Please make sure all the required fields are properly filled and try again

When a PWA beats a native app

A native app means two separate builds, two store listings and a review queue for every fix. A PWA stays part of the website: one codebase, one team, and the update ships the moment you deploy it. For a business that needs an icon on the screen, push notifications and speed, that is usually enough.

01

One codebase

Site and app are the same project. No separate iOS and Android developers, and no keeping three versions of the same feature in sync.

02

Updates without store review

A corrected price or wording reaches the user on the next open. No waiting for a store check and no persuading people to update the app.

03

The content stays searchable

PWA pages are ordinary URLs that get indexed and bring traffic. The contents of a native app do not exist in search results at all.

How we implement a PWA

We start not with the manifest but with the question of what a user has to be able to do offline. The caching strategy follows from that answer.

01

Site audit

We check HTTPS, speed, the mobile layout and which pages are worth caching at all. If the site is slow, that gets fixed first.

02

Offline scenario

We agree what stays available without a connection: catalogue, product page, contacts, saved documents. Everything else shows a clear fallback page instead of a browser error.

03

Manifest, service worker, cache

We write the files, set separate strategies for assets and for data, and version the cache so an update reaches the user rather than getting stuck in an old copy.

04

Testing and launch

We test installation on Android and iOS, offline behaviour and the switch to a new version. Then push notifications and analytics events go live.

Gift
Show promo code

Additional services

All competencies in-house — complex tasks solved quickly, without losing quality or time on communication between contractors.

Web sites

Landing Page

E-commerce

Advertising creatives

CRM implementation

Frequently asked questions about PWAs

What people ask before the work starts.

01

How does a PWA differ from a responsive site?

A responsive site simply looks right on a phone. A PWA adds an icon on the screen, offline operation and push notifications. If you already have responsive layout, this is not an alternative to it but the next layer on top.

02

Will a PWA replace our native app?

It depends on the features, and the honest answer is sometimes no. Catalogue, account area, orders, statuses and push notifications are all covered. Bluetooth hardware, background route tracking and in-app store billing are not — those need native development.

03

How does a PWA behave on iPhone?

It installs only manually through Safari: «Share» → «Add to Home Screen». Web push works after that step. The system may clear the cache if the app has been unused for a while, so the offline scenario is less reliable on iOS than on Android.

04

Can a PWA be published in Google Play or the App Store?

In Google Play, yes, through a Trusted Web Activity wrapper. The App Store is harder: Apple rejects apps that merely open a website, so a listing there usually calls for genuine native development.

05

What does it cost to maintain a PWA?

There is normally no separate budget for it — it is part of site support. One recurring task is added: after each release, confirm that the cache has rolled over and users are on the new version.

06

Does a PWA affect search rankings?

Not in itself, it is not a ranking factor. Speed and return-visit depth work indirectly. The real risk runs the other way: a badly configured cache can serve a crawler an outdated version of a page.

07

How long does development take?

It depends on the state of the site and the scope of the offline scenario. The basic set — manifest, static cache and an offline page — is markedly faster than an offline catalogue with data synchronisation. We give the timeline after the audit.

08

We are on WordPress. Will a plugin not do this?

A plugin gives you a manifest and a basic cache, which can be enough for a brochure site. For a store or an account area the caching strategies have to be written per page type, otherwise personal data lands in the cache and people see an old price.

PWA development: a site that behaves like an app

What a PWA actually is

A progressive web app is an ordinary website with three additions: an icon on the home screen, offline operation and push notifications. People open it from the phone screen like an app, yet nothing is downloaded from a store — it all runs in the browser.

Technically it is a handful of files on top of the site you already have. The Web App Manifest declares the name, icons, colours and the fact that the app opens without an address bar. The service worker is a script between the page and the network: it intercepts requests and serves stored copies when there is no signal. HTTPS is mandatory.

How a PWA differs from a website and from a native app

Compared on the points that change the decision and budget.

CriterionOrdinary websitePWANative app
Installationnoneicon added from the browservia App Store or Google Play
Without a connectionblank pagewhatever is cached worksworks
Push notificationsbrowser onlyyes, with limits on iOSyes
Updatesimmediateimmediate, once the cache version changesrelease plus store review
Device hardwareminimalcamera, location, filesfull
Codebaseoneoneseparate for iOS and Android
Search resultsindexedindexednot indexed

iOS limitations to know in advance

Android offers installation itself: the browser shows a prompt and the visitor only has to agree. On iPhone the site must be opened in Safari and added through «Add to Home Screen» — there is no system banner, and part of the audience does not know the gesture exists. Web push on iOS works only after that step, and the system may clear the cache if the app goes unused for a while.

When not to order a PWA

  • you need Bluetooth, NFC payments or background route tracking — a native app wins;
  • your audience looks for you in the App Store and treats a store listing as proof of seriousness;
  • the site is slow or awkward to use — a PWA does not cure that, it preserves the problem in the cache;
  • the traffic is one-off: people arrive from an ad, buy once and never return — nobody installs the icon.

A PWA or a new website

A corporate site, an online store and a landing page are types of website, each with its own structure and content. A PWA replaces none of them: it is a mode of operation added on top of a finished project. If there is no site yet, development comes first and the PWA becomes the next step of the same project.

Who we have worked with

Adcore has been working since 2014, with 24 people on staff and more than 600 completed projects. Clients include Hyundai, Heineken, Kärcher, CLAAS, Hilti, PepsiCo, Silpo and Materia Medica, plus residential developments and clinic networks.

Adcore digital agency © 2012-2026 LLC "АДКОР" Kyiv, Ukraine