display: standalone and PWA Look
display: standalone and the PWA look are directly linked: this one manifest field decides whether a user sees a browser address bar or an interface that looks like a native app. Here's how standalone differs from the other display modes, and what can quietly break that effect.
What a PWA manifest is and what display controls
The manifest is a JSON file that describes the PWA to the operating system: name, icons, colors, start URL, and the display field, which controls how the app looks once installed. Display has a few possible values — browser, minimal-ui, standalone, fullscreen — and each one hides or shows browser UI elements differently.
How standalone differs from browser mode
In browser mode, the app opens like an ordinary page — address bar, navigation buttons, the full familiar browser chrome. In standalone, those elements disappear and the app looks like its own window installed on the device, which is exactly what a user expects from a real app.
Why this matters for an arbitrage storefront
A visible browser address bar is a constant reminder that this is a website, not an app, and that quietly lowers trust and session depth. Standalone removes that reminder and matches the expectation users bring from ordinary app stores, which directly affects whether they reach registration and deposit instead of closing the tab early.
Other manifest fields that work alongside display
Display rarely works alone: start_url decides where the icon leads on a repeat open, name and short_name are what the user sees under the icon, theme_color and background_color set the system bar and splash screen colors, and orientation locks screen rotation. A mismatch between these fields — a dark design theme against a light background_color, for instance — is noticeable even when standalone itself is configured correctly.
How to verify a PWA actually opens in standalone
Add the PWA to the home screen and open it from that icon specifically, not through the browser — that's the only way to see the real display mode in action. Browser developer tools can check the manifest fields for validity. The most common reason standalone fails to kick in is an invalid manifest, missing HTTPS, or missing required fields, which makes the system fall back to plain browser mode.
FAQ
- Why is display: standalone better than fullscreen for an arbitrage storefront?
- Fullscreen hides every system element, including the status bar, which looks unfamiliar on some devices and can put users on guard. Standalone hides just the browser chrome while keeping system elements visible — closer to how most familiar apps actually look.
- Why does a PWA sometimes open in the browser instead of as an app?
- Usually it's an invalid or incomplete manifest, missing HTTPS, or opening a direct browser link instead of the installed icon. In those cases the system falls back to plain browser display as the safe default.
- Is HTTPS required for standalone mode?
- Yes, modern browsers require HTTPS for full PWA functionality, including proper standalone launch. Without a valid certificate, some PWA features, including the intended display mode, may not activate.
- Does APEX configure the manifest and display automatically, or does that need to be done by hand?
- APEX's builder generates the manifest with the right display mode and other fields automatically when the storefront is assembled, and custom domains come with free HTTPS included — so there's no manual manifest assembly or separate SSL setup needed.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free