Google is committed to advancing racial equity for Black communities. See how.

Set up Google Play services

To develop an app using Google Play services APIs, set up your project with the relevant SDKs, which are available from the Google maven repository.

For more detailed instructions, view the Android Studio page about how to update the SDK tools that your app project uses.

To test your app when using Google Play services, you must use one of the following:

  • A compatible Android device that runs Android 4.1 (API level 16) or higher and has the Google Play Store app installed.
  • The Android emulator with an AVD that runs the Google APIs platform based on Android 4.2.2 (API level 17) or higher.

Declare dependencies for Google Play services

To develop features that depend on the Google Play services APIs in your app, complete the following steps:

  1. Open the build.gradle file inside your app's module directory.

  2. For each SDK that your app requires, include the dependency for that SDK. This page includes a section that lists common Google Play services dependencies for Android apps. You might also want to add Firebase dependencies to your project.

  3. Save the changes and sync your project.

The following snippet shows an example build.gradle file that uses the location library:

apply plugin: ''


dependencies {
    implementation ''

New versions of the Google Play services SDKs with bug fixes and new features are periodically released. These updates are announced in the release notes. If your app uses a dependency that has been updated, change to the latest version in your app's dependencies to take advantage of these fixes.

Check whether Google Play services is installed

As described in the Google Play services overview, Google Play services receives automatic updates on Android 4.1 (API level 16) and higher through the Google Play Store app. However, Android devices without Google Play Store don't have Google Play services installed. If your app runs on devices without Google Play services, you might want to check to see if Google Play services is installed on the device before you attempt to use Google APIs, or enable features in your app that require Google Play services to function.

To check for the presence of Google Play services on the device, use the isGooglePlayServicesAvailable() method.

To then begin a connection to Google Play services, or learn how to detect whether the version of Google Play services installed supports a specific API, read the guide on Accessing Google APIs.

List of Google Play services dependencies

Table 1 contains the set of dependencies powered by Google Play services, which you can include in your app:

Table 1. Google Play services dependencies to include in a build.gradle file, and the use cases that the dependencies fulfill.
Use case Dependency name
Google Mobile Ads
Android Advertising ID (AAID)
Lightweight version of Google Mobile Ads
AdSense for Search (AFS) Custom Search Ads (CSA)
Google Analytics Services SDK for Android
Google Sign-In for Android
SMS Retriever API
Google Awareness API
Utility classes
More utility classes
Google Cast
Google Cast Application Framework (CAF)
Android TV Receivers
Chromium network stack (Cronet)
Fast IDentity Online (FIDO) Authentication
Google Fit API for Android
Google Play Games Services for Android
Google Play Instant
Fused Location Provider for Android (includes activity recognition and geofencing)
Google Maps SDK for Android
ML Kit barcode scanning
ML Kit face detection
ML Kit image labeling
ML Kit text recognition
Nearby device discovery and connection
Show open-source licenses
Screen lock quality check
reCAPTCHA Enterprise for app instrumentation
SafetyNet APIs
Google Tag Manager
Tasks API on Android
Mobile Vision
Google Pay for Payments on Android
Wearable Data Layer API

Gradle plugins

Google Play services also includes several Gradle plugins, as shown in Table 2:

Table 2. List of Gradle plugins included in Google Play services.
Use case Gradle plugin name
Show open-source licenses
Strict version checking