Concept in Installation
The N+1 install problem
Published
The N+1 install problem occurs when several browsers install separate copies of the same web app. Installation belongs to the browser, not the operating system. Each browser creates its own app, storage, and record of installation, so a device can hold N browsers’ copies plus one from the next browser the user tries. Chromium browsers (Chrome 73, Edge 79), Safari on iOS 16.4 and macOS 14, and Firefox 143 on Windows each manage their installs this way (MDN “Installing and uninstalling web apps”, web.dev “Installation”).
How it works
Section titled “How it works”An installed web app runs inside the browser that created it. Chrome’s desktop app window is a Chrome process reading Chrome’s profile storage; Edge’s is an Edge process reading Edge’s; a Safari Home Screen web app on iOS uses its own data store separate from Safari tabs. MDN and web.dev document how this affects installation, storage, and removal.
- Edge knows a site is installed from Edge and offers “Open” when the site is visited again; Chrome, visiting the same site, offers “Install” because it has no record of the Edge app. Installing from Chrome as well yields two apps on the device.
- Cache Storage, IndexedDB, cookies, and
localStoragelive in the installing browser’s profile (or, on iOS, in the web app’s own container), so a user signed in to the Edge copy is signed out in the Chrome copy, and offline data cached by one is absent from the other. - Removing the Edge copy from
edge://appsleaves the Chrome copy inchrome://apps, and vice versa.
Within one browser the behaviour depends on the platform:
| Platform | Second install of the same site from the same browser | Identity key |
|---|---|---|
| Chrome and Edge, desktop (Windows, macOS, Linux, ChromeOS) | Refused; the install surface disappears and the browser offers to open the existing app | Manifest id, falling back to start_url |
| Chrome, Android (WebAPK) | Refused; one WebAPK per manifest id per browser |
Manifest id |
| Chrome, Android (shortcut fallback when the WebAPK server is unreachable) | Allowed; each shortcut points to the same browser storage | Shortcut only |
| Safari, iOS and iPadOS | Allowed, by design, with the user-chosen name distinguishing copies; each copy has isolated storage | Manifest id plus the name typed when adding |
| Safari, macOS 14+ | Allowed; a second “Add to Dock” creates a second web app | Name typed when adding |
The manifest id member is what lets a browser recognise a site it has already installed even after start_url changes; without it the identity is the start_url, and changing that URL turns an update into a new app on Chromium. On iOS the same id is deliberately not a deduplication key: WebKit documents multiple installs (work and personal accounts) as a feature and uses id together with the user’s name for the app to keep Focus and notification settings separate per copy.
A page cannot query the other browsers’ installs. getInstalledRelatedApps() reports an installed PWA only when the manifest lists it under related_applications and only from the same browser, and display-mode: standalone says only that this copy is running installed. You can reduce the cost of duplicate installs (stateless pages, account sign-in that restores data on any copy) or use explicit copy to steer users to one browser. The page cannot enforce that choice.
See also
Section titled “See also”- Installing and uninstalling web apps (developer.mozilla.org)
- Web Push for Web Apps on iOS and iPadOS (webkit.org)
- Web Application Manifest: id member (w3.org)
idmanifest member- getInstalledRelatedApps()
- Uninstalling an installed PWA
- iOS Add to Home Screen
Specifications
| Specification | Status |
|---|---|
| None. | |