We are discontinuing the Google Sign-In JavaScript Platform Library for web. The library will be unavailable for download after the March 31, 2023 deprecation date. Instead, use the new Google Identity Services for Web.
By default, newly created Client IDs are now blocked from using the older Platform Library, existing Client IDs are unaffected. New Client IDs created before July 29th, 2022 can set `plugin_name` to enable use of the Google Platform Library.

Android app installs from your web site

By adding the Google Sign-In button to your web site, you can automatically prompt your users to download your Android app over the air to their Android devices. To enable this feature, you must use the same Google API Console project for your Web and Android clients, and configure your web app's sign-in button.

App requirements

For your app to be eligible for this feature, it must be published in the Google Play store, be free, and it must meet a quality threshold. This threshold is determined by Google and is subject to change. New apps might take some time to meet the quality threshold.

Configure your Google API Console project

Google uses the Google API Console to configure access for apps to communicate with the Google APIs. For direct app installs, you must use the same project for your Web and Android apps.

  1. Go to the Credentials page of the API Console.
  2. Create credentials for each app into which you want to integrate direct app installs. If you have multiple Android apps, the order that you define your client IDs determine which app is installed.
    1. For the Android app that you want your users to be prompted to download, click Add credentials > OAuth 2.0 client ID, select Android, and complete the form.
    2. For your web app, click Add credentials > OAuth 2.0 client ID, select Web application, and complete the form.
    3. If you have additional clients, such as a paid version of your Android app or an iOS app, create OAuth 2.0 client IDs for those apps as well. This grouping enables deep linking to work across your mobile apps if you enable it for your client IDs.

Configure your web app

Your web app must use the Google Sign-In button to prompt your web site users to download your app the first time that they sign in. This feature is enabled by adding the app_package_name parameter to your sign-in button.

  1. Add a sign-in button to your app.
  2. Add the data-app_package_name parameter to your HTML button or the app_package_name parameter to the signIn() or render() methods. Specify your Android app's package name as the value. This value should be the same as the value that you entered in the Google API Console for the Android app that you want your users to download.
  3. If you previously authorized the app for your account, you need to disconnect the app before you can try out the direct app install.
  4. Refresh your web app to pick up the change to the app_package_name parameter.
  5. Test your automatic app install by visiting your web app and clicking the sign-in button. First, you should see the authorization dialog. After accepting the authorization dialog, you will see the direct app install prompt.

Testing Android app installs for your web site

If your app meets the eligibility requirements, you can test the over-the-air install feature by signing in to your app for the first time with your account. If you want to test subsequent app installs, you will need to follow these steps:

  1. Revoke your accounts access tokens for the app. It is recommended that your app provide users with an option to revoke access from within your app. You can also manually disconnect and revoke tokens.
  2. Uninstall the app from all of the Android devices where you use the app and signed into it with this account.
  3. Wait for at least 30 minutes to test the sign-in flow from your web app to try to trigger the app install prompt.