Stay organized with collections
Save and categorize content based on your preferences.
European Economic Area (EEA) developers
The Places SDK for Android (New) provides improved performance and a new
pricing model, making it worthwhile to update apps that use the
Places SDK for Android (Legacy). For more details on comparing features,
see Choose your SDK.
Use this guide to understand key differences in the
Places SDK for Android (New) compared to the
Places SDK for Android (Legacy), along with how to handle necessary
changes.
Billing best practices for migration
warning_amber
This guidance applies if your API usage is high enough to
move into second-tier pricing. When migrating to a newer version of an API,
you're also being billed for a different SKU. To avoid increased costs during the month of
your transition, we recommend switching to the new APIs in production as close to the
beginning of the month as possible. This will ensure that you reach the most cost-effective
monthly pricing tiers during the migration month. For information about pricing tiers,
see the pricing page
and the pricing FAQ.
Enable Places SDK for Android (New)
Places SDK for Android (Legacy) relies on the
Places API service. To use the features of
Places SDK for Android (New), you must first enable
Places API (New) in your Google Cloud project. For more
information, see Set up your Google Cloud
project.
You then must ensure that you have added Places API
(New) to the API key used by your app. For more information, see Use API
Keys.
General changes
Some general changes that apply to multiple APIs include:
New classes have been added to define the requests or to add new fields to
the response.
The response Place
object contains the new
getReviews()
method that returns a List of
Review
objects. When your app displays information obtained from the Place
object, such as photos and reviews, the app must also display the required
attributions.
For more information, see the documentation on
attributions.
API-specific changes
This section includes the following migration guides for each API:
[null,null,["Last updated 2025-08-28 UTC."],[],[],null,["# Migration overview\n\n**European Economic Area (EEA) developers** If your billing address is in the European Economic Area, effective on 8 July 2025, the [Google Maps Platform EEA Terms of Service](https://cloud.google.com/terms/maps-platform/eea) will apply to your use of the Services. Functionality varies by region. [Learn more](/maps/comms/eea/faq).\n\nThe Places SDK for Android (New) provides improved performance and a new\npricing model, making it worthwhile to update apps that use the\nPlaces SDK for Android (Legacy). For more details on comparing features,\nsee [Choose your SDK](/maps/documentation/places/android-sdk/choose-sdk).\n\nUse this guide to understand key differences in the\nPlaces SDK for Android (New) compared to the\nPlaces SDK for Android (Legacy), along with how to handle necessary\nchanges.\n\n\nBilling best practices for migration\n------------------------------------\n\nwarning_amber\n\nThis guidance applies if your API usage is high enough to\nmove into second-tier pricing. When migrating to a newer version of an API,\nyou're also being billed for a different SKU. To avoid increased costs during the month of\nyour transition, we recommend switching to the new APIs in production as close to the\nbeginning of the month as possible. This will ensure that you reach the most cost-effective\nmonthly pricing tiers during the migration month. For information about pricing tiers,\nsee the [pricing page](/maps/billing-and-pricing/pricing)\nand the [pricing FAQ](/maps/billing-and-pricing/faq).\n\n\u003cbr /\u003e\n\nEnable Places SDK for Android (New)\n-----------------------------------\n\nPlaces SDK for Android (Legacy) relies on the\n**Places API** service. To use the features of\nPlaces SDK for Android (New), you must first enable\n**Places API (New)** in your Google Cloud project. For more\ninformation, see [Set up your Google Cloud\nproject](/maps/documentation/places/android-sdk/cloud-setup).\n\nYou then must ensure that you have added **Places API\n(New)** to the API key used by your app. For more information, see [Use API\nKeys](/maps/documentation/places/android-sdk/get-api-key).\n\nGeneral changes\n---------------\n\nSome general changes that apply to multiple APIs include:\n\n- Uses a new pricing model. For pricing information for all APIs, see [Places SDK for Android\n (New)](/maps/billing-and-pricing/pricing#places-pricing).\n\n- [Place Details\n (New)](/maps/documentation/places/android-sdk/place-details), [Nearby Search\n (New)](/maps/documentation/places/android-sdk/nearby-search), and [Text Search\n (New)](/maps/documentation/places/android-sdk/text-search) require field\n masks to specify which fields you want returned in the response.\n\n- New classes have been added to define the requests or to add new fields to\n the response.\n\n- The response [`Place`](/maps/documentation/places/android-sdk/reference/com/google/android/libraries/places/api/model/Place)\n object contains the new\n [`getReviews()`](/maps/documentation/places/android-sdk/reference/com/google/android/libraries/places/api/model/Place#getReviews())\n method that returns a List of\n [`Review`](/maps/documentation/places/android-sdk/reference/com/google/android/libraries/places/api/model/Review)\n objects. When your app displays information obtained from the `Place`\n object, such as photos and reviews, the app must also display the required\n attributions.\n\n For more information, see the documentation on\n [attributions](/maps/documentation/places/android-sdk/policies#other_attribution_requirements).\n\n| **Note:** Because Text Search (New) and Nearby Search (New) were added to Places SDK for Android and did not replace any existing APIs, there is no migration required to use them.\n\nAPI-specific changes\n--------------------\n\nThis section includes the following migration guides for each API:\n\n- [Migrate to Place Details (New)](/maps/documentation/places/android-sdk/migrate-details)\n- [Migrate to Place Photo (New)](/maps/documentation/places/android-sdk/migrate-photo)\n- [Migrate to Autocomplete (New)](/maps/documentation/places/android-sdk/migrate-autocomplete)"]]
