related_applications

related_applications

An array of objects, each representing a platform-specific native application related to the web app. Each object must include a platform property and at least one of either a url or an id (or both).

platform

A string that identifies the platform on which the application can be found. Examples include amazon (Amazon App Store), play (Google Play Store), and windows (Windows Store). See the complete list of possible platform values.

url Optional

A string that represents the URL at which the platform-specific application can be found. If not specified, an id must be provided.

id Optional

A string with the ID used to represent the application on the specified platform. If not specified, a url must be provided.

A "related application" is a native application that provides functionality similar to your web app, often with additional features or better integration with users' devices.

The related_applications manifest member lets you identify the platform-specific native applications that are related to your web app. For example, consider you have a native Android app for your product available through the Google Play Store. It provides the same core features as your web app and integrates better with the device's notification system. You can use related_applications to specify this native Android app in your web app's manifest file.

Some key points about the related_applications member include:

• It allows you to specify multiple related apps on different platforms, giving users options for native apps across various devices and operating systems.

• It creates a unidirectional relationship between your web app and the specified native apps. The native apps are not required to reference your web app in return.

• The data may be used by web crawlers to gather more information about the native apps related to your web app, potentially improving discoverability of these native apps.

• When used with the prefer_related_applications member set to true, it enables browsers to suggest installing the related native app instead of your web app.

  Note: For Chromium-based browsers, prefer_related_applications should be set to false or omitted to make your web app installable.

This example shows how to specify a related native Android app in your web app's manifest file. It uses minimal information to identify the native app available on the Google Play Store:

{
  "related_applications": [
    {
      "platform": "play",
      "id": "com.example.app1"
    }
  ]
}

If native versions of your web app are available on both Google Play Store and Windows Store, you can specify them in your web app's manifest file like so:

{
  "related_applications": [
    {
      "platform": "play",
      "url": "https://play.google.com/store/apps/details?id=com.example.app1",
      "id": "com.example.app1"
    },
    {
      "platform": "windows",
      "url": "https://apps.microsoft.com/store/detail/example-app1/9WZDNCRFHVJL"
    }
  ]
}

If you want to indicate to browsers that you prefer users to be given the option to install your native app, available on the Google App Store, instead of your web app, you can set prefer_related_applications to true. Browsers may then prompt users to install the native Android app instead of your web app.

{
  "prefer_related_applications": true,
  "related_applications": [
    {
      "platform": "play",
      "id": "com.example.app1"
    }
  ]
}

• prefer_related_applications manifest member
• The web app manifest for making your web app installable
• Navigator.getInstalledRelatedApps()