3 ms·
Maps in iOS6 look great, but will moving away from Google break legacy apps for <5.1? I'm sure main stuff will integrate pretty seamlessly, but what about the l
by JoeCortopassi 14y ago
Maps in iOS6 look great, but will moving away from Google break legacy apps for <5.1? I'm sure main stuff will integrate pretty seamlessly, but what about the little stuff? (e.g. in a UIWebView, if I make a link to google maps, when the user clicks it, they are taken to the Map app). In the long run, it's the right decision, I'm just eager to test some of our MapKit apps on iOS6, to see what breaks
- vijaykiran 14y agoFWIW, my small app which uses MKMapView just to show a location - works fine on iOS6 as is. Of course. I'd guess that API (is and) will be backward compatible.
- _frog 14y agoI'll chime in here as I'm currently working on an app that uses MapKit extensively. MKMapViews work in pretty much the same way as they did in iOS 5, no breaking changes. The one thing that did break in my case was the feature of my app that opened up a walking route in the old Maps app. On iOS 5 this is done by redirecting any maps.google.com URL requests to the Maps app but of course this doesn't work with the new method. Thankfully they've replaced this with a generic API that allows you to programmatically create a routing request (no more string concatenation!) and pass it to any app which implements the required protocol for handling it, right now that's just the Maps app but I'm sure that selection will expand once iOS 6 is out.