Someone taps your home-screen icon. For a second the phone shows a blank white rectangle, the browser default name, and a stretched favicon. Then your WordPress theme finally paints. That first second taught them this is still a website trapped in a shortcut, not an app that belongs next to Instagram.
Native apps open with a branded splash, a system status bar colour that matches the product, and a display mode that hides browser chrome. Progressify ships that install presentation for WordPress: your own icon, app name, splash screen, and theme colour, plus display and startup behavior so the installed PWA can launch fullscreen or standalone the way Progressify exposes it. You set it in the PWA stack. You do not rebuild the theme for a launch screen.
Progressify is the DaftPlug PWA plugin. This post is only about manifest-driven install presentation: icon, app name, splash screen, theme colour, and display / startup behavior. Not the bottom tab bar, not dark mode, not smooth page transitions, not idle detection, not push notifications, not offline caching, not install prompt timing or styles, not Android or iOS store builds, not pull to refresh, not wake lock, not haptics, not skeletons, not toasts, not background sync, not autosave forms. Those live elsewhere. For adjacent app-like navigation polish after launch, keep WordPress PWA smooth page transitions nearby.
What Progressify actually ships here
Stay inside the real feature set:
- Your own icon, app name, splash screen, and theme colour as part of the Progressify install / manifest story
- Display Settings for display and startup behavior (fullscreen launch and the standalone-style experience Progressify exposes)
- Platform-aware install presentation so iOS and Android get a coherent home-screen tile and launch look
- Theme-agnostic layering: Progressify sits over the themes and plugins you already run
- A settings-level branding pass you complete in Progressify rather than inventing a custom splash in
header.php
This post does not invent undocumented splash durations, custom Lottie launch animations, per-route theme colours, or claims that every OS paints splash assets the same way. The product promise is branded install presentation (icon, name, splash, theme colour) plus display and startup behavior so the installed PWA launches looking like an app. Your theme still owns layout after launch. Progressify owns the install shell.
Why splash, theme colour, and display mode matter
The first paint is a brand test. People judge installed apps in under a second. A white flash and a generic label fail that test before your hero section ever loads. A splash that matches the icon and a theme colour that matches the chrome tell the OS (and the person) this tile is intentional.
Standalone removes the browser’s soft cover. In a normal tab, Safari or Chrome chrome frames your site. After install, that chrome is gone. Theme colour becomes the status-bar story. Display mode decides whether the experience feels like a browser wrapper or an app window. Wrong settings look unfinished even when the site is fast.
Icons and names outlive marketing campaigns. The home-screen tile sits for months. A stretched favicon and a legal entity name nobody uses in conversation make the PWA feel like a bookmark. Progressify’s “your own icon, app name” promise exists so the tile matches how you talk about the product.
Display mode completes the app-like claim. Fullscreen or standalone-style launch (as Progressify exposes it) is what separates “Add to Home Screen as a shortcut” from “this opens like our product.” Pair branding with display settings. Do not ship a perfect icon into a browser-chrome shell and call it done.
How to set splash, theme colour, and display mode in wp-admin
Assume Progressify is installed, HTTPS works, and the PWA can already install (manifest, service worker, basic icons).
1. Confirm you are branding for install, not for a browser tab demo
Splash and theme colour matter most after Add to Home Screen, when the OS shows launch assets and paints the status bar. Smoke-test on a real phone. Desktop DevTools helps, but the home-screen grid and the cold open are the truth.
2. Open Progressify branding and Display Settings
In wp-admin, open Progressify. Set app name to the short label people should recognise in a crowded icon grid (not your full legal company string unless that is the brand). Upload a proper icon set, not a stretched favicon. Set splash screen and theme colour so launch matches site chrome. Then open Display Settings and choose the display / startup behavior you want (fullscreen or standalone-style experience as Progressify exposes it).
Do not turn on tab bar, dark mode, transitions, idle detection, push, and branding in the same panicked pass. Ship icon, name, splash, theme colour, and display mode first. Add chrome after the cold open already looks intentional.
3. Pick theme colour on purpose
Theme colour should match the dominant chrome people see after launch (header bar, primary brand colour), not a random accent from a seasonal campaign. On light UIs, a light theme colour can wash out status icons. On dark UIs, match the dark shell. Document the hex so the next designer does not “refresh the brand” in the PWA settings without updating the live header.
4. Treat splash as brand continuity
Splash should feel like the icon grew into a launch frame: same mark, same colour family, no tiny logo lost in a white void. Avoid shipping a full marketing poster as splash if the OS crops it into a confusing crop. Prefer a clear mark and colour field that still reads on a small phone.
5. Verify display mode on a device you hold
- Install the PWA and force-close it.
- Cold-open from the home-screen icon.
- Confirm splash (or platform launch presentation) matches brand, not a blank white tile.
- Confirm theme colour paints the system chrome in a way that matches the first screen.
- Confirm display / startup behavior hides the browser UI the way you intended (fullscreen / standalone experience as configured).
- Open a deep link into an article or product and confirm the installed shell still feels like an app, not a tab.
- Compare iOS and Android once. Progressify handles platform-specific install quirks. Your job is to notice if one platform still shows a weak icon or a name that truncates badly.
If a page builder also injects a full-screen loader that fights the OS splash, reconcile it. Two launch stories look broken.
6. Keep sensitive flows honest
Login, checkout, and account screens should be in your first cold-open test set. Branding is presentation, not a security layer. Pair display mode with WordPress auth, HTTPS, and your existing session policies. Do not treat a pretty splash as a substitute for proper redirects after login.
What good looks like
- Installed PWA shows your Progressify icon and app name on the home screen, not a generic browser shortcut.
- Cold open presents splash and theme colour that match brand chrome.
- Display Settings launch the app in the fullscreen / standalone experience you chose in Progressify.
- Tab bar, dark mode, transitions, idle detection, push, offline, install prompt styles, store builds, pull to refresh, wake lock, haptics, skeletons, toasts, background sync, and autosave forms were not required for this win.
- You did not invent undocumented splash APIs or claim every OS paints identical launch frames.
- A teammate can install the app, cold-open it, and describe the brand in one sentence. Deep links still open inside the installed shell with the same theme colour story.
If DevTools looks perfect but a real device still shows a white launch because icons never regenerated after an upload, re-save icons, clear the old home-screen shortcut, and reinstall. Stale install tiles are common.
Pitfalls (the ones that bite)
Shipping a favicon as the only icon. Home-screen density needs real PWA icons. A 32px favicon upscaled looks cheap.
Using the legal entity name as the app name. “Acme Holdings LLC Portal” truncates into nonsense. Use the product name people say out loud.
Treating splash as a Core Web Vitals fix. Splash is brand continuity at launch. It does not replace caching, image work, or deferred scripts. Measure performance separately.
Leaving display mode in a browser-like setting after marketing “we are an app.” Brand the tile, then actually launch without chrome.
Bundling every app-like UI toggle. Turning on tab bar, dark mode, transitions, and splash together makes failures hard to attribute. Enable branding and display first, verify, then add the next piece.
Promising custom cinematic launch videos in marketing copy. Stay at product level: icon, name, splash, theme colour, display and startup behavior.
Forgetting to reinstall after icon changes. Many devices cache the home-screen asset. Remove the old icon and add again after branding updates.
Practical checklist before you call it done
- Confirm the PWA installs on a real phone over HTTPS.
- Set Progressify app name, icons, splash screen, and theme colour.
- Open Display Settings and choose display / startup behavior (fullscreen or standalone experience as Progressify exposes it).
- Remove any old home-screen shortcut and reinstall so icons refresh.
- Cold-open and confirm splash and theme colour match brand.
- Confirm browser chrome is gone (or intentionally present) per your display choice.
- Spot-check a deep article or product URL opened from the installed app.
- Compare iOS and Android icon crops and name truncation.
- Leave tab bar, dark mode, transitions, idle detection, push, offline, install prompts, store builds, pull to refresh, wake lock, haptics, skeletons, toasts, background sync, and autosave forms for separate passes if they are not already stable.
- Re-test after the next brand refresh. Icon and colour drift silently.
Takeaway
A WordPress PWA that installs cleanly still fails the app test if the cold open looks like a blank browser tab. People expect a branded splash, a theme colour that matches the product, and a display mode that hides chrome. Native apps deliver that. Your installed site can too. The fix is not a custom loader in the theme. It is Progressify install presentation: your own icon, app name, splash screen, and theme colour, plus Display Settings for startup behavior.
Progressify handles manifest-driven branding and display alongside the rest of the PWA stack, without asking you to rebuild launch screens per platform. Set the brand once. Test on a phone you actually hold. Keep other UI features as separate enablement work.
One Pro membership unlocks Progressify plus Lightify, Generatify, Rankify, and Snapshotify. New Pro plugins join existing memberships. Plans differ by site count only (Pro $37.99 for 1 site, Pro Plus $74.99 for 5, Pro Max $138.99 for 100), with a 14-day money-back guarantee. See pricing when the installed app should open looking like your product instead of a white rectangle with a stretched favicon.
Set splash, theme colour, and display mode. Install once. When the cold open matches the home-screen tile, the PWA finally feels like it belongs next to the rest of the apps on the phone.