Recent reports claim that Apple ended its iOS mobile maps contract with Google a year early. But the result, Apple's home-brewed Maps app, has left many users wishing the two companies had stayed on good terms.
Sure, Maps comes with new features that weren't available on the Google-made version for iOS, such as spoken navigation directions and 3D views of cities. But Apple's new Maps app has become infamous for its quirks (misnaming cities and countries, moving famous landmarks, distorting landmasses and manmade structures in 3D mode) and its lack of integrated public transit directions.
Some have called Maps "appalling" and a "huge step backward;" others have been less harsh and have labeled the app "a decent effort for a first pass."
Why would Apple do something like this? To answer this question, we've combed the wisdom of some of the web's top Apple watchers. Flip though our gallery (below) to view opinions from the New York Times, AllThingsD, Daring Fireball, Slate and The Verge. Then, read on to view our gallery of the worst fails spotted in Apple's Maps app.
What do you think of Apple Maps? Has it made you late or gotten you lost? Do you have horror stories to share? Or rave reviews? Let us know: email us at email@example.com or tweet @HuffPostTech.
Chris Ziegler of The Verge recently reported that Apple pulled out of its contract with Google over a year early, which would explain why Google didn't have a standalone maps app ready to go when iOS 6 launched without Google Maps. Ziegler posits that Google Maps for Android had advanced too far ahead of the iOS version of Google Maps -- and Apple
AllThingsD's John Paczkowski points to Google's unwillingness to share its spoken turn-by-turn navigation data as the source of the eventual break between Google and Apple on maps in iOS.
Well-sourced Apple enthusiast John Gruber speculates that Apple may have given itself the upper hand by terminating is partnership with Google a year early (instead of waiting until mid-2013 for it to expire). "Apple wasn’t going to wait to negotiate until their backs were to the wall with the currently-shipping version of iOS reliant on Google Maps when the old deal expired," Gruber argues. It was in Apple's best interest, he writes, to release its own Maps app with a major iOS release, rather than waiting for the Google contract to expire while a new iOS release was still being prepped.
Sure, Apple's Maps are being lampooned across the web; but at least Apple got what it wanted when it wanted it. Right? ...Right?
Slate's Matthew Yglesias argues that Apple dropped Google Maps in the hopes that Apple could one day offer a superior (and native) mapping service in iOS. For now, Apple is relying on its brand power to carry it through the rocky launch of its sub-par Maps app. With a little bit of luck, the company's loyal customer base will stick around long enough until Apple improves ist Maps.
"[W]hat they [Apple] achieve by ending the relationship [with Google] early is a chance to some day—hopefully soon—have the very best maps experience in the world," writes Yglesias. "Under iOS 5 they didn't have that, and as long as Apple depended on Google they were never going to have it."
Although critics and users have panned the glitches in Maps' interactive Flyover feature, the 3D bird's-eye view option has also been called "stunning" and "lovely" (when it works properly). The New York Times suggests that, although Google has a years-long head start on mapping applications, the company has a lot of work to do before it can offer a 3D mapping option similar to what's available on Apple's mobile Maps app.
From the Times: "Google has 3-D images in Google Earth, which is a separate app with a separate code base from Google Maps, so it would take some time to combine the two."
It seems that Google's facing a steep, rocky road as it rolls toward it release of its Google Maps iOS app, which the Times predicts will be ready at he end of 2012.
What Makes Google’s Maps So Good
Nobody ever raved about Google’s mapping app for phones until they saw how hard it was for Apple to come up with a rival. In my Times column today, I wrote about the challenges Apple has faced in replacing its iPhone GPS/mapping app, substituting its own data sources for Google’s. I noted that the new app is beautiful and will be really terrific someday — once it does a better job of incorporating all of its various data sources.
The Times’s technology columnist, David Pogue, keeps you on top of the industry in his free, weekly e-mail newsletter.
In researching the story, I interviewed representatives from Apple and Google. At Google, I spoke with Manik Gupta, senior product manager for Google Maps, and Daniel Graf, director of Google Maps for Mobile.
What I realized is that mapping the world is a staggering, gigantic, vast, inconceivably huge and ambitious project. It represents years and years of hand-tuning and manual effort.
I was surprised to learn that, like Apple, Google began its efforts by licensing petabytes of data from outside geodata companies.
They include TomTom, the same company that Apple’s using. (The other big map vendor is NavTeq, which Nokia bought a few years ago; I guess that explains why Apple and Google aren’t using NavTeq’s data. Too bad — by all accounts, the map app on Nokia’s Windows Phone is pretty great; I’ll be trying it out shortly.)
But that’s just the basic data. “We start with licensed stuff, then expand and enhance it,” Mr. Gupta said. Google has supplemented it with years of additional data gathering, involving its Street View cars, satellite data and human labor.
And it shows. As of 2008, for example, onto those digital maps of the world Google had overlaid 13 million miles of turn-by-turn directions in 22 countries; today, it has 26 million miles of guidance in 187 countries.
“It’s fair to say that in the mapping world, you can’t just throw money at it and then you have it the next day. This takes time,” Mr. Gupta said. “It took a lot of time to get where we’re at.” He said that even now, Google is far from done; error reports still flow in by the thousands.
Many of them come from Google Map Maker, a Web site that is live in 200 countries (and just started in the United States) that lets average citizens make corrections to Google’s maps as they find them. You can, for example, draw a line to represent a new road.
Like Apple, Google also collects location and movement data (anonymously) from millions of smartphones as they’re driven around; from this information, Apple and Google can determine when, for example, a one-way street has been mislabeled in its data.
You may be familiar with Street View, a Google exclusive that lets you stand at a certain spot on the map and “look around.” You can see a photo of the address you seek, and use your mouse to turn right or left and actually move through the still photos. It’s an amazing way to see what it’s like to be at that spot.
Street View isn’t available for the entire world, but you’d be surprised at how many inhabited areas are covered: Google’s GPS- and camera-equipped Street View cars have, so far, driven five million miles through 3,000 cities in 40 countries.
What you may not realize, however, is that those photos are far more than just helpful references for you, the viewer. Google’s software analyzes what’s in those photos. Its image-recognition software can read the text on street signs, storefront signs, hotel names and so on. It can tell a major road from a minor one, a single-lane road from multilane and one-way streets from two-way streets. Street View, in other words, generates still more useful data for Google’s maps.
I asked Google why its satellite photos don’t seem to display the same jarring seams that are showing up on Apple’s — obvious borders between side-by-side tiles that were taken at different times of the year or in different weather.
“When you look at Google Earth,” I was told, “you can see that the globe is made from a mosaic of aerial and satellite photos, often taken in different lighting and weather. We license these photos from multiple providers, possibly the same ones that Apple uses; but we’ve had the time to come up with a smoothing algorithm. In January, we introduced a new way to render them, smooth them out, make them seamless. But by no means have we perfected this.”
On this call, Google pointed out a new feature that I hadn’t seen before: compass mode. On an Android phone, you can call up a location like Trafalgar Square in London. You hold the phone in front of you to see a Street View-like photo of the scene — and as you look left, right, up, down, or behind you, the view changes, as though you’re looking through a magic window at another place in the world. You can even use Compass mode to look around inside places — I tried Delfina, the San Francisco restaurant — to get a feel of the décor before you go there.
Can you imagine how powerful Compass mode will be once it covers most of the earth’s developed areas? It will give you a sort of instant teleportation, a way to travel without travel, a sense of a place without having to go there.
What I’ve learned from this deep dive into the making of map apps is that you can’t just license a bunch of data, bake at 350 degrees and come up with a useful tool. Gathering the data is only the starting point; from there, it takes years to reconcile it, correct it and make it useful. (This Atlantic article offers a good look at the kind of hand-tuning that Google’s minions do constantly.)
By the way, let me be clear: I have no doubt that Apple’s Maps app will get there. We’ve seen this movie before — remember MobileMe? It, too, was very rough when it made its debut. Today, its successor, iCloud, is smooth and sensationally useful. Maps will be, too.
But I suspect that Apple has just realized the same thing I have: that we may live on a small blue planet, but digitally representing every road, building and point of interest is a task of almost unimaginable difficulty. Let’s be grateful that another major player has just joined the attempt.