The Places SDK for Android (New) provides improved performance and a newpricing model, making it worthwhile to update apps that use thePlaces SDK for Android (Legacy). For more details on comparing features,seeChoose your SDK.

Use this guide to understand key differences in thePlaces SDK for Android (New) compared to thePlaces SDK for Android (Legacy), along with how to handle necessarychanges.

Billing best practices for migration

This guidance applies if your API usage is high enough tomove 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 ofyour transition, we recommend switching to the new APIs in production as close to thebeginning of the month as possible. This will ensure that you reach the most cost-effectivemonthly pricing tiers during the migration month. For information about pricing tiers,see thepricing pageand thepricing FAQ.

Enable Places API (New)

Places SDK for Android (Legacy) relies on thePlaces API service. To use the features ofPlaces SDK for Android (New), you must first enablePlaces API (New) in your Google Cloud project. For moreinformation, seeSet up your Google Cloudproject.

You then must ensure that you have addedPlaces API(New) to the list of authorized APIs on the key used by your app. For moreinformation, seeUse API Keys.

Ensure that you have enough quota in Places API (New)

Make sure that there is enough quota in the Places API (New) tocover your current traffic. To review and manage yourquotas and usage limits, seeQuotas and quotaalerts.

Note the difference:

• The quota for Places SDK for Android (Legacy) relies on the quota ofthe Places API service. It is the sum of all Places API methods.
• The quota for Places SDK for Android (New) relies on the quota ofthe Places API (New) service. There is a separate quota for eachAPI method.

Check if your negotiated agreement includes Places API (New)

If you have a negotiated agreement, check that it covers thePlaces API (New), with the expected pricing. If not, contact yourSales contact person at Google or your partner to discuss how you can includethis API.

General changes

Some general changes that apply to multiple APIs include:

• Uses a new pricing model. For pricing information for all APIs, seePlaces SDK for Android(New).

• You must initialize your app by calling thePlaces.initializeWithNewPlacesApiEnabled()method. For more information on selecting the Places API service, seeSetup your Google Cloudproject.

• Place Details(New),Nearby Search(New), andText Search(New) require fieldmasks to specify which fields you want returned in the response.

• New classes have been added to define the requests or to add new fields tothe response.

• The responsePlaceobject contains the newgetReviews()method that returns a List ofReviewobjects. When your app displays information obtained from thePlaceobject, such as photos and reviews, the app must also display the requiredattributions.

  For more information, see the documentation onattributions.

• Migrate from Place Details (Legacy) to Place Details (New)
• Migrate from Place Photo (Legacy) to Place Photo (New)
• Migrate from Autocomplete (Legacy) to Autocomplete (New)
• Migrate from Current Place (Legacy) to Nearby Search (New)