Skip to content
Bdazzil Marketing

Blog Web Design

How to Add Progressive Web Apps (PWAs) to WordPress

A WordPress progressive web app lets visitors add your site to their phone’s home screen, open it in its own window without browser bars, load key pages on a weak

9 minute read

A WordPress progressive web app lets visitors add your site to their phone’s home screen, open it in its own window without browser bars, load key pages on a weak connection and, where it makes sense, receive push notifications. For a UAE business that sells to repeat customers, members or clients who check in often, that can turn a website into something that behaves much more like an app, without the cost and approval cycle of the App Store and Google Play.

The technology is mature, but the implementation details decide whether it helps or quietly breaks things. Caching the wrong page can show a customer someone else’s cart, and a careless offline setup can serve stale prices for days. This guide explains how we approach PWAs as part of web design projects, and what to check before switching one on for a site built on WordPress.

What a PWA actually adds to WordPress

A progressive web app is not a separate product. It is your existing website with three additions that browsers recognize:

  • HTTPS: required for everything else. Any site still serving mixed content needs that fixed first.
  • A web app manifest: a small JSON file that tells the browser the app’s name, short name, icons, theme color, background color, start URL and display mode (usually “standalone”, which hides the browser interface).
  • A service worker: a script that sits between the page and the network. It decides what to cache, what to fetch fresh, what to show when the connection drops and how to handle push messages.

Once these are in place, Chromium browsers on Android and desktop can offer an install prompt, and Safari users on iPhone can add the site from the Share menu. The site still ranks, links and shares like any other page, which is the main commercial advantage over a native app.

When a PWA is worth it, and when it is not

A PWA earns its place when people return often and speed matters to them. Good candidates include:

  • Membership, course and community sites where users log in several times a week.
  • Restaurants, clinics and salons with regular bookings and a menu or service list people revisit.
  • Stores with loyal repeat buyers who reorder familiar products.
  • Field teams, brokers or agents who open the same internal tools on the move, sometimes with patchy signal on site visits.

It adds little to a corporate brochure site visited once or twice during a buying decision. In that case, the same effort is better spent on speed, content and clear routes to an inquiry. A PWA also does not replace a native app where you need deep device access, heavy offline data or a presence in app store search.

Choosing how to add it

There are two broad routes, and the right one depends on how custom the site already is.

ApproachSuitsWatch for
Dedicated PWA pluginStandard content sites and simpler stores that need a manifest, icons, an offline page and basic cachingMaintenance status, default caching rules, conflicts with page caching and security plugins
Custom manifest and service worker (often built with Google’s Workbox library)WooCommerce, membership and LMS sites, or any site with logged-in areas and dynamic pricingNeeds a developer who owns the caching logic and tests it after every major update

Before installing any plugin, check when it was last updated, whether it supports your WordPress and PHP versions, and exactly what it caches by default. Several plugins aim to do everything, including push, analytics and install banners. We prefer fewer moving parts: a clean manifest, a carefully scoped service worker and push handled by a dedicated service only if there is a real use for it.

Building a WordPress progressive web app step by step

1. Fix the foundations first

Run the site through Lighthouse and Chrome DevTools. Confirm HTTPS everywhere, no mixed content, a responsive layout and acceptable Core Web Vitals. A PWA amplifies what is already there. A slow site installed on the home screen is still a slow site.

2. Write the manifest properly

Give the app a short name that fits under a home screen icon, which matters for longer brand names and Arabic names alike. Provide icons at 192 and 512 pixels, plus a maskable icon so Android can shape it without cropping the logo. Set the start URL to the page people actually want on opening, such as a dashboard, a booking page or the shop home. For bilingual sites, decide whether the installed app opens in the visitor’s last used language or a default, and set the “lang” and “dir” members accordingly so an Arabic version opens right to left.

3. Define caching rules by page type

This is where most problems start. A sensible default for WordPress looks like this:

  • Static assets (theme CSS, JavaScript, fonts, logos): cache first, with versioned file names so updates replace old copies.
  • Images: cache first with an expiry limit and a cap on the number of entries, so the cache does not grow indefinitely on the user’s phone.
  • Public pages and posts: network first, falling back to the cached copy when offline, or stale while revalidate for content that changes rarely.
  • Never cache: wp-admin, login and account pages, cart, checkout, REST API calls that return personal data, and any response containing a nonce.

