Google Places API Violation

Question

I am using Google Places API to pull a list of resturants, and I am displaying them on map. However, since Apple has switched there map services over from Google in iOS 6.0, I am now in violation of Google's terms of use, which states that you must display Google data on a Google map.

"If your application displays Places API data on a map, that map must be provided by Google."

https://developers.google.com/places/policies#terms_of_use

I obviously need to change the map, because I am not going to release an application that is in violation. Any thoughts or suggestions on what to do? Should I go Google Maps with a web view? Does apple have some sort of Google Places API alternative?

Edit:

Using Google Maps through a web view is a hassle, i'd like to find an alternative to that, although it would technically work.

Answer 1

I decided to use Google Maps JavaScript API. Although, it is a little more difficult to deal with, mainly the JavaScript through Objective-C, it is a solution. The map is displayed through a web view, and I use JavaScript to interact with the map.

https://developers.google.com/maps/documentation/javascript/tutorial#api_key

I will wait to accept this answer, to see if anyone else has any thoughts. I just wanted to post this, in case it helps someone else.

Edit:

Google recently released a Maps SDK for iOS, this is the better solution now.

https://developers.google.com/maps/documentation/ios/

Answer 2

I would try to directly contact Google, explaining the situation, and ask them for written permission to use Apple's maps. This is more a legal question than programming. One would think that Google is aware that you can no longer display their maps using Apple's API and that, even regardless of the map, they would want you to use their places, as doing so generates advertising revenue for them.

Answer 3

Agree with @Owen here - you could get permission to leave your app unchanged until some possible future date when you might have to change it, or could you definitely go to the effort of changing it now and then possibly have to change it again in the future for some other reason.

If you could get a 100% guarantee that you could change it once and never have to change it again then I'd say do it now, but nothing's certain.