Stay organized with collections
Save and categorize content based on your preferences.
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:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-01 UTC."],[[["The Places SDK for Android (New) offers enhanced performance and a revised pricing structure, encouraging app updates."],["To minimize potential cost increases, it's advisable to transition to the new APIs at the start of a billing cycle."],["Before using the new SDK, enable the \"Places API (New)\" in your Google Cloud project and include it in your API key."],["Places SDK for Android (New) introduces mandatory field masking for Place Details, Nearby Search, and Text Search, defining specific data returned in responses."],["New features like Text Search (New) and Nearby Search (New) are additions to the SDK and do not require migration from existing functionalities."]]],["The Places SDK for Android (New) offers improved performance and a new pricing structure. To utilize it, enable the \"Places API (New)\" service in your Google Cloud project and add it to your app's API key. General changes include a new pricing model, required field masking for Place Details, Nearby Search, and Text Search, along with the addition of new classes. The `Place` object now has a `getReviews()` method. Switch to the new APIs as early as possible in the month to minimize billing costs.\n"]]
