Nah. I don't agree with the premise of this article. This was not one person's decision. Many actors had to be involved in the decision making process. For some reason Apple decided that kicking Google off the platform was worth the abuse they'd have to endure with Maps.
Those who keep saying "Maps is great" need to leave an egocentric view and realize that there are millions of users all around the world with different experiences.
According to the apology letter they serve about 500 million searches in one week. That means two billion searches per month. What does this mean in therms of customer experience?
According to this either 60% of the locations either incorrect or missing altogether. I'll be generous and propose that Maps, world-wide, might have an average of 5% incorrect or missing locations. I don't know if this is too low or too high. It's just a number that I pulled out of my imagination in order to get a sense of proportion.
If only 5% of the data is wrong and we have two billion searches per month, that means 100 million bad searches per month. I'll let the reader guess as to how many users that affects. It certainly is in the millions.
If data errors are larger than that the situation is far worst. Again, I'll leave it up to the reader to guess as to how much user anger would trigger Apple to post an apology letter on the front page of their site.
If you live here in California, and, in particular, the Bay Area, please refrain from posting how "Maps is great and it is beautiful". You do not represent the experience of the vast majority of users who had almost no issues whatsoever with Google Maps.
Oh, yes, on the whole "Maps is beautiful" mantra. Who the f* cares? 3D view? Who the f* cares? First make them dead accurate, then add eye candy if it makes sense. Accuracy is far more important than bling when it comes to maps. Nobody is going to want to use a beautiful map that takes you to the wrong place. And 3D view. Really? Get it right first. Then play.
Those who keep saying "Maps is great" need to leave an egocentric view and realize that there are millions of users all around the world with different experiences.
I have a theory about these people -- they are the ones who never realized that you could search Maps for place names.
If you search for street addresses, both Maps implementations perform OK. But the strength of Google's database is that you can type almost anything within reason into the Maps search box and get where you want to go. For my first few weeks of iPhone usage, whenever I wanted to find a nearby "Starbucks" or "Barnes and Noble" or $name_of_local_restaurant, I'd do the search in Safari, pick a likely result, and then click on the page's address link, assuming there was one, in order to open it in Maps. Eventually I realized that I could type the search string directly into Maps, and that made life a lot easier. If that stopped working or became less effective on the iPhone that I use for navigation in the car, I would scream bloody murder.
So my guess is that the people who aren't complaining about Apple's maps application are either living in metro areas that were carefully vetted by the data provider, searching for street addresses directly, or both.
I'm not trying to apologize for Apple's mess -- and it is a mess -- but your theory doesn't hold for me.
Some places are genuinely fine: I'm in San Francisco and the maps really are pretty damn good (in SF, I'll actually use the word good). Of course, this is right in Apple's back yard, but the reports seem to indicate that most major U.S. cities are in good shape (mind you, I'm talking about maps & places, not flyover's 3D views, which are a whole different story). And, I legitimately find the link to Yelp's reviews more useful than Google's place markings, but Google's are more consistently available.
Not to say that this isn't a huge mess, but simply that there are places where "Maps is good" ("Maps is great" is a bit much no matter where you are!).
I don't have an iPhone, but isn't the new maps missing public transit data? Does that mean it won't route me through subways, etc, or doesn't even show bus stops and subway stations? And what about bike paths, Google has fantastic labeling of bike routes. As a city dweller, it's good to know they are "accurate", but, from what I've heard, they are missing many key components that would actually help tons in a city. Not trolling here, just asking if maps has that info, and to what degree. Cuz if that is missing from city data, that to me is just as bad as inaccurate maps for a flyover state.
Bus stops and subway stations show up, but you need to launch a third-party app to navigate through them. And some of the third-party apps designated to do this don't work very well.
In New York, the situation is fairly dire. Before, subway stops showed up on the map with the names of the subway lines so you could see that the nearest stop to you was an "R" or a "4/6" or whatever; now that information does not appear on the map at all.
If you use the map and ask for transit directions, that used to just work. Now you get presented with a list of apps it can launch for this purpose, but some of them are terrible and the ratings don't reflect this - you just have to try them at random and see. For instance, there's an app called "Transit" which tells you which stations you want to go between but it doesn't give the names of the subway lines so you don't know which platform to stand on to get the right train. Meanwhile, one of the very best apps for doing New York subway navigation and planning - KICKMap - doesn't even show up as one of the available options from Maps.
In a word, "no." There are 3rd-party add-ons available from the App Store, but those only cover a subset of cities. Also, there don't seem to be routing plugins that can find transit directions across multiple transit agencies the way Google Maps can. So, for example, if you wanted to go from San Diego to Los Angeles, Apple maps couldn't tell you which buses to take on each end of the Amtrak ride.
(Though I had less luck with Hong Kong. For instance, a search for "Big Buddha, Lantau Island, Hong Kong" and every likely English variant just finds the middle of Lantau Island, not the Buddha itself.)
During the beta period it was pretty terrible. Place names that I could see on the map would not show up in search, either as chinese or pinyin. It was better by the time GM was released, though.
Another example: in Saigon, the Mekong was not rendering as water. Imagine being in Manhattan and having big blank yellow spaces where the East and Hudson rivers should be.
I can't imagine that the decision to drop Google early was made by the executive committee without getting a sign-off from Forstall that they would be ready with a new Maps app.
The ordering in making that fateful Google decision must have been first to decide if their own alternative was going to be close to ready. At that point somebody aggregated the data from the Maps team and made a forecast that said they would be.
Further, the failure of Maps has made iOS 6 itself a failure. You can tell from the marketing materials that the new Maps application was the headline feature of iOS 6. You can reverse engineer their thinking - we are dropping Google so this new release of the OS needs something special to hold it up. That 'something special' was the 3D view.
People are forgetting that Maps was marketed as a better application than Google Maps.
So that leaves a few points where it went wrong:
a) whoever provided the input to the group that decided to drop Google in saying that they would be ready
b) whoever decided to drop Google based on that info
c) whoever was responsible for delivering the finished Maps product
d) whoever was responsible for pinning the success of iOS 6 on Maps
e) whoever was responsible for testing Maps
f) whoever was responsible for raising user expectation by marketing Maps and iOS 6 as being 'better' and 'the best'
As head of iOS and a member of the exec committee, a lot of those paths lead back to Forstall.
Everybody knows by now that the maps are no good. I think that at this point the rage and anger is about overpromising and knowingly shipping an unfinished product of insufficient quality, something Apple has never (arguably) done before.
As it says in the article, the same could be applied to Siri but Siri came with the "beta" warning label, a lot of people understand that voice recognition and that kind of pseudo-AI is really hard, and it was better than anything competitors had to offer, which, obviously, is not the case with maps.
...something Apple has never (arguably) done before.
Well, pretty much every 10.x.0 OSX release has had some nasty regressions in it, but they're generally not quite as easy to spot as the maps fiasco. What's worse is that this isn't a new product that starts off a bit crap with the view of improving it over time - there have been a few examples of these as well.
Instead, from the users' point of view, the maps update falls plainly into the "if it ain't broke, don't fix it" category. Users don't give a damn about contracts between Apple and Google. The Maps app has been there since iPhoneOS 1.0 and it's not had any drastic changes since then, despite its tremendous popularity. I find it baffling that they didn't release the new map material as an extra mode with more features (3D, turn by turn navigation), in addition to Google's map material for the classic 2D view until iOS7 comes along. That would probably have completely avoided the problem and given Apple an extra year to get their data into shape. The new features, although a little half-baked, would still have been seen as an improvement by users, whereas now they're just blinded by the seething rage of having the core functionality yanked out underneath them.
I really disagree with your views of the "ain't broke" area. For me and a lot of users it _was_ broken, because it had tiles that didn't zoom properly with a slow connection and didn't have turn by turn. Maps was falling behind, especially with the lack of turn by turn. Even my non-technical friends have been wondering when iOS would finally catch up with Android on that front.
No, but the point is that Apple needed to break away from Google at some point (note: the timeframe to breakaway is subjective). I would say that within 6 months, things will be a lot better for Apple. If they'd stayed with Google, the answer would still be "no" in 6 months.
Well off the top of my head it'd be assuming that searches were distributed randomly w.r.t bad data, whereas in all likelihood there may be some (inverse) relationship between the badness of an area and its search popularity. In general living outside the US I was happy with the gmaps solution generally, apple maps had some glaring errors in my neck of the woods on launch.
Oh, please! There's no way to get the data required to do any real statistics work on this. Not without doing a hell of a lot more work than is worth for an HN post.
My simplistic 5% = 100 million calc serves to simply highlight that small numbers can mean huge problems. Even if I am off by an order of magnitude this is still a huge number of searches per month that are potentially sending people to entirely the wrong place, if at all.
You are assuming that both the bad map data and the searches are evenly distributed across all locations. If their data are good in the most-searched areas, the number of users affected is much smaller.
The list goes on across the net. I support several other posters in that only an Apple fan would say that the maps are good overall. All you will hear from these people is how TomTom had a bad map 5 years ago, or how Garmin is missing a 3 year old suburb in their area. The fact is that in this instance, Apple stuffed up severely.
It was a brave decision of Apple to go ahead with this version of maps - they would have known full well just how bad it was. Maybe it's the kick in the butt that Apple needed to catch up quickly. I expect that within 6 months, the situation will be a lot better for Apple.
"Nah. I don't agree with the premise of this article. This was not one person's decision." Except in any corporation there is always one person who says "Ship it" and it does - regardless of anyone else's point of view. Was that Forstall? Most likely.
I really don't get the "Maps are great for me" apologists either. It reads like "Typhoon in Japan? Looked outside, weather is great here."
I'm sure TomTom and Apple cleaned up the data for areas where their programmers and bosses live. Even in Seattle, I searched for "Pizza" and it didn't find the place down the street [I had to search for "Pizzareia" for it to show up].
When you see reports of major airports being missing or mislocated, you can't use the "Well my local airport shows up fine" defense. It's like an inverse Tu Quoque fallacy [you hit a problem, I didn't, therefore the problem isn't there].
> According to this either 60% of the locations either incorrect or missing altogether.
According to a followup article ( http://vore.cc/post/32503374905/old-maps-vs-new-maps ) the old Maps app fails this exact test at least as badly. It just fails a bit differently. Whereas the new Maps app often says it can't find anything, the old one would for a similarly sized group of searches silently err on the side of finding a match that was wrong.
It only failed when he left out the country name from the search. Once he added the country name the new map barely changed, but the new one got dramatically better.
The problem is very simple: The same city name shows in in multiple countries and the old map just didn't know which one he wanted.
> Inside Apple, tension has brewed for years over the [skeuomorphism] issue. Apple iOS SVP Scott Forstall is said to push for skeuomorphic design, while industrial designer Jony Ive and other Apple higher-ups are said to oppose the direction. "You could tell who did the product based on how much glitz was in the UI," says one source intimately familiar with Apple’s design process.
Very interesting. Of course, Steve Jobs was also in favor of skeuomorphic design, so it's not like Forstall is the sole reason I "find my friends" in stitched leather.
That's not skeumorphism; it's a style choice. If I had to simulate ripping the top piece of paper off the notepad in notes to clear it, then that would be skeumorphic design.
Can we just make this the auto-reply comment whenever someone mentions skeuomorphism on the internet? I couldn't be more sick of the concept, except when I hear it constantly being used incorrectly.
Textures and styles aren't skeuomorphism, skeuomorphism is imitating real-world objects to provide a sense of familiarity in execution. Not a notes app that looks like a notepad, a notes app that FUNCTIONS like a notepad.
I think you two are wrong. Skeumorphism is about ornamental design, about design features that imitate something that was once necessary but is no more.
It’s consequently all about style, not about function (at least when it comes to real-world objects). Wikipedia has examples like flame shaped lightbulbs, artificial film grain or spoke patterns on hubcaps.
It seems that when it comes to software, skeumorphism can also refer to functional adoptions of virtual interfaces to their real-world counterparts†, but I think it would be misguided to exclude mere style here.
I mean, in the end this is a stupid semantic argument. Using leather textures is what it is, whether it’s skeumorphism or just style, but you two certainly do not have the facts on your side.
—
† It’s pretty clear why that is the case: it’s only possible to make lightbulbs look like flames, not to make them work like flames. Software provides more freedom and makes it possible to make something virtual work like the real thing.
If we're going by the wikipedia page, here's their definition they provide:
"skeuomorphism is when a product imitates design elements /functionally necessary/ in the original product design, but that becomes ornamental in the new product design."
So yes, it is about function.
And also, the three things you mention are directly related to the function of the original objects. While these things are clearly used ornamentally in modern devices, their existence/use was inherent in the design of the modern devices' predecessors.
I think you misunderstood me. While it can be purely stylistic in the modern interpretation, the element replicated must have some functional purpose in the original. I do not think that you have to reimplement the functionality, that was just the example I used.
Your examples are skeumorphic because they use functional aspects of the original. "Find My Friends" is not skeumorphic because even if such a thing as "Find My Friends" existed in a previous form, the leather has nothing to do with its function.
If that sounds confusing to you, then I don't know what else to say. You're wrong?
Almost all aspects of a physical object are "functional", so this is a strange distinction to make.
For example, the rich Corinthian leather of a desk calendar functions as an arm rest and also functions as a binding mechanism for the calendar pages within. The stitching of said leather functions to hold the piece together.
The point is that you do not need rich Corinthian leather to make a desk calendar; in fact the vast majority of desk calendars in the world do not have any leather on them at all. Even on the real-world object, the choice to use leather serves a decorative purpose--it is not a functional necessity. Yet I've never heard someone call a leather desk calendar "skeuomorphic."
But is it necessary? That's an important part of the definition. For instance, the wood on Newsstand doesn't make it skeumorphic, but the bookshelf design does.
And again, where is the original product design for Find My Friends? Why did I never hear about anyone using a leather-bound location diviner before?
You're overly restricting the definition of skeuomorphism, or perhaps confusing it entirely with anachronism. Wikipedia's definition of skeuomorphism is a design element that is retained as an ornamental imitation of a formerly functional counterpart. When a notepad app wastes screen space on drawing non-functional spiral binding, that's definitely skeuomorphism.
You're right, that is skeumorphic. And many other things Apple does are too.
However, that doesn't mean every thing -- like the leather stitching in "find my friends" -- that Apple does involving natural textures is skeumorphic.
Stranger still, it is said that the stitched leather theme was modeled after the upholstery in Jobs' Gulfstream jet! [0] Both iCal on OS X and Find My Friends on iOS have the same motif.
“But before Forstall, it was Steve Jobs who encouraged the skeuomorphic approach, some say. “iCal’s leather-stitching was literally based on a texture in his Gulfstream jet,” says the former senior UI designer. “There was lots of internal email among UI designers at Apple saying this was just embarrassing, just terrible.”
Forstall has been called "Apple's chief asshole"[0] - he channels Steve Jobs's approach of being a douchebag, but doesn't seem to have acquired the same level of perfectionism as Jobs.
He also gives me that impression when I see him on Keynotes, one of a power grabbing, back-stabbing kind of guy. Which could or could not be true, I'm talking purely from a "face-reading" standpoint.
The exact opposite of that would be Bob Mansfield.
I've seen each VP (except Mansfield) talk in person and I have gotten a very different impression of Forstall. He was one of the most impressive VPs in my eyes (he talked a lot about his passion for bettering accessibility and making life-altering impacts with iOS).
No, Apple has a "liberal arts problem" in that they don't seem to have the hard core folks to do algorithms in the way that Google does. Apple has a lot of smart people, but can you really see them building a self driving car with tons of lasers spinning on it in order to have super accurate maps? I can't. But that's what Google did.
Its also a "device centric problem": I'm always struck when talking with someone from Apple about how device centric they are thinking (running algorithms locally that should run in the cloud, etc.). The cloud is eating the world and device centric thinking, while its done them well for a while, is increasingly incorrect.
A "a self driving car with tons of lasers spinning on it"? Learn before you speak. The noticeable problems are not subtle: clouds covering cities in the UK, buildings not being named on College Campus, etc. Stadia 0.5km out of place. They are obvious, silly, dealbreaker problems for Soccer Moms and Sociology FFS. Algo's are not going to solve this cr@p, its Cartpgraphy 101...and in any event, Google has to hand fit the data that they do have, for a variety of reasons, to sat-nav visuals (including incosistent basemaps).
Totally agree. I know, from many sources that a lot of human labor goes into making the Google data so good. They used to give out cookies to employees who would filter search results as porn/not porn. Algos can only get you so far.
If the cloud is eating the world, why did Google buy a mobile OS company and then a mobile device company? If Apple is too device-centric, why does Siri send every query to their data center instead of processing it on the phone?
In short, I don't think you've thought deeply about what you're writing.
It's had a similar number of issues, as compared to Maps. The difference is, it didn't replace or introduce a must-have feature in iOS. As a result, it's failures were something users are able to overlook because Siri is still, essentially, a toy feature. It's not key to the phone's operation; heck it's non-obvious that it's even a feature because no where on the interface indicates that it exists (it's a hidden long-press action on the home button).
Maps, however, is crucial to most people that use an iPhone. After telephony and web functions, it's probably the next most used feature. So, any failure by it, even if it's slight, is amplified. Yes, you can use Google Maps on the web or another app (MapQuest should really be capitalizing on this opportunity to reclaim some relevance), but it's one of the default icons on the home screen and where most people are going to head first. It would be like the dialer not being able to call certain phone numbers or the text message not working with certain recipients. It's a vital function and has to work.
I would say Siri is probably more of a failure than Maps, but because of it's non-essential nature, that feature is able to get away with what Maps can't.
How do you know that nobody you know uses Google maps? I'm assuming you know at least a few people who own smartphones and who you do not often travel with; have you asked them whether they use Google maps?
FWIW, the first thing I did when I first bought an iPhone was move Maps onto the taskbar - replacing Mail - since I used Maps more than any other phone feature.
Interesting. I was thinking the same thing. Everytime I decide to depend on ios4 maps (pre-debacle) for active usage (while driving), I end up getting lost because it was horribly offcourse. Other than offline direction search, I learnt not to depend on it. So technically, other than the Schadenfreude, I dont really have a lot of problem with ios6 maps since I can fireup maps.google.com for maps/directions
Does it work for you? I stil have to meet a single person which actually can ask Siri something and Siri understands it and gives reasonable answer... I was under impression that it did not work because I'm ESL speaker: but it also does not work for people who speak english very well.
Siri works fabulously for me. Here's how I use it, these use cases work consistently.
1. Call my wife at her office.
2. Text My Wife - I'll be home in 15 minutes.
3. Set a timer for 15 minutes.
4. Where's the closest Mc Donalds.
Obviously I'm not looking for a magic speaking encyclopedia of knowledge, that being said my primary use case for Siri is in the car, and for 90% of what I need to do it works fine.
BTW I just asked Siri "What is a class action" and it asked me if I wanted to search the web for "What is a class action" and it found the definition. I'll give it this though, whether automated or manually Siri's been pretty consistently tuned to get better and better as its gone along which was likely to happen as it got a larger and larger dataset to work with.
Yep, works nicely for me too. Definitely a net positive in functionality on the phone, even if it's limited and not entirely reliable. Text messaging can be MUCH faster with it, especially if my hands are busy.
It's no AI and you'll have trouble if you treat it as such, but if you think of it as list of occasionally useful things that it can do, then it's pretty handy.
I am German and we didn't get all Siri features before iOS 6 (wolfram Alpha is still missing). But I tried it more in the last days and am really impressed! Even when I thought "oh, I mumbled the word, Siri won't get it" it was correctly recognized. I most use it as text to speech for SMS. And checking Fußball Bundesliga works good. (But only first league, no info available for second league.)
Since iOS 6 (or at east I never noticed before?) there is also an info button on the Siri screen which shows example querys/commands. This hels a lot!
I'm from germany too - I mentioned this before, but did you notice that you can't speak to Siri in english at all when its set to german? This is problematic when telling Siri to play music by any artist whose name, band or album is pronounced in english - a native german name would work though.
This, I guess, would apply to every non-english country and seems like a quite an oversight rendering music controls via Siri useless. Since english words and expressions became natural parts of every language, and are also pretty common in artist, movies, brands, places, etc, Siri should always check back with its english dictionary regardless of language settings.
The biggest issue with Siri was the same as with the current Maps blunder, where it works well for US users, but causes issues for everyone else.
There are some videos of non-native English speakers trying to use Siri on their new 4s (before additional languages were added), which are quite funny actually.
The same goes for the new Maps, which seems to have most of its issues related to countries outside the US.
But especially with iOS6, it's actually the first time for me personally where I feel like I'm downgrading my device instead of upgrading it: youtube app - gone, maps - replaced with inferior alternative, ...
Might not be so much about functionality as that it was down an awful lot when it was launched. To the point where several people I know gave up relying on it - a feature that works less than 95% of the time quickly becomes 0% useful because the small fraction of failures is so frustrating and annoying that you avoid the whole thing (until recently this problem applied to speech recognition in general, but it's just finally getting over that hump, I think).
It sounds more like they have a services/big data problem, + maybe a Windows XP-like "good enough" problem (leading to new features and changes being viewed more skeptically)
I don't understand why someone needs to be fired just because they had one or two bad products. Why would you throw away the rest of the knowledge that this person has? Demote them, put them on new projects, place them where they are stronger and have them work on another project, but outright removing someone seems like it is throwing the baby out with the bathwater.
Makes sense to some extent at a company like apple. Maybe you get two chances but if you don't have the foresight to see how important maps are to people you might not be the best fit for the job.
Fresh perspectives matter sometimes in product's lifecycle. Working on same stuff for years you run a high chance of developing tunnel vision. If there is a new but capable person with different vision, there is a good chance something new and appealing might come of it.
Case in point - Steven Sinofsky and Windows 7.
I dont know what other project they can put someone like Scott Forstall on without even indirectly becoming related to OS development at Apple.
Why people don't seem to get this is beyond me. Releasing Siri and Maps early were purely strategic decisions. Clearly both Siri and Maps can be improved more rapidly if some of the development is crowdsourced. Apple would believe (and rightly so) that the brand has enough excess credibility/goodwill with the public to ride this out.
Google has done this repeatedly with products like GOOG-411, a data collection exercise that was promptly shut down once it had served its purpose. Apple is taking a risk here because Maps is not some 'free' offering like GOOG-411, but they've done the math and will come out ahead when the dust settles.
Who at Fortune deserves to be fired for its recent long string of incredibly idiotic articles about Apple, which have been panned here and elsewhere, then?
I think the new Maps app is fantastic; the data accuracy leaves a bit to be desired, but I notice that those doing the most high-profile complaining point to errors in rural England, rural Ontario, etc. Here in the Bay Area, the data is working fine for me as well.
It is not shocking to me that a map database that is a few months old is less mature than one like Google's, which is the product of a decade's effort, and also the product of 5 years' worth of improvements riding the back of iOS users' crowd-sourced data. Now Apple has that data coming into its database, instead of flying out the door to Google's.
Maps is likely to improve, and fast.
In any case, blaming Forstall is idiotic and talking about firing him is Fortune-level idiotic. He made great things at NeXT, Mac OS X is great, Siri is great, and Maps is a work in progress that shows great promise.
Have you tried reloading map data and zooming in and out on maps in Google Maps vs. Apple Maps in an area with EDGE or otherwise bad internet coverage? Apple's app wins hands-down versus reloading non-vector map tiles.
Newsflash: A lot of people live in rural England, rural Ontario and Rural Holland. Besides, it can't find places like central station in Amsterdam (hardly rural). I don't care whether it's the app or the data, I don't care that it's working great in the bay area. What I do care about is that I had a perfectly working mapping solution, and now I have a second class thing that's just not working. I don't know about you, but IMHO having wrong directions is even worse than having no directions.
"Antennagate" wasn't a big deal? When my wife used her iPhone 4 it would drop calls constantly (pretty decent AT&T coverage, Columbus, Ohio). She even had it replaced due to the issue (which wasn't fixed until she put a case on it).
Ah, I see that too. Clearly problematic since there doesn't seem to be a way at all to load up the intended 428 University Ave address. No good.
Still though, "really really bad" makes me think you have experienced many other issues. I'm genuinely curious about how Maps performs in the places it is "supposed" to be at least passable. Got any other examples?
Meta: please don't edit your comments to respond to sub-comments. It makes the flow of the conversation very difficult to follow and makes my previous comment seem irrelevant and out of place.
Both David Pogue and Anil Dash have written about getting driving directions that takes them to the wrong location in places like New York city.
I'm just one user, but if a navigation app takes you the right address in the wrong location in a place like the Bay area or NYC, that's a "really bad" problem.
Not in my experience. It's fine here, at least in the city and in Berkeley. No problems aside from a few addresses needing me to add "sf" to them to avoid having them go to different cities (which sometimes also occurred with Google's map data).
I'm working on a routing/location based app right now. Out of curiosity could you give examples of what you mean by "really bad"?
True, and I granted that point already. However, a lot of people live in China, too, and it's being widely reported that Apple Maps is much better than Google Maps' data, in China. I'll just give one link, but a little googling around proves the point quite well:
You didn't have a perfectly working solution before, btw; Google Maps still has a lot of errors.
And what you have now is both Google Maps (via Safari), and also a new Maps app that is internally superior and relies on a less-mature dataset which will mature quickly and give Google some much-needed motivation to improve its data as well. I'm not sure why this is such a big disaster.
Edit: By the way, Apple Maps finds Amsterdam Centraal (not "Central") Station just fine, if you spell it correctly. I just checked; it finds the exact same place as Google Maps.
Defending the maps app as "a few months old" does not excuse the fact that it is not as good as the app it replaced. I'm sure it will improve in the future and may lead to improvements in all map apps as a result of increased competition.
I didn't defend the maps app in that way; I was defending the immaturity of the map data.
The app, as I said, is superior in my opinion to the Google Maps app. It zooms better, loads faster, looks better, has better layout, is prettier, and has turn-by-turn directions and 3D features that were absent in the Google Maps app. Remember that the app and its functionality is completely separate from the database it points to. None of the map data is stored in the app.
In a, probably unintended, way, I believe you've nailed the nail on its head: Apple excels at making aesthetic beautiful stuff, which looks good and feels good. But maps are about details and accuracy, otherwise they're useless.
This is going to be the real test for Apple. They need to fix stuff, they know that, it will be interesting to see when improvements will be noticible.
Cook spoke of 500 million searches in two weeks. If only 1 promille triggered a feedback or "report problem", that would be 500.000 change requests. How can you brute-force this massive amount of data?
A quick Google search will tell you that there are non-trivial problems all over the world in major cities at major landmarks with Apple maps.
It's nice that you agree with the parent poster that Apple Maps are fantastic, but let me say that I don't think so. There are far too many obvious and MAJOR cockups (eg. Hong Kong is misplaced - it's not even on the island, Tokyo's main railway is missing, etc.) ... but you think that's Fantastic??
I will point you to Garmin and TomTom as two examples of maps that FAR exceed Apple's "fantastic" offering.
In 6 months time, the landscape will (hopefully) be different ... but to call this offering fantastic is ignorant.
Maps are an interesting area for bikeshedding to occur, because any two people can both be experts in their area yet both experience wildly different results.
I've got a question on the maps fiasco, is it possible that Google never shared any usage data with Apple and somehow Apple thought nobody really used the App all that much? Seems like the click/search stream in maps is a tremendous asset for a number of reasons, not the least of which is that it comes with a unique undisguisable identifier with each request. Where you go an when you go there, both part of the query when you use maps. Its an advertiser's wet dream I would think.
Perhaps Scott realized that and decided to take it back from Google? I don't know. I do know it is pointless to try to second guess the executive staff of a company like Apple (or Google, or Groupon, or Zynga, Etc) even though it is fun.
I think you'd have to be a fool to think Apple didn't see this coming, but in reality it a big deal for Apple, but not an earth shattering one. To truly improve things like Siri and Maps, you need real world data, user feedback, etc.
I'm sure they are keenly aware of the shortfalls of their own software, as much as they are of the hardware they make. That's the whole point of QA. What pushing out products early does is let you start getting feedback on the known unknowns - problems you'd expect to have but didn't know exactly where they might be, and the unknown unknowns - problems you didn't see coming at all.
Almost all of the gripes people have with Apple Internet services and software involve Cue's products, not Forstall's. But because Cue doesn't have any interest in the top job, and because of his seniority, he ducks blame every time.
As much as I dislike Forstall--particularly the way he presents--I don't think we can lay this all at his feet. You can bet that even Steve had a hand in this decision.
The whole flow was amazing.
1. Acquire external talent
2. Fire google
3. Tell the press that the new map gonna be amazing
4. Apologize for the whole mess
5. Sell 3rd party map on the app store
6. Profit
Another way to look at the accumulation of power during Jobs absence is other members of the executive team stepping up to the plate while another is absent...
Those who keep saying "Maps is great" need to leave an egocentric view and realize that there are millions of users all around the world with different experiences.
According to the apology letter they serve about 500 million searches in one week. That means two billion searches per month. What does this mean in therms of customer experience?
http://www.mtonic.com/applemaps/
According to this either 60% of the locations either incorrect or missing altogether. I'll be generous and propose that Maps, world-wide, might have an average of 5% incorrect or missing locations. I don't know if this is too low or too high. It's just a number that I pulled out of my imagination in order to get a sense of proportion.
If only 5% of the data is wrong and we have two billion searches per month, that means 100 million bad searches per month. I'll let the reader guess as to how many users that affects. It certainly is in the millions.
If data errors are larger than that the situation is far worst. Again, I'll leave it up to the reader to guess as to how much user anger would trigger Apple to post an apology letter on the front page of their site.
If you live here in California, and, in particular, the Bay Area, please refrain from posting how "Maps is great and it is beautiful". You do not represent the experience of the vast majority of users who had almost no issues whatsoever with Google Maps.
Oh, yes, on the whole "Maps is beautiful" mantra. Who the f* cares? 3D view? Who the f* cares? First make them dead accurate, then add eye candy if it makes sense. Accuracy is far more important than bling when it comes to maps. Nobody is going to want to use a beautiful map that takes you to the wrong place. And 3D view. Really? Get it right first. Then play.