Show the WordPress PWA Install Prompt After Visitors Decide They Like the Site

A visitor lands on your WordPress site. The page is still painting. A big “Install our app” banner covers the content. They dismiss it. Or worse, they bounce.

That is the default browser install moment: early, loud, and easy to ignore. A Progressive Web App only helps if people actually add it. Timing and style matter more than the tech under the hood.

This post is about the install invitation: when it shows, how it looks, what you brand, iOS/Android quirks, and install analytics. Not push, offline forms, background sync, or app-store builds. Those are separate jobs.

If you need the plain-English PWA baseline first, start with What is a Progressive Web App (PWA)? A plain-English guide for WordPress site owners in 2026. Here we zoom in on install prompt rules inside Progressify.

The problem: first-paint prompts feel like ads

Browsers can fire a native install event when a site meets PWA criteria. That event is useful. It is also blunt. It does not know if someone has read a paragraph, scrolled past the fold, or come back twice.

Ask on first paint and you train people to close you. Ask after they have decided the site is worth keeping, and installs climb without sounding spammy. Progressify puts it simply: ask at the right moment, not the first one, with five prompt styles on rules you set.

What Progressify actually gives you for install prompts

Stick to the features that ship. No invented toggles.

Prompt styles. Banner, popup, overlay, button, or QR code. Pick the shape that fits the page, not one generic strip for every site.

Triggers. Show on visit count, time on page, or scroll depth. That is how you wait until someone has engaged.

Dismiss memory. Dismissed once stays dismissed for as long as you set. You are not nagging every reload.

Branding. Your own icon, app name, splash screen, and theme colour. The home-screen tile should look like your brand, not a generic browser shortcut.

Platform handling. iOS and Android are handled per platform. The install path is not identical on every device, and Progressify accounts for that.

Install analytics. Installs broken down by device, browser, and country. You can see what actually converted.

That is the install-prompt surface. Push, offline forms, background sync, and store builds live elsewhere in the plugin. Leave them out of this setup pass.

Choose a style that matches the page

Treat the five styles as UX tools, not a checklist to enable all at once.

Banner. Low interruption. Good for blogs and long reads where you do not want a modal over the article.

Popup. Stronger call. Use when the visitor has already scrolled or spent time, so the ask feels earned.

Overlay. Highest attention. Pair it with a strict trigger (second visit, deep scroll). On first paint it feels like an interstitial ad.

Button. Always-available install control for people who want it on their terms. Useful in a header, footer, or account area.

QR code. Desktop-friendly path to a phone install. Someone reading on a laptop can scan and add the site on mobile without hunting menus.

Pick one primary ask, maybe a quiet button as a backup, and keep the page calm.

Trigger after intent, not after load

Visit count, time on page, and scroll depth are the three levers.

Visit count. Wait until the second or third visit if your content is habitual (news, membership, store). Returning visitors already know the site. First-timers need a fair look first.

Time on page. A short delay (enough to read a section) beats an instant modal. Start conservative. Tighten later with analytics.

Scroll depth. If someone has scrolled past the hero into real content, they are engaged. That is a cleaner install moment than the first 200ms of paint.

Combine carefully. “Second visit and 50% scroll” is usually smarter than “any visit, immediate popup.” The goal is a prompt that lands after the visitor has decided they like the place.

Dismissed means dismissed (for a while)

Nothing kills trust like a prompt that returns on every navigation. Progressify lets a dismiss stick for as long as you set. If someone said no today, give them breathing room. A week, two weeks, a month. Match the length to how often people return.

Forced re-asks read as growth hacking. Quiet patience converts better over a quarter.

Brand the install: icon, name, splash, theme colour

The prompt is only half the experience. What lands on the home screen is the other half.

Set a clear app name people will recognise in a grid of icons. Ship a proper icon set, not a stretched favicon. Choose a splash screen and theme colour that match your site chrome. A sloppy icon makes an installed PWA feel like a bookmark. A branded launch feels like your product.

iOS and Android are not the same path

Install UX differs by platform. Android (especially Chromium) often surfaces a cleaner native install flow when the site is installable. iOS has its own Add to Home Screen habits and UI quirks.

Progressify handles iOS and Android per platform so you are not maintaining two hand-rolled scripts. Still test on a real iPhone and a real Android phone before you call the setup done.

If you already covered offline reading and checkout honesty elsewhere, keep this pass focused on install. For the offline angle, see A WordPress PWA offline strategy that does not break checkout.

How to set install prompt rules in practice

You do not need a custom service worker for this. Progressify handles the PWA base (manifest, service worker, icons, platform install logic). You configure the invitation.

1. Get the PWA basics right first

Install Progressify. Fill in name, icons, colours, display. Confirm the site is installable. A beautiful prompt on a broken manifest still fails.

2. Pick one primary style

Banner or button for quieter sites. Popup or overlay only when your trigger already proves interest. Add QR if desktop-to-mobile install matters for your audience.

3. Set a delayed trigger

Start with something like: second visit, or 30+ seconds on page, or ~50% scroll. One strong condition beats three weak ones stacked into noise.

4. Configure dismiss duration

Pick a window long enough that “No thanks” means something. Then leave it alone. Do not shorten it every time installs look soft.

5. Brand icon, app name, splash, theme colour

Check the home-screen result on iOS and Android. Fix anything that looks cropped, generic, or off-brand.

6. Watch install analytics

Use device, browser, and country breakdowns to see where prompts convert. If Android installs and iOS stalls, fix the iOS path before you invent a new popup.

Pitfalls that waste good PWA work

First-paint overlays. They look aggressive and train dismissals. Delay the ask.

Re-prompting every session. If dismiss is set to minutes, lengthen it.

Generic branding. Treat the home-screen tile like a product asset, not a stretched favicon.

One style for every page. Match intensity to context. A checkout page does not need the same treatment as a blog post.

Ignoring platform differences. What looked fine on Android alone is how iOS users never install.

Mixing this brief with other PWA features. Push, offline forms, background sync, and store builds are real Progressify capabilities. They are not what this article configures. Keep the install pass focused so you can measure it.

Membership note (when you want the full stack)

Install prompts are one Progressify surface. Speed, SEO, AI content helpers, and backups sit in the other DaftPlug plugins. One Pro licence unlocks Progressify, Lightify, Generatify, Rankify, and Snapshotify. New Pro plugins join existing memberships. No new line item when the catalogue grows. See pricing if you want the site tiers.

Takeaway

A WordPress PWA install prompt should feel like an invitation after someone already likes the site, not a tax on first paint. Use Progressify’s banner, popup, overlay, button, or QR styles. Trigger on visit count, time on page, or scroll depth. Honour dismissals. Brand the icon, name, splash, and theme colour. Respect iOS and Android differences. Then read install analytics by device, browser, and country and adjust the ask, not the visitor’s patience.

Do that, and Add to Home Screen stops feeling like an ad and starts feeling like the natural next step.