Places SDK for iOS version 8.5.0 supports two SDK versions: Places SDK for iOS is the existing Places SDK for iOS (New) is the next generation version of the SDK.
With the release of Places SDK for iOS version 8.5.0, your first task is to decide which SDK to use. This is true if you are a new customer or an existing customer already using the SDK. Use this guide to understand the key differences between the two SDKs.
How to select your SDK version
Places SDK for iOS relies on the Places API service. Before you can use Places SDK for iOS, you must enable the Places API service in your Google Cloud project.
The version of the Places API service that you enable controls the SDK version used by your app:
Places API: Enables the existing Places SDK for iOS. If only Places API is enabled for the project associated with the API key used for your app, your app won't have access to the new features added in Places SDK for iOS version 8.5.0 and later.
Places API (New): Enables Places SDK for iOS (New) including Text Search and all new features described in Key features added to Places SDK for iOS (New). Does not enable existing features such as Place Details, Place Photos, Current Place, and Place Autocomplete.
Both: Enables all the features for both Places SDK for iOS (New) and Places SDK for iOS.
For more information on selecting the Places API service, see Set up your Google Cloud project.
Which SDK do you choose?
To help decide which version to choose:
If you are a new customer just getting started with Places SDK for iOS, then start with both Places API (New) and Places API so you have access to all features.
If you are an existing customer, you can continue using the existing SDK. However, to take advantage of the performance improvements and the feature enhancements of the Places SDK for iOS (New), you can use the new SDK.
There is no migration necessary when moving to the new SDK. You only have to enable Places SDK for iOS (New) on the API key used in your app. If you are using both the existing Places SDK for iOS and Places SDK for iOS (New), enable both versions on your API key. For more information, see Use API Keys.
Key features added to Places SDK for iOS (New)
This section covers key features added to Places SDK for iOS (New).
Implemented on the Google Cloud standard platform
Places SDK for iOS (New) is implemented on the service infrastructure on Google Cloud. This implementation brings a more secure and trusted platform. This standard design brings a level of consistency across the SDKs that improve the efficiency of development with Places SDK for iOS (New).
Improved performance
Places SDK for iOS (New) provides improved performance, making it worthwhile to replace apps that use the existing SDK.
New Text Search service
Text Search returns information about a set of places based on a string — for example "pizza in New York" or "shoe stores near Ottawa" or "123 Main Street". The service responds with a list of places matching the text string and any location bias that has been set.
Simplified pricing
Pricing is simplified with Places SDK for iOS (New) so that you only pay for the data you use. Simplified pricing is implemented using field lists, also called field masks.
With Places SDK for iOS and Text Search you use field lists to control the list of fields to return in the response. You are then only billed for the data requested. Using a field list is a good design practice to ensure that you don't request unnecessary data, which helps to avoid unnecessary processing time and billing charges.
For detailed pricing information for both SDKs, see Usage and Billing.
Expanded place types
The new SDK adds the place types shown in the following table. These types are returned as part of the Place Details and Text Search response. You can also use these new types, and the existing types, in a search with Text Search. The new types are included in Table A.
| Type | |||
|---|---|---|---|
| american_restaurant | discount_store | ice_cream_shop | sandwich_shop |
| amusement_center | dog_park | indian_restaurant | school_district |
| athletic_field | electric_vehicle_charging_station | indonesian_restaurant | seafood_restaurant |
| auto_parts_store | event_venue | italian_restaurant | ski_resort |
| banquet_hall | extended_stay_hotel | japanese_restaurant | spanish_restaurant |
| barbecue_restaurant | farm | korean_restaurant | sporting_goods_store |
| barber_shop | farmstay | lebanese_restaurant | sports_club |
| bed_and_breakfast | fast_food_restaurant | marina | sports_complex |
| brazilian_restaurant | ferry_terminal | market | steak_house |
| breakfast_restaurant | fitness_center | medical_lab | sushi_restaurant |
| brunch_restaurant | french_restaurant | mediterranean_restaurant | swimming_pool |
| bus_stop | gift_shop | mexican_restaurant | tailor |
| camping_cabin | golf_course | middle_eastern_restaurant | telecommunications_service_provider |
| cell_phone_store | greek_restaurant | motel | thai_restaurant |
| child_care_agency | grocery_store | national_park | transit_depot |
| chinese_restaurant | guest_house | park_and_ride | truck_stop |
| coffee_shop | hair_salon | performing_arts_theater | turkish_restaurant |
| community_center | hamburger_restaurant | pizza_restaurant | vegan_restaurant |
| consultant | heliport | playground | vegetarian_restaurant |
| convention_center | hiking_area | preschool | vietnamese_restaurant |
| cottage | historical_landmark | private_guest_room | visitor_center |
| courier_service | home_improvement_store | ramen_restaurant | wedding_venue |
| cultural_center | hostel | resort_hotel | wholesaler |
| dental_clinic | hotel | rest_stop |
countryadministrative_area_level_1administrative_area_level_2postal_codelocality