Once the user installs your PWA: - The user can find an app icon in the launcher, home screen, start menu, or launchpad. - The app appears as a result when a user searches for the app on their device. - The app has a separate window within the operating system. - The app supports for specific capabilities. > [!NOTE] > **Note:** While installation differs per browser and operating system, you don't need to customize a package or executable for your PWA to be installed. ## Installation criteria Every browser has a criterion that marks when a website or web app is a Progressive Web App and can be installed for a standalone experience. The metadata for your PWA is set by a JSON-based file known as the Web App Manifest, which we share in the [next module](https://web.dev/learn/pwa/web-app-manifest). As a minimum requirement for installability, most browsers that support it use the Web App Manifest file and certain properties such as the name of the app, and configuration of the installed experience. An exception to this is Safari for macOS, which does not support installability. The requirements to allow installation differ among the different browsers, here we detail the criteria for Google Chrome and includes links to requirements for other browsers. Users can install your web app even if it doesn't meet the installability criteria in Chrome. Check out [How Chrome helps users install the apps they value](https://developer.chrome.com/blog/how_chrome_helps_users_install_the_apps_they_value#manual_installation_of_any_app) to learn more. Because the test that a PWA meets installability requirements can take several seconds, installability itself may not be available as soon as a URL's response is received. > [!NOTE] > **Note:** The process for uninstalling a PWA is different on each combination of operating system and browser. In most situations, the app can be uninstalled the same as any other platform-specific app; in other situations, the PWA window offers a menu with an uninstall option. Deleting the icon may not clear the storage that a PWA is using. ### Desktop installation Desktop PWA installation is supported by Google Chrome and Microsoft Edge on Linux, Windows, macOS, and Chromebooks. These browsers show an install badge (icon) in the address bar, stating that the current site is installable. ![Chrome on desktop with the install badge in the URL bar.](https://web.dev/static/learn/pwa/installation/image/chrome-step1.jpg) In Chrome, after clicking the install badge. ![Once the user clicks next, the user is presented with the opportunty to install the PWA.](https://web.dev/static/learn/pwa/installation/image/chrome-step2.jpg) Step 2, once the user clicked next. When a user is engaged with a site, they may see a module inviting them to install the site as an app. ![Google chrome in-product help suggesting the PWA installation.](https://web.dev/static/learn/pwa/installation/image/google-chrome-product-he-9238ca86bdc87.png) The browser's drop-down menu may also include an "Install " item that the user can use. > [!NOTE] > **Note:** Chromium-based browsers on desktop let you see all installed PWAs with that browser using `about:apps`. Only standalone and minimal-ui [display modes](https://web.dev/learn/pwa/app-design#display_modes) are supported on desktop operating systems. PWAs installed on desktops: - Have an icon in the Start menu or Start screen on Windows PCs, in the dock or desktop in Linux GUIs, in the macOS launchpad, or a Chromebook's app launcher. - Have an icon in app switchers and docks when the app is active, was recently used, or is opened in the background. - Appear in the app search, for example, search on Windows or Spotlight on macOS. - Can set a badge number on their icons, to indicate new notifications. This is done with the [Badging API](https://developer.mozilla.org/docs/Web/API/Badging_API). - Can set a contextual menu for the icon with [App Shortcuts](https://developer.mozilla.org/docs/Web/Manifest/shortcuts). - Can't be installed twice with the same browser. > [!NOTE] > **Note:** Installation may unlock [additional capabilities](https://web.dev/learn/pwa/capabilities) that are unavailable to PWAs running in a browser tab. not available for PWAs running within the browser's tab. After installing an app on the desktop, users can navigate to `about:apps`, right-click on a PWA, and select "Start App when you Sign In" if they want your app to open automatically on startup. ### iOS and iPadOS installation A browser prompt to install your PWA doesn't exist On iOS and iPadOS. On these platforms PWAs are also known as *home screen web apps* . These apps have to be added manually to the home screen using a browser share menu. We recommend that you add the [`apple-touch-icon`](https://developer.chrome.com/docs/lighthouse/pwa/apple-touch-icon) tag to your html. To define the icon, include the path to your icon to the page ``: The browser uses that information to create the shortcut, and if you don't provide a specific icon for Apple devices, the icon on the home screen will be a screenshot of your PWA when the user installed it. The steps to add apps to the home screen are: 1. Open the Share menu, available at the bottom or top of the browser. 2. Click **Add to Home Screen**. 3. Confirm the name of the app; the name is user-editable. 4. Click **Add**. On iOS and iPadOS, bookmarks to websites and PWAs look the same on the home screen. On iOS and iPadOS, only the standalone [display mode](https://web.dev/learn/pwa/app-design) is supported. Therefore, if you use minimal UI mode, it will fall back to a browser shortcut; if you use fullscreen, it will fall back to standalone. > [!CAUTION] > **Caution:** On Apple devices, you can install the same PWA multiple times. Each installation has its own isolated storage and is treated as a different application. PWAs installed on iOS and iPadOS: - Appear in the home screen, Spotlight's search, Siri Suggestions, and App Library search. - Don't appear in App Gallery's categories folders. - Lack support for capabilities such as badging and app shortcuts. Incidentally, Apple's [Web Clips](https://developer.apple.com/documentation/devicemanagement/webclip) is used to create the PWA icons in the operating system. They are just XML files in Apple's Property List format stored in the file system. > [!TIP] > **Tip:** When users use the PWA, they are not using an instance of the browser app, they are using something known as *Web.app*, so you should expect slight differences between your PWA rendered in a browser and a PWA window. Both browser and Web.app use the same core from WebKit and the same JavaScript runtime, but they run in different processes and may have different implementations, such as having isolated storage. ### Android installation On Android, PWA install prompts differ by device and browser. Users may see: - Variations in the wording of the menu item for install such as **Install** or **Add to Home Screen**. - Detailed installation dialogs. In the following image you can see two different versions of an installation dialog, a mini-infobar (left) and a detailed installation dialog (right). ![Mini info bar and installation dialogs on Android.](https://web.dev/static/learn/pwa/installation/image/mini-info-bar-installati-ccdb28e301b54.png) Depending on the device and browser, your PWA will either be installed as a WebAPK, a shortcut, or a QuickApp. #### WebAPKs A WebAPK is an Android package (APK) created by a trusted provider of the user's device, typically in the cloud, on a WebAPK *minting server*. This method is used by Google Chrome on devices with Google Mobile Services (GMS) installed, and by Samsung Internet browser, but only on Samsung-manufactured devices. Together, this accounts for the majority of Android users. When a user installs a PWA from Google Chrome and a WebAPK is used, the minting server "mints" (packages) and signs an APK for the PWA. That process takes time, but when the APK is ready, the browser installs that app silently on the user's device. Because trusted providers (Play Services or Samsung) signed the APK, the phone installs it without disabling security, as with any app coming from the store. There is no need for sideloading the app. PWAs installed using WebAPK: - Have an icon in the app launcher and home screen. - Appear on Settings, Apps. - Can have several capabilities, such as [badging](https://web.dev/badging-api), [app shortcuts](https://web.dev/articles/app-shortcuts), and [capture links within the OS](https://web.dev/articles/declarative-link-capturing). - Can [update](https://web.dev/articles/manifest-update) the icon and app's metadata. - Can't be installed twice. > [!TIP] > **Tip:** You don't need to build or sign any package when a WebAPK is used. It's all handled transparently between the browser, device, and minting server. #### Shortcuts While WebAPKs provide the best experience for Android users, they can't always be created. When they can't, browsers fall back to creating a website shortcut. Because Firefox, Microsoft Edge, Opera, Brave, and Samsung Internet (on non-Samsung devices) don't have minting servers they trust, they'll create shortcuts. Google Chrome will too if the minting service is unavailable or your PWA doesn't meet installation requirements. PWAs installed with shortcuts: - Have a browser-badged icon on the home screen (see the following examples). - Don't have an icon in the Launcher or on **Settings, Apps**. - Can't use any capabilities that require installation. - Can't update their icons and app metadata. - Can be installed many times, even using the same browser; when this happens, all will point to the same instance, and use the same storage. ![A PWA installed with different browsers on the same device.](https://web.dev/static/learn/pwa/installation/image/a-pwa-installed-differen-3ddf75a64e5da.png) #### QuickApps Some manufacturers, including Huawei and ZTE, offer a platform known as [QuickApps](https://developer.huawei.com/consumer/en/huawei-quickApp/) to create light web apps similar to PWAs but using a different technology stack. Some browsers on these devices, like the Huawei browser, can install PWAs that get packaged as QuickApp, even if you are not using the QuickApp stack. When your PWA is installed as a QuickApp, users will get a similar experience to the one they would have with shortcuts, but with an icon badged with the QuickApps icon (a lightning image). The app will also be available to launch from the QuickApp Center. ![QuickApps on a Huawei or ZTE home screen.](https://web.dev/static/learn/pwa/installation/image/quickapps-a-huawei-zte-23e50dd9b923c.png) ## Prompting for installation In Chromium-based browsers on desktop and Android devices, it's possible to trigger the browser's installation dialog from your PWA. The [Installation Prompt chapter](https://web.dev/learn/pwa/installation-prompt), covers patterns and how to implement them. > [!CAUTION] > **Caution:** If you write instructions for the user, remember to localize the instructions, as menu items' names may vary by language. ## App catalogs and stores Your PWA can also be listed in app catalogs and stores to increase its reach and let users find it in the same place they find other apps. Most app catalogs and stores support technologies that let you publish a package that doesn't include the whole web app (such as your HTML and assets). These technologies let you create just a launcher to a standalone web rendering engine that will load the app and let the service worker cache the necessary assets. The app catalogs and stores that support publishing a PWA are: - [Google Play Store for Android and ChromeOS](https://chromeos.dev/en/publish/pwa-in-play), using a [Trusted Web Activity](https://developer.chrome.com/docs/android/trusted-web-activity). - Apple App Store for iOS, macOS, and iPadOS, using WKWebView and [App-Bound Domains](https://webkit.org/blog/10882/app-bound-domains/). - [Microsoft Store for Windows 10 and 11](https://docs.microsoft.com/windows/uwp/publish/pwa/overview), using APPX packages. - [Samsung Galaxy Store](https://samsunginternet.github.io/introducing-progressive-web-apps-to-samsung-galaxy-store/), using the Samsung WebAPK minting server. - Huawei AppGallery, using a [QuickApp container for your HTML application](https://developer.huawei.com/consumer/en/doc/development/quickApp-Guides/quickapp-h5-to-quickapp-introduction-0000001150075595). If you want to learn more about how to publish a PWA to app catalogs and stores, check out [BubbleWrap CLI](https://github.com/GoogleChromeLabs/bubblewrap) and [PWA Builder](https://pwabuilder.com). > [!CAUTION] > **Caution:** Some app catalogs and stores have technical or business requirements that before your PWA is accepted for publication. Check each store's requirements before starting. ## Resources - [What does it take to be installable](https://web.dev/articles/install-criteria) - [WebAPKs on Android](https://web.dev/articles/webapks) - [Patterns for promoting PWA installation](https://web.dev/articles/promote-install) - [Using a PWA in your Android app](https://web.dev/articles/using-a-pwa-in-your-android-app) - [List your Progressive Web App in Google Play](https://chromeos.dev/en/publish/pwa-in-play) - [Submit your PWA to the Microsoft Store](https://docs.microsoft.com/en-us/windows/uwp/publish/pwa/overview) - [Publishing a PWA to App Store](https://firt.dev/pwa-stores/) - [WebKit: App-Bound Domains](https://webkit.org/blog/10882/app-bound-domains/) - [How Chrome helps users install the apps they value](https://developer.chrome.com/blog/how_chrome_helps_users_install_the_apps_they_value#manual_installation_of_any_app)