
Yesterday we saw the appearance of the new iPad which was accompanied by a new Apple TV and some other goodies. A special interest happened to be around the new iPhoto for iOS and OS X. As Stephen Hackett of 512 Pixels (via Matthew Panzarino) discovered first, the app isn’t using Google Maps any longer. Apparently Apple is now using their own map service. Here’s how I found out using mitmproxy and some simple changes in iOS that redirect all wireless traffic through a designated proxy.
Using mitmproxy – this tool was also used to discover the recent Path privacy brouhaha – it was easy to figure out that the requests went to Apple’s own servers:
But not only iPhoto for iOS is using Apple’s service, also iPhoto on OS X uses it to create the slideshows, as Jonas K. via Twitter mentioned earlier:
@holgr could you do the same test for iPhoto 11 slideshows as well? Also seem to be using Apple maps, see twitter.com/jokru/status/1…
— Jonas K. (@jokru) March 8, 2012
With the help of mitmproxy it’s easy to find out what’s going where. Of course nobody except Apple currently knows for sure where the mapping data is actually coming from. The current guess currently is OpenStreetMap (OSM). If you want to compare the various mapping sources, including Apple’s and OSM, there’s a site for that.




Apple starts using their own mapping service, ditches Google Maps: Yesterday we saw the appearance of the new iP… http://t.co/DfNbEepS
No more Google Maps for Apple’s new iOS apps http://t.co/VINORKIY via @holgr
[…] aren’t yet as accurate as Google’s, if only because they are short of place names. A report here even takes a looks at the way these mapping tools work to discover they are indeed getting their […]
[…] nonetheless as accurate as Google’s, if usually since they are brief of place names. A report here even takes a looks during a approach these mapping collection work to learn they are indeed […]
[…] Holger Eilhard later confirmed that the map images in iPhoto for iOS are being pulled down from Apple’s own […]