Select platform: [Android](https://developers.google.com/maps/documentation/places/android-sdk/versions.md.txt "View this page for the Android platform docs.") [iOS](https://developers.google.com/maps/documentation/places/ios-sdk/versions.md.txt "View this page for the iOS platform docs.") [JavaScript](https://developers.google.com/maps/documentation/javascript/versions.md.txt "View this page for the JavaScript platform docs.")

<br />

> [!NOTE]
> **Note:** The Places SDK for Android features that are available in your app are determined by a combination of the SDK version number that you specify in your app configuration, the APIs enabled on your API key, and how you initialize your app. For more information, see [Choose your SDK
> version](https://developers.google.com/maps/documentation/places/android-sdk/choose-sdk).

The Google Maps Platform team regularly updates SDKs with new features, bug fixes, and
performance improvements. This page provides guidance on how to manage your dependencies
on mobile SDKs.

## Which version to link to?

- **For mission-critical apps**, link to the latest dot release of the major
  version that you are using (X.\*), and upgrade yearly to the new major version.

  As you release new versions of your application
  throughout the year, you may start using newer dot versions of the Places SDK for Android. This will
  not require updates in your application as new dot versions are backward compatible.

  **Benefits:**
  - If you discover issues in the Places SDK for Android, fixes will be provided in a backward-compatible way for 12 months after the initial release of the major version, per the [Mobile support
    policy](https://developers.google.com/maps/software-support#sdk-support). You will not need to urgently upgrade to an *incompatible* SDK version to benefit from fixes.
  - The latest improvements and features are easy to adopt when your app is already built on the latest version.
  - Annual incremental updates to the newest major version of the SDK might require less work to adapt, rewrite, and test your application than having to handle backward-incompatible changes introduced across multiple major version releases.
- **For non-critical apps**, link to any fixed version. When you receive a deprecation
  notice for that fixed version, you will have 12 months to make your updated app code available to
  your users.

  **Benefits:**
  - Less frequent maintenance work.
  - New versions of your app keep supporting users' devices running earlier mobile operating systems for longer (until you need to upgrade to a new SDK version).

Project owners with monitored email addresses receive proactive notifications about changes that
affect each of their projects. [Stay
informed](https://developers.google.com/maps/support#staying_informed) about major updates, deprecations, and other changes.

## Installation

In your app-level `build.gradle.kts` or `build.gradle` file, always specify
a version instead of a prefix range (`+`) or `latest` because these can lead
to unpredictable and unrepeatable builds. The Places SDK for Android adheres to
[semantic versioning](https://semver.org), and new
major version releases may include breaking changes. **The minimum API level supported is
24**.

```
dependencies {

    // Places and Maps SDKs
    implementation("com.google.android.libraries.places:places:6.0.2")
}
```

## Maintenance and upgrade

Android Studio automatically checks for newer available versions and provides a warning when a
newer version of a dependency is available. To minimize technical debt, update to the newest
available version as soon as possible. If you are updating to a new major version,
[check the release notes](https://developers.google.com/maps/documentation/places/android-sdk/releases)
for backward-incompatible changes and how to update your code.

> [!NOTE]
> **Note:**The minimum API level required by Maps SDK for Android version 19.0.x is Android API Level 23 ("Marshmallow"; Android 6.0) or higher.

In addition to polling for newer versions, Google Cloud
[project
owners](https://cloud.google.com/iam/docs/roles-overview#basic) receive emails about backwards incompatible changes that may
affect their projects. To get proactive notification about backwards incompatible
changes, [assign
the owner role](https://cloud.google.com/iam/docs/granting-changing-revoking-access) with a monitored email address for each of your projects.

### If you are upgrading from Places SDK for Android version 3.2.0 or earlier

There is no migration necessary when moving to the new SDK. You only have to:

1. Enable **Places API (New)** on the API key used in your app. For more information, see [Using API Keys](https://developers.google.com/maps/documentation/places/android-sdk/get-api-key.md.txt).
2. In the `dependencies` section of your module-level
   `build.gradle` file, update the `places` dependency
   and add the `kotlin-bom` dependency:

   ```
     dependencies {
         implementation(platform("org.jetbrains.kotlin:kotlin-bom:1.8.0"))
         implementation 'com.google.android.libraries.places:places:3.5.0'
     }
   ```

   For more information on the `kotlin-bom` dependency, see
   [Usage of the latest kotlin-stdlib version in transitive dependencies](https://kotlinlang.org/docs/whatsnew18.html#usage-of-the-latest-kotlin-stdlib-version-in-transitive-dependencies).
3. Update your existing app to call the new [`Places.initializeWithNewPlacesApiEnabled()`](https://developers.google.com/maps/documentation/places/android-sdk/reference/com/google/android/libraries/places/api/Places.md.txt#initializeWithNewPlacesApiEnabled(android.content.Context,%20java.lang.String)) method to initialize your app. For more information, see [Initialize the Places API client](https://developers.google.com/maps/documentation/places/android-sdk/config.md.txt#connect-client).

Your existing apps continue to work unchanged, but you can now take
advantage of all new SDK features.