# The N+1 install problem: one PWA, multiple independent installs

> How installing a PWA is tied to the browser used to install it, so the same PWA can end up installed as separate, data-isolated instances from different browsers on one device — and why the browser that installed it is the only one aware of the installed state.

**In one line:** Installing a PWA is tied to the browser used to install it, so installing the same PWA from a second browser creates a second, independent copy rather than reusing the first.

## Installs are scoped to the installing browser

A PWA installed by a browser remains specific to that browser — the browser used to install a PWA is the one used to run it. This means the same PWA can be installed from a different browser, and the two installed apps will behave as two different instances that do not share any data.

## No cross-browser awareness of install status

The browser used to install the PWA knows the PWA is installed, but other browsers do not have access to that installed status. For example, if a PWA is installed using Microsoft Edge, Edge will prompt to open the PWA when the site is visited again, while Chrome will continue to prompt to install the application, since Chrome has no knowledge of the Edge install. Installing the PWA using Chrome as well then results in two separate copies of the PWA on the same device.

## Isolated storage per install

When multiple instances of a PWA are open, data is not shared between instances installed from different browsers — each browser's installed copy keeps its own separate storage.

## Uninstalling is also browser-specific

Similarly, the method used to uninstall a PWA depends on which browser was used to install it (for example, via `edge://apps` or `chrome://apps`), so removing one browser's copy does not remove another browser's copy of the same PWA.

## Platform-specific reinstall behavior differs

Whether a repeat install duplicates an app or reuses the existing one also depends on the platform, not only on switching browsers:

- On iOS/iPadOS, the same PWA can be installed multiple times; each installation has its own isolated storage and is treated as a different app.
- On desktop, a PWA cannot be installed twice with the same browser.
- On Android, a shortcut-based install can be created many times, even from the same browser; when that happens, all of them point to the same installed instance and use the same storage. A WebAPK-based install, in contrast, cannot be installed twice.

## Practical checklist

- [ ] Do not assume installing a PWA in one browser prevents (or is visible to) an install prompt in another browser on the same device.
- [ ] Do not assume data is shared between copies of the same PWA installed from different browsers — each keeps isolated storage.
- [ ] Point users to the browser-specific uninstall surface (for example `edge://apps`, `chrome://apps`) that matches the browser they installed from.