Install BrandOps as an app

BrandOps is a Progressive Web App, not a native App Store or Play Store download. You install it straight from your browser.

• On Android and desktop Chrome or Edge, the browser fires a native install prompt once it decides BrandOps qualifies; accepting adds an icon to your home screen or app launcher that opens in its own standalone window, no browser chrome.
• On iOS Safari, there's no install-prompt API for third-party sites to use, so you install manually via the Share button's "Add to Home Screen."
• Once installed, BrandOps detects it's running standalone (rather than in a regular browser tab) and can adjust its own UI accordingly.
• BrandOps declares shortcuts to Dashboard, Tasks, Orders, and Content in its app manifest, so on platforms that support it, you can jump straight to one of those from the installed icon without opening the dashboard first.

A service worker caches enough for BrandOps to open gracefully without a connection, though live data still needs one.

• The /offline page and core app icons are precached on install, so BrandOps always has somewhere sensible to fall back to.
• Static assets (icons, images, fonts, and Next.js's build chunks) are cached with a cache-first strategy: once fetched, they load instantly from cache on repeat visits.
• Page navigations use a stale-while-revalidate strategy: if a cached copy of that page exists, BrandOps shows it immediately while quietly fetching the latest version in the background; if nothing is cached yet, it waits on the network and falls back to the offline page only if that fails too.
• API requests are always network-only and never cached: your tasks, orders, and client data are never served stale from a local cache, only ever live from the server.
• The offline page itself explicitly tells you your data is safe: everything you've entered is stored on BrandOps's servers, not lost because your connection dropped.

Push alerts run through the same service worker that powers offline support, but installing the app and subscribing to push are two separate steps.

• You can enable push notifications from a regular browser tab; installing BrandOps to your home screen isn't required to get them.
• Push alerts require Growth plan or above; enabling them on a lower plan reverts the browser-level subscription so your device doesn't end up half-subscribed. See the Notifications guide for the full opt-in flow.
• A push notification tapped from your device opens (or focuses an existing tab to) the relevant page in BrandOps: the service worker matches the notification's target URL against any already-open window before opening a new one.

BrandOps's service worker is versioned, so installed users don't get stuck on an outdated cached build.

• When a new deployment ships, the app detects the update and can apply it, which activates the new service worker and reloads the page onto the latest version.
• Old caches from previous versions are cleaned up automatically once a new version takes over, so installed storage doesn't grow unbounded across deploys.
• This update-detection logic only runs in production, so a leftover development-mode service worker won't trigger reload loops while you're just browsing locally.