Google Separated Places API & Maps SDK for iOS

By Mobile App Team IPhone App

Google today said it is putting the Google Places API for iOS 2.0 and the Google Maps SDK for iOS 2.0 into partitioned CocoaPods. The thought here is to lessen the application size for developers who need Places data, yet not Maps data.

It will require some investment for the change reported by Google today to produce results, so don't race to roll out improvements to your application just yet.
As a matter of first importance, the move to pull the Places API from the Maps SDK targets one and only subset of programmers: the individuals who utilize the Places API for iOS. In case you're utilizing Maps for iOS, there is nothing to stress over or change.

Hire an iOS Developer

As per usual, Google proposes all developers move up to Google Maps SDK for iOS 2.0 and Google Places API for iOS 2.0 inside 12 month, as the more seasoned v1.x manufactures won't be bolstered come mid-2017.

Why trouble? Application size.

"Beforehand, on the off chance that you needed to utilize the Places API you needed to incorporate all of Google Maps," clarified Google in the discharge notes. "As a consequence of the split, the last size of the Places API paired is 70% littler than the past consolidated binary." That's a critical diminishment for applications that need just the Places API and not the whole Maps SDK.

There are different advantages. Google asserts the whole Google Maps paired is currently under 100MB, which gives it a chance to press in under GitHub's maximum record size point of confinement. In addition, the Maps system is presently accessible as a download for manual establishment, marker information windows now render reliably, and data windows will now effectively regard the tallness of the returned content as opposed to continually being square taking into account the width.

Developers on the Standard Plan Google Maps SDK for iOS 1.x who have not focused on a particular adaptation in their profile I'll be moved up to the new SDK naturally after running "Pod upgrade." Developers who've picked particular Places capacities can exploit another relocation manual for smooth over the way toward moving from variant 1.x to rendition 2.0. Google has full documentation on the most proficient method to concentrate Maps and Places from their particular CocoaPods, which will give designers a chance to utilize the SDKs physically in their applications and undertakings when suitable.

Google is getting rid of the Premium Plan Maps SDK, which has been supplanted with the new SDK for iOS 2.0 for Standard and Premium Plan engineers. Google has made a relocation manual for help engineers make this move, as well. Google noticed that designers' Enterprise Maps keys will keep on working close by their Premium Plan, which won't be stopped or generally killed.

Google Maps SDK for iOS Premium Plan 1.13.2 will be upheld for the following year, yet Google firmly proposes all engineers upgrade to adaptation 2.0 when functional.