Install To Home Screen: ReVend OS As A PWA
Why the warehouse tablet behaves better when the app installs to the home screen, what the manifest and icon configure, and the small win that adds up across a shift.
A receiving dock isn’t a desk. The operator’s left hand is on a scanner, the right on a touch screen, and there’s no time to fumble through tabs. Installing the platform to the warehouse tablet’s home screen makes it open like an app, not a Chrome bookmark — which sounds like a small win until you watch a shift.
What the manifest configures
The Web App Manifest (/manifest.webmanifest) declares the app’s display name, the start URL, the theme colour, the orientation preference, and the icon set. The browser uses these when the tablet user picks Install on the address-bar prompt: the icon lands on the home screen, tapping it opens the app full-screen, and the address bar that wastes fifty pixels at the top is gone.
The icons
The icon set covers the standard Android sizes (192×192 maskable, 512×512 standard) and the Apple touch-icon for iOS Safari. They’re the same brand mark that lives in the app’s header, just exported at the resolutions the OSes actually use. Without them, the home-screen icon falls back to a generic browser thumbnail and the install loses its credibility.
Why on warehouse tablets specifically
Three reasons. Screen real estate: warehouse tablets are usually small (8”, 10”), and the address bar swallows visible UI that the receiving grid actually needs. Persistence: a home-screen icon survives the tablet getting locked, restarted, or handed to the next shift; a tab in Chrome doesn’t. Mental model: operators think of it as “the platform,” not “the website,” and the home-screen launcher matches that mental model.
Install flow
Open the platform on the tablet’s browser, wait for the install prompt (or trigger it from the address-bar menu). Pick Install. The icon lands on the home screen. From now on, tapping the icon launches the app in standalone mode — no address bar, no tab strip, just the platform.
Not a native app
The PWA install runs the same web app the desktop browser runs. There’s no separate codebase, no app-store review queue, no install size to manage. Updates ship continuously through the normal deploy pipeline, and the tablet picks them up on next launch without an app-store roll.