4. Design a useful offline page

Replace the browser’s error screen with a branded page that explains the connection has dropped, lists what is still available and offers a phone number or WhatsApp link that works once the signal returns. For a restaurant, cached menus are useful offline. For a store, recently viewed products are. Prices and stock should be marked as last updated, or excluded.

5. Handle updates cleanly

Service workers persist on the device. When you change the site, users can keep seeing the old version until the new service worker takes control. Version the cache, clear old caches on activation and consider a small “new version available, refresh” notice for logged-in users. Plan a kill switch too: a no-op service worker you can deploy quickly if something goes wrong.

WooCommerce, memberships and logged-in users

Dynamic WordPress sites need extra care because the same URL returns different content for different people. Cart fragments, mini carts, account menus and personalized recommendations must always come from the network. Checkout should never load from a service worker cache, and payment gateway redirects should be excluded from its scope entirely. Many UAE gateways redirect to a hosted payment page and back, so test the full round trip with each gateway you use.

Membership and LMS platforms raise a second issue: protected content. If lessons or member resources are cached for offline reading, they remain on the device after the membership expires. That may be acceptable for a PDF guide and unacceptable for paid video. Decide deliberately, and keep premium media streaming only.

Install prompts, iPhone behavior and push notifications

Install behavior differs by platform, and users in the UAE split across both. Chromium browsers fire an install event you can use to show your own “Add to home screen” button at a sensible moment, such as after a second visit or a completed booking, rather than on arrival. Safari on iPhone does not show an automatic prompt, so a short instruction card pointing to Share and then Add to Home Screen helps.

Web push works on Android and desktop browsers, and on iPhone from iOS 16.4 onward, but only for sites the user has added to the home screen and only after they grant permission. Ask for permission after a clear action, for example “Notify me when my appointment is confirmed”, never on page load. Push messages should be transactional or genuinely useful: booking reminders, order updates, class changes. Promotional blasts erode trust quickly and lead to the permission being revoked.

Privacy, testing and measurement

Push subscriptions and any analytics you collect about installed users are personal data under the UAE PDPL (Federal Decree-Law No. 45 of 2021). Explain in your privacy notice what you store, why and how users can switch notifications off. Keep consent records if you rely on consent.

Testing should cover more than one phone. Check installation on a recent Android device and an iPhone, test offline behavior with the network switched off, log in and out to confirm no personal data is served from cache, and complete a full purchase or booking. In analytics, track the display mode so you can compare installed users with browser users, and watch return visits, session depth and conversion rather than install counts alone.

Frequently asked questions

Does a PWA affect SEO on a WordPress site?

Not directly. Google indexes the same pages it did before, and the manifest and service worker do not change rankings. Indirect effects come from speed: a well-configured service worker can make repeat visits faster. The risk is a misconfigured one serving outdated content or blocking fresh pages, so test carefully and keep public pages network first.

Can a PWA replace our native mobile app?

For many service businesses, yes, particularly where the app mainly shows content, bookings and account details. It cannot match a native app for deep hardware access, complex offline data or app store discovery. A useful approach is to launch the PWA first, measure how often people return, and only commission a native app if the evidence supports it.

Will a PWA work for Arabic and English versions?

Yes. The manifest supports language and text direction, and the service worker can cache both language versions. Decide which language the installed app opens in, test right to left layouts in standalone mode, and make sure the offline page exists in both languages so Arabic users are not dropped into English when the connection fails.

How much maintenance does a PWA need?

Less than a native app, but more than none. Review caching rules after theme, plugin or checkout changes, update icons after a rebrand, and test on new iOS and Android releases. Keep a documented way to disable the service worker quickly. Most issues we see come from caching rules nobody revisited after the site changed.

An app experience without the app store

Done carefully, a WordPress progressive web app gives your most loyal customers a faster, app-like way back to you, while keeping everything that makes the website valuable in search. The work is mostly in deciding what to cache, what to leave alone and when to ask for attention. If you are weighing a PWA against a native app, or want your current WordPress site assessed for it, the Bdazzil team is happy to talk it through.

Keep reading

Free Growth Audit

Tell us about your project

A few details and we'll reply within one business hour, with a 30-minute call and a written plan to follow.

Sunday to Thursday, 9am to 6pm UAE time. Replies within one business hour.