iOS 11 won’t be available to iPhone and iPad users until the fall, but tech journalists are already noting the improvements coming to Apple’s maps, including lane guidance, augmented-reality enhanced Flyover maps, indoor maps and one-handed mode, among others.
Justin O’Beirne is back with a look at how both Google and Apple Maps have changed incrementally over the past year.
Shortly after I published my Cartography Comparison last June, I noticed Google updating some of the areas we had focused on[.]
Coincidence or not, it was interesting. And it made me wonder what else would change, if we kept watching. Would Google keep adding detail? And would Apple, like Google, also start making changes?
So I wrote a script that takes monthly screenshots of Google and Apple Maps. And thirteen months later, we now have a year’s worth of images […]
It’s cool to see how much Google Maps has changed over the past year. But it’s also surprising to see how little Apple Maps has changed[.]
I’ve just upgraded my iPhone and iPad to iOS 10, but haven’t had a chance to mess with the new version of Apple Maps; iMore and Macworld set out the changes, including integrated services and apps, predictive intelligence, and improvements in driving directions and search, among other things. Also, you can set it to remember where you parked, which isn’t new in and of itself, but is for iOS.
“We made significant changes to all of our development processes because of it,” says Cue, who now oversees Maps. “To all of us living in Cupertino, the maps for here were pretty darn good. Right? So [the problem] wasn’t obvious to us. We were never able to take it out to a large number of users to get that feedback. Now we do.”
Apple senior vice president Eddie Cue, quoted in this Fast Company profile of Apple, on how the Apple Maps debacle changed Apple’s famously insular culture, opening things up to the point that they now have a public beta program. [James Fee]
iLounge’s Jesse Hollington looks at the changes coming to Maps in iOS 10, the next release of Apple’s operating system for the iPhone and iPad. “Functionally, it doesn’t quite incorporate the kind of sweeping changes we’ve seen in prior years, but instead focuses on redesigning the user experience and adding a few useful iterative features.” (Thanks to James Fee for the link.)
Justin O’Beirne, who has previously mused about the possibility of a Universal Map and looked at how Google Maps has changed over the past few years, has now embarked on a multi-part comparison of the cartographic designs of Google Maps and Apple Maps. “We’ll take a look at what’s on each map and how each map is styled, and we’ll also try to uncover the biggest differences between the two.” The first part is already up: it looks at city labels, highway markers, road labels, and points of interest, and reveals some interesting divergences in terms what each platform chooses to put on the map. (Note that it’s a very big page, and even on a fast connection the images may take some time to load.) [Cartophilia]
Yesterday’s updates to Apple Maps include four new Flyover cities, traffic data for Hong Kong and Mexico, public transit data for Los Angeles, and Nearby search for the Netherlands.
Google Earth Blog reports on the mid-January imagery update for Google Earth.
Google Earth Blog also reports that version 1.0 of ArcGIS Earth is now available. Announced last June and previously available as a series of public betas, ArcGIS Earth appears to be aimed at filling the gap left by Google when Google Earth Enterprise was discontinued last year.
Mont Blanc, the highest mountain in the Alps, is now in Street View.
Time’s John Patrick Pullen compares how easy or difficult it is to send driving directions to your phone using maps from Apple, Google and Microsoft before coming up with a surprise winner: “I pulled up MapQuest for a punchline on this story, but the joke’s on all of us. MapQuest is, by far, the easiest way to get maps from your desktop to your phone.” I really ought to try this out myself and see if I agree with him.
A major feature of Apple’s forthcoming Maps application for OS X 10.9 Mavericks is enhanced error reporting. AppleInsider has the details. This was inevitable, not just because of the uneven quality of Apple’s maps and the reputational firebombing they’ve gotten since their launch last year, but because all online maps suck and need error reporting. Of course, reports are one thing; how quickly and effectively they’re acted on—that’s what’s important.
Previously: Apple Maps on the Mac.
A Mac version of Apple’s maps was among the new features announced for Mac OS X 10.9 Mavericks at Apple’s Worldwide Developers Conference (WWDC) on Monday. Coverage: 9to5Mac, The Verge. I’m surprised to see that they’re doing it as a standalone application rather than on the Web, which is what I’d expected. One trick of the app is that you can send turn-by-turn directions to your iOS device. There’s an API, so developers will also be able to integrate the maps into their own apps. If they want. Cue old and tired jokes about Apple maps’ quality in three, two …
This is something I’ve been meaning to write for a while. I should have written it last December, during the hullaballoo over Apple’s maps, but I’ve never been one to strike when the iron is hot.
You’ll recall that there were a lot of complaints about Apple’s maps app when it launched with iOS 6, replacing the previous app that was powered by Google Maps. The map data didn’t match the user experience: it was a first-rate app that used second-rate data. Apple oversold the experience and failed to meet the high expectations of its customers. It was a problem that no other online map provider had ever had to deal with before, not least because no one had launched a new map service with the same amount of hubris, nor the same amount of scrutiny from day one.
But many of the complaints about Apple’s maps verged into hyperbole. The notion that Apple’s maps were uniquely bad compared to other online maps was frankly unfair. Because when you get right down to it, all online maps suck. They all fail in some way, somewhere, and some more than others—and if the maps you use seem fine to you, it’s because they suck somewhere else.
Details continue to emerge, as details tend to do, about how and why Apple replaced Google with its own maps in iOS 6. John Paczkowski reports that the Apple-Google maps arrangement faltered over voice-guided turn-by-turn directions, which Google Maps has had on Android for years but Apple couldn’t get from Google. John Gruber looks at the timeline of Apple’s contract with Google here and here, and has some ideas why Apple would give the boot to Google with time still on the clock.
Pogue calls Apple’s Maps app “an appalling first release. It may be the most embarrassing, least usable piece of software Apple has ever unleashed.” (I guess he never tried version 1.0 of the Podcasts app on older hardware.) In passing, however, he also mentions that Street View is coming to the mobile website in a couple of weeks. Street View is a big part of my own Google Maps usage; if it is for you as well, you’ll welcome that news. (The desktop web version requires Flash, so has not been available to mobile devices.)
The competition has been having fun at Apple’s expense, except that Motorola’s ad gave iOS a nonexistent address to get lost with.
Update: Apple CEO Tim Cook’s statement.
First, how to report a problem in iOS 6 maps: MacRumors, Macworld. Jamie Ryan reports that reported errors are being corrected quickly.
More information about Google Maps’s removal from iOS 6, and whether it will return with a Google-built app. Eric Schmidt said Monday that, contrary to rumours, Google hadn’t submitted an app yet, and things got muddled from there. The Verge and the New York Times’s Bits Blog reported last night that there was still a year left on Apple’s contract with Google, and that Google was caught flatfooted by the move and is scrambling to build its own map. They are building one, though. It’s just a matter of when we’ll see it.
One place where Apple’s maps are demonstrably better than Google’s is China, where Apple was able to draw upon maps from a Chinese company. The drawback is that the maps aren’t integrated with those in the rest of the world. Anthony Drendel, AppleInsider, Wall Street Journal.
TUAW argues that Apple dumped Google because it wasn’t allowed to do turn-by-turn navigation with Google Maps. Engadget’s Brad Hill believes that the switch was “shrewd, inevitable and an indicator that Apple understands the true battle it wages.” See also AppleInsider’s detailed multipage review.