Migration overview

The Places SDK for iOS (New) provides improved performance and a new pricing model, making it worthwhile to update apps that use Places SDK for iOS. For more details on comparing features, see Choose your SDK.

Use this guide to understand key differences in Places SDK for iOS (New) compared to Places SDK for iOS, along with how to handle necessary changes.

Enable Places SDK for iOS (New)

Places SDK for iOS relies on the Places API service. To use the features of Places SDK for iOS (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:

• Uses a new pricing model. For pricing information for all APIs, see Pricing for the Places SDK for iOS (New).

• Field masking is required by Place Details (New), Nearby Search (New), and Text Search (New) to specify which fields you want returned in the response.

• GMSPlacesClient contains new methods to call these new APIs.

• New classes have been added to define the request to each of the new APIs.

• The response GMSPlace instance contains the new reviews property of type GMSPlaceReview. When your app displays information obtained from the GMSPlace instance, such as photos and reviews, the app must also display the required attributions.

  For more information, see the documentation on attributions.

Note: Because Text Search (New) and Nearby Search (New) were added to Places SDK for iOS and did not replace any existing APIs, there is no migration required to use them.

API-specific changes

This section includes the following migration guides for each API:

• Migrate to Place Details (New)
• Migrate to Place Photo (New)
• Migrate to Autocomplete (New)