Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I agree with Omar that Apple will probably work quite hard to make sure <code>MapKit</code> isolates developers from breakage. But, there will be <em>some</em> problems.</p> <p>The first problem I see is usage of undocumented features of Google Maps. Undocumented doesn't necessarily mean the same thing as <em>Private APIs</em>, which it's pretty hard to sneak into the app store (although not impossible).</p> <p>For example, <a href="https://stackoverflow.com/questions/576768/how-to-invoke-iphone-maps-for-directions-with-current-location-as-start-address">this technique for opening Maps with a URL</a>, to display routes. This is different than using <code>MapKit</code>, but it still could be an issue for some apps.</p> <p>The second thing I see are potential <em>legal</em> issues associated with Google Maps. If I remember correctly, there are Google geocoding web services, that allow free usage, so long as you display the results on a Google map. Currently, iPhone maps are Google maps (Maps.app or <code>MapKit</code> maps). In the future, they map not be. If <a href="https://stackoverflow.com/questions/10992595/can-i-still-use-google-maps-in-ios-6">your app relies on a back end that uses Google geocoding services</a>, you may have some rework to do.</p> <p>Anyway, the majority of maps-related code should not break. I just wanted to give a couple examples of where there could be problems.</p> <p><strong>Update:</strong> also, there have been reports that the new Apple Maps are inferior to Google Maps in a few ways. Although it might still <em>work</em>, if your app is doing something like routing to an <em>address</em>, you might find that Apple's new maps app does a poorer job of finding the location you give it. So, in order to work <em>as well</em> as it used to, you may need to refactor your app to use coordinates, rather than addresses. Again, little things might turn out to make a difference here.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload