Hacker News new | comments | show | ask | jobs | submit login
The Amazing iOS 6 Maps (theamazingios6maps.tumblr.com)
837 points by Maakuth on Sept 20, 2012 | hide | past | web | favorite | 371 comments



I look at this and can't believe Apple wanted to ship with this. And I mean that literally, not incredulously. I believe Apple wants to be in carol of its mapping future, but this product isn't ready yet, and I don't think Apple is so delusional to not be able to see that.

So that makes me wonder what happened in contract negotiations with Google to force it out. Did Google flat-out say "No"? Seems unlikely. Was it just too expensive? That's possible, especially if these negotiations happened during the time Google massively raised the prices on its API (completely random speculation: maybe the price increase was only about Apple), so Apple had to invest elsewhere. Did Google just want control of their map data or want to give Android a massive competitive edge so they backed out? That seems unlikely, but may be answered if Google doesn't put out a map app for iOS.


You are probably correct. However if you look at Google's moves in the maps API with respect to charging money the simplest explanation is that Apple and Google could not come to terms on the price for access and so Apple went with 'plan B'.

Given the pain Apple is causing Google in its patent assault I don't doubt for a minute that the senior management at Google would have any regrets about 'losing' the Apple map business vs 'gaining' a poorly executed maps product on their premier devices.

I also don't expect Apple to approve any Google "maps" application any time soon either given how strategic it is for their mobile business.

My best guess is that Apple did the math and said "Well its going to suck rocks but we have to dominate this space, this moves our time table up but doesn't change what we need to do, ship what you have and put your best team on making it excellent."

EDIT: Reminds me of Intel's response to AMD's multi-core where Intel literally glued two separate CPU chips into the same package and shipped it as a 'multi-core' CPU. That sucked too but they had an answer in the market, and they invested in making that answer competitive over the next 3 years to get a more real multi-core out the door.

[1] http://en.wikipedia.org/wiki/Pentium_D


> I also don't expect Apple to approve any Google "maps" application any time soon either given how strategic it is for their mobile business.

Soooo, their users don't matter? "Business strategy" is more important?

This is Apple?!


Yes, this is Apple.

See: The In-App Purchase controversy with eBooks and other applications. For example, did demanding the removal of all links to Amazon.com from the Kindle app (because Amazon didn't want to hand their eBook margin to Apple by using Apple's IAP API) make anyone other than Apple better off?


You know, I'm starting to miss Steve Jobs. He was a businessman as well, but he also knew how to treat his customers right, because keeping the customers in the hype is extremely important in his high-benefits scheme. I don't think he would have let that kind of stuff happen. He would have paid the price: it's not like Apple can't afford Google Maps for another version of two of the iPhone, and now some customers are considering switching. If they get out of the walled garden that turns into a prison, they might not come back.


Not so sure about that. I tend to think he would have been less likely to put this new maps out though. Perhaps paid Google for a bit longer until the Apple maps were real competition.


Yeah, the question is if Apple still got the feeling that the hype should result into pleasure in post-launch.


It also reminded me of Apple cutting off Internet Explorer for Mac[1] and went with building Safari. See how that worked out for them (and all devices relying on WebKit).

[1] http://en.wikipedia.org/wiki/Internet_Explorer_for_Mac


Keep in mind that Google maps are arguably the best in the world - IE for Mac was a pretty dreadful browser.


True, but Safari was based on KHTML which was being worked on for a long time and was pretty comparable(and even in some cases better) than Firefox and IE at the time. Can you say the same about iOS 6 maps and Google Maps?


Speaking as one of the people who worked on adapting khtml into Wbkit, no, it was no comparable with Mozilla or IE at the time. It took a major effort to get to shippable performance, web comparability, standards compliance, and quality. Check out the first 2 or 3 years of WebKit commits on trac.webkit.org and you will see some incredibly basic stuff.


I'm sure the TomTom deal will change things fairly soon. The agreement was signed three months ago, and by then Maps for iOS 6 was clearly already too advanced to incorporate much of what TomTom can offer. I suppose we'll see updates coming thick and fast from here to Christmas, especially considering the current wave of negativity surrounding the app.

I wouldn't be surprised if Cook decided next week that they might as well buy TomTom outright.


Apple doesn't have a history of dominating any free-to-use services so I'm doubtful that they'll invest beyond the "good enough" threshold. This feels like ReadingList to me.


We'll see [1]. Some people miss the critical bit about maps on phones.

Ask yourself, "How can Google make sooo much money on search advertising?" I mean seriously, rounded to the nearest billion they don't have any other businesses. The insight that explains it is that search advertising exploits the fact that the consumer is "looking" and they have what they are looking for "the query". When that signals a possible purchase intent "car safety reviews" for example, at that instant in time Google gives advertisers a way to put their message in front of the consumer's eyeballs when they are most receptive to that message. The effectiveness of a car dealership advertisement in a Harry Potter movie preview? Lots of eyeballs, few if any looking for a car. In a search query on cars? Lots of eyeballs, many if not most of which are looking for a car. This is what makes search advertising an insanely better advertising vehicle then pretty much any other form of advertisement.

Now lets look at maps on mobile devices. This has the same fundamental super power as search advertising, mobile maps are a search api. Many people don't put that together but when you are using your mobile device's maps you are seeking out directions, what you are looking for signals intent, and on that intent one can build a very profitable advertising platform. If I pull out my iPad and click 'coffee shops' on the maps search box I have signaled both where I am, and that I'm looking for a coffee shop. As a shop owner how much would you pay to have that person go to your shop? $0.50? $1? $2? How do you know your ad worked? Well there is an NFC payment, or a coupon you can offer up on the mobile device, or your local WiFi hotspot (remember that?) can tell you that the wifi mac address of the device that did the maps search, just walked into range of your hotspot.

Do you see it yet? Mobile Maps is as big a business as Google's search advertising business and its still un-plundered. Apple will do everything they can to 'dominate' this particular 'free to use' service.

[1] Best scene ever in "Charlie's War"


I don't disagree with your assestment of the value in maps advertising. This is why Google acquired Where 2 Technologies years ago, why they had an outstanding Maps app on Android from day 1, and why they have continued to iterate on it more than any of their other applications.

It's also why Apple has waited until now to address it. It's because they are not Google, this is not their core competency. It's a platform hole that has to filled, simple as that. Same as iCloud Mail.


> the simplest explanation is that Apple and Google could not come to terms on the price for access

Yeah, it's not like Apple is sitting on a mountain of cash right now! Oh wait...


"I have a lot of money" doesn't translate to "I should make bad business deals".

If nothing else, it's certainly possible that writing their own maps app and taking the initial PR/UX hit of "it's not as good as Google's yet" was the only reasonable option available to them.

(Not that we have any idea.)


for a company that makes the claim of not compromising on the user experience. They have taken sacrifices in the past to ensure a better user experience. Its not out of character if they did have to spend more money for a year till they got out maps perfectly


I really doubt that they charge Apple for shipping Google Maps on their phone. They want as many people as possible to use the app.


They don't charge to ship the app, they only charge Apple when people use it : http://searchenginewatch.com/article/2122151/Google-Maps-API...


As I said, I don't think that kind of thing would apply to a Maps app by Google. It is for businesses who use maps for something else. For example if you show a map on your homepage with all the locations of your stores.

The browser makers (Mozilla & Co) don't pay either if somebody opens the Google maps web site.


You have completely missed the big picture here.

Google charges 'volume' users of their maps API, that is part of the way they pay for it. The map "application" on iOS was a client that called Google Maps APIs and displayed the results. It generates a lot of volume, and Apple was going to have to start paying for that this year.

you wrote: "For example if you show a map on your homepage with all the locations of your stores."

If you did that enough times Google would start charging you. They also reserve the right to show ads for somebody else's store on your map. (not that they would just yet, but they keep that right in reserve if you want to use their content.)

Google and Apple sell Ads. Google is much better at it than Apple is, but the great untapped market is effectively advertising to mobile users. A common theme for desktop users is they use web search a lot, a common theme for mobile users is that they use map search a lot.

Apple wants you to sell ads through their network, so they get a huge chunk of the ad revenue that you are getting for your content. They do this because you're showing your ad on an Apple device. When you use Google maps through a browser you get ads from Google's ad network on the page. If you use an Application (usually a better UX) the platform provider has more control over you (they have to approve your App after all) So the fight here is who sells the advertisement into the Maps data stream.

Google has the best mapping product on the planet at the moment. They can use that to demand concessions like "we get all the ad revenue" in exchange for you being able to use our data/api. They don't care if the local restaurant shows a map to their location, the do care if you're an application that millions of people might use.

Its pretty clear that Google and Apple agreed to disagree and end their relationship with respect to Maps. That the Apple product is so horrible suggests that this relationship ended earlier than Apple planned, or their Maps technology has matured more slowly than they anticipated. Either way, the result is that Apple now has a grossly inferior maps application on their most successful products. This is going to cost them both in sales to people who are on the fence with regard to mobile, and in customer goodwill (this is already evident). That is a calculated risk they took. The alternative was to meet Google's requirements, whatever they were, to continue to use their map data in their application.

The part I think you are missing is this. Apple had to know how crappy their Map application was, customer experience is what they do, they don't just forget about it all of a sudden. Given that they are shipping that pile of crap means that they and Google are at odds on this issue. Is there any scenario where Apple would 'approve' an application by Google that would be instantly significantly better than their native App? Or conversely, given that they couldn't reach an agreement on the native App, do you think Google would agree to constraints in a published App that they would not agree to in a native App?

No, the only explanation that is credible is that they walked away and Apple has dug in their heels and bet that they can build out a better map experience faster than Google can take market share away with Android's map experience. From where I am sitting, given the significance of the risk involved in taking that path (some of which we're seeing being actualized as rampant ridicule) I can only imagine how distasteful Google must have made it for Apple to stick with them. And that suggests to me that you will never see another native Google maps product on iOS until Apple capitulates and cedes the space to Google or Apple moves so far ahead of Google that they no longer feel it is a threat to their advertising base.


So now it is Google's fault that Apple ships a crappy maps app? Sorry, I think Apple just were too full of themselves, and they were greedy at the expense of their customers.

As for the other story - sure, if Apple had demanded that the Google Maps app shows Apple Ads, not Google Ads, or that they get a share of the Ad revenue, then Google would walk away eventually. Obviously it is also worth something for Google to have their Maps on iOS, so they might even have paid Apple for the privilege for a while (either a fixed sum, or part of the ad revenue).

If Google were to publish a Maps app now (and Apple would accept it), it would simply be free and show Google ads, like all the other Google maps. Apple wouldn't have to pay a dime. Why should it have been different with a Google maps app shipping with iOS?

Maps are a central part of a mobile device, so I suppose Apple was getting desperate to get a share of the pie (Ad revenue and valuable data collection).


Why should it have been different with a Google maps app shipping with iOS?

Because the world of business development is very different from the world of consumer APIs. In a bizdev world, you want SLAs and contractually understood definitions of how both sides will behave. A company like Apple (or Google, Oracle, Microsoft, etc) isn't going to build a core feature of its product on somebody else's technology without understanding exactly what that means.

And all of that costs money.


Is there any indication, anywhere, that Apple had to pay Google for the maps app? Quotations, citations? I really really doubt it, if anything I would expect Apple received money from Google for the privilege of being the preinstalled maps app.


I take it you have a source for this assertion?


>Is there any scenario where Apple would 'approve' an application by Google that would be instantly significantly better than their native App?

Yes. The scenario we're currently in. By approving Google Maps app now, they give their users back the experience they expect without having to pay Google for the use of the Maps API. Meanwhile they can keep working on their own mapping solution until it's ready to take over, at which point they can pull Google Maps from the App Store.


Read the 9to5mac story about rumors of a Google Maps app waiting to be approved. So we get to test that option. I think its fabulous since it can give us data that neither Apple nor Google would give up voluntarily :-)

Truly one of the best parts of working at Google when I did was being able to see so much more of the moving pieces in these sort of mini-dramas. Don't miss it enough to go back but it was unique.


I don't know what happened between these two huge companies. But it is actually good that their relationship (with respect to maps) ended. Apple's maps suck today, and will probably suck for a year or two - but I'm sure they'll continue to improve. Few years from now, customers will have more options - right now, it is Google maps and Google maps only and the closest competitor is Bing, which isn't half as good as Google maps. Having more options is good, so no company can hike rates crazily like Google did.


> what happened in contract negotiations with Google to force it out.

This is almost certainly Apple being pissed off about Android and continuing to untie themselves from Google.

It just isn't working out as well as they had planned.

Google give Maps for free to other providers as well, as long as you bundle search/gmail with it.

Apple decided to pick out and replace the only part that Google don't make money on in iOS, the part that had the most technical risk and the part that Android completely kick their ass on.

Google right now are asking why they should bother going to the trouble of producing a no-revenue Maps app for iOS when so many users suddenly discovered a greater appreciation for Android today.

Apple completely screwed up here. In more ways than one - and it was all because of a grudge.


I couldn't care less about what Apple was thinking before they released this. What matters is that they pushed out a living, breathing UX fuck-up of an application to millions of people that depended on it to get around.


And if each iPhone user reports one problem, the entire POI problem will be solved.

I didn't calculate that, but I'm fairly certain it works. The only reason Google knew where my businesses were was because I told them. They kept that information walled up, so I guess I need to tell apple too now that there are millions of people seeing that database.

I haven't found where to add a POI, it may not be there, but marking wrong ones is easy.

Edit: Found it. Adding a location is under the "report a problem" under the curl up corner. Don't start with a new pin.


> And if each iPhone user reports one problem, the entire POI problem will be solved.

When each iPhone user reports one problem, and staff at Apple take a look at them all, determine whether each report is correct, and act on it, the entire POI problem will be solved.


If you touch the corner to reveal the map options, "Report a Problem" is next to "Data from TomTom and others." You can report incorrect search results, incorrect street labels, missing location (POI) or problems with directions.


Adverts.

Spatial adverts are a big thing now, with a big future. I would speculate that beyond the cost of licensing the maps or the contractual stuff is that Apple did not want to deliver to Google more advertisers that would further entrench Google Maps as the dominant player.

Apple need to be able to build their own POI database and knowledge of where all advertiser businesses are in order to get that revenue long-term.

Thus, Apple need control of the maps to control the method that advertisers get onto the map.

I think it's just strategic rather than contractual or short-term financial.


I'm not sure whether you're saying that there weren't google ads in the old iOS maps, but I'm fairly sure I saw an ad there when I did a search for Pizza Hut a week ago in SF.


There were. I think they called them "Sponsored" or something. It really annoyed me because if I'd search for something common like "Home Depot" it would give me random pins at places that were definitely not Home Depot but rather sponsored businesses.


None of this is true.

Google doesn't own their own POI database they license it from others and to date Apple hasn't approached these companies. So it isn't about the POI database.

It's more about the fact that Google was withholding data for Turn by Turn and 3D.


Zagat and Frommer's aren't comprehensive, but surely they're at least important POI databases?


That makes sense, but you miss one point - Google isn't the only game in town. Why not contract with Bing, which has it's own mapping app on iOS and use that for iOS 6 (either permanently, or as a stop gap while you perfect your own mapping software). I would be surprised if Microsoft would reject that offer, given that it would help them get more search share and mindshare. I wonder if they tried this at all.


> Was it just too expensive? That's possible, especially if these negotiations happened during the time Google massively raised the prices on its API

I think the figure was that Apple had $117bn or so IN CASH at the end of Q2. Whatever it was, money cannot have been the issue here. (Also, consider the cost of developing the new Maps.app in-house. Huge.)


If I had $500 in my pocket I would still not pay $20 for a latte.


> If I had $500 in my pocket I would still not pay $20 for a latte.

... but the alternative here is alienating half their users.

They don't have to pay Google forever, they just have to pay them until they actually get their own mapping infrastructure into a usable state.

Nobody likes paying too much, but sometimes the alternative is far worse, and you're much better off just swallowing your pride and doing it.


Release early, release often. Luckily Apple themselves don't have any delays getting revisions into their app store.


The only issue is that since Maps is a default app, not managed by the App Store, Apple has to push OS updates to update it in any way, which is somewhat of a barrier to adoption.


But the problems reported are all data problems, which presumably can be fixed in the cloud. No app update needed at all.


Yeah, not only that, but you can apparently register your iOS app as a routing app for Maps, and its content will be integrated into the Maps app for users who install it.

http://appleinsider.com/articles/12/09/20/embark_garmin_add_...


And yet that shouldn't be a problem if the issue lies in the server's data.


The "roller coaster" effects in the 3-d view are my favorite. They've got some smoothing algorithm going, or it wouldn't curve the way it does, but the elevation data must not have a high enough resolution. Google has made this sort of thing look so easy for so long, but it's clearly very hard to get this stuff right.

So, I guess it's not that surprising that apple messed up something incredibly hard in their first attempt. I'm curious as to whether these issues are as widespread as they seem, or if they're more edge cases made to appear common by the internet. But the curiosity isn't enough to drive me to upgrade. I'm totally putting off that until I figure out a decent alternative app.


I don't think Apple gets a pass here. If they are forcing users onto their product it had better be competitive, no matter how hard it is. Microsoft got so such pass with WP7 and that was an entirely new OS/platform!


It's not known if Maps was removed because of Apple or Google or both. So while there's no choice on having Google's Maps removed in iOS 6, the reason it happend isn't clear. When it came time to renew the contract one or both parties could have made unacceptable demands, leading to the current situation.


Yes, it's interesting how everyone has been assuming Apple booted Google off of iOS as an act of vindictive retribution. Everybody assumed that Apple's maps would have magical qualities that would leave Google looking second rate. Now that it seems to be the other way around you have to wonder if it was actually Google that pressed the big red button on the maps contract.


I think it's not really a case of who booted who off. I assume that Google wouldn't let Apple have any of the good features like vector maps or turn-by-turn navigation. Google Maps on iOS was already the shittiest mapping app across all platforms. So Apple have replaced it with an even worse alternative but at least it has some headroom to improve vs 2004 Google maps experience which was never going to get any new features.

I think Apple made the right move. Even if Google is 10 years ahead in mapping, the experience you got on the iPhone was Google maps from 2004. So Apple is only 2 years behind 'iOS 5 Google Maps' and given the resources they have to throw at the problem it'll probably improve quicker than that.


Anyone here actually used this version of Maps to find someplace yet? Not just to break it and point and laugh, but to actually use it?

I can only see 3D maps as a gimmick, so I can't bring myself to care too much that it's broken. I'm slightly surprised that feature shipped in that state, but meh.

What I care about: can it get me where I'm going? It's 2012 and I've still found nothing that can do that without occasional issues. This version of Maps hasn't been in my hands long enough to judge it properly. Considering the update was just released to the general public less than 48 hours ago, has anyone had time to judge it properly?

Worth noting: I've had the old Maps try to send me through concrete walls, or direct me 400 miles away looking for the nearest branch of a bank. My dedicated GPS unit has told me I've arrived at my destination… in the middle of a busy highway, and it too has asked me to turn through concrete barriers more than once. I've had both direct me to locations well off of where I was trying to go.

This is all from actual usage.

So if anyone knows of something that doesn't have these problems, I'd love to hear from you!


It tried to use it today. I'm in Kapaa, HI. I searched for "Bar Acuda" a highly rated and popular restaurant here on Kauai. iOS 6 maps gave me some place in Spain. Tried "Bar Acuda, Kauai" and was told "No Results". Tried iOS 5 with just "Bar Acuda" and it found it first try.

It's not just the quality of the maps that's an issue. It's also the quality of search. Google maps isn't perfect either but on top of having better map data is has better search so for example searching for "gauteir exhibit, sf" actually finds the De Young Museum in San Francisco even though I didn't name the museum nor did I spell the name correctly. IOS6 maps just said "no results"


For me a killer problem is that it doesn't have access to the massive Google Local place database, so I find myself unable to find the addresses of things I want directions to (making the question of whether I'd get good directions to the destination pointless).

Here are screenshots of an example situation I ran into yesterday, while trying to pick up my iPhone 5 from the UPS Customer Center:

http://cache.saurik.com/tinyimg/ios6upsmap.png


It works most of the time. Especially for businesses, as I think it accesses the yelp directory. If it gets point a and b correct, the routing seems ok.

Most errors seem to be that of string parsing - the biggest sin is not recognizing town/state portions of search strings consistently.

Ironic since I'd bet some of the best language parsing people are busy working on llvm and clang somewhere else on apple campus.


For that matter, they have people working on natural language processing, though my phone's too old for me to know how that's working out for them.


Here in London you're only guaranteed to find where you're going if you search by postal code. And the directions are quite bad too… through parks and etc.


The Mayor of London has some tips

http://i.imgur.com/o44nv.jpg


Does Apple have a Maps program on the Android devices? Are there other Maps programs available on the iOS devices? Saying Apple is 'forcing' users onto their product is a bit much.


You're being obtuse, people have money invested in the Apple ecosystem, it's not easy to switch, and no other mapping app will have the iOS integration Maps does. Until a comparable app is available on the OS, yes Apple is forcing users onto their product.



You're not forced to upgrade to iOS6 nor is Apple blocking Google Maps on the browser.


I upgraded to iOS6 to get the turn-by-turn navigation. Now I discover that only iPhone 4S and 5 devices get voice guidance. There is no way I can get Google Maps back without jailbreaking my phone.

The voice limitation appears to be simply planned obsolescence; Waze can handle it without issues. This is a slap in the face to someone who paid a lot of money to Apple for a current-generation phone a little over a year ago.

Apple's closed platform has worked only because they've been able to give consumers such a high-quality experience. I think this fiasco will be a big wake-up call to lots of iPhone owners about how Apple's limitations can hurt them.


> There is no way I can get Google Maps back without jailbreaking my phone.

You can't restore from a pre-upgrade backup?


If you didn't jailbreak beforehand and capture the SHSH blob, no, you can't. So for the vast majority of people who upgraded to iOS 6 there is no going back.

http://blog.iphone-dev.org/

That's the cost of being inside a walled garden. You don't even have the freedom to install previous firmwares on your device.

But since the browser is part of a firmware upgrade it would be a terrible idea anyway, a new security bug has been found on mobile safari recently, you don't want to stay on older fimrwares if you can help it. Google maps, or a secure browser ? Pick one.


You're not forced to upgrade to iOS6

Oh, come on.

nor is Apple blocking Google Maps on the browser

And nor are they allowing third party apps to integrate into the OS in the way their Maps app does.


Unless you want, say, security updates. You're also forced to buy a new phone/device if you want them after x years too, where x is a low number


Where X is a number considerably higher than for Android. Look at the number of years the 3GS has survived and compare that with your average Android phone not getting latest OS updates or any security updates.

But I agree that anyone buying a new phone is stuck with iOS 6.


It depends on what kind of updates you're talking about. OS updates are a problem, but I personally know that the G1 got around 3 years of Maps app updates, and given the current OS version distribution newer devices are likely to do even better than that.


My Motorola droid is able to run Android 4.1 - not a super snappy experience, but it does run. It released in october of 2009. Every feature in 4.1 works on it. I don't have the "fun" apple is pulling with a guessing game on what features work on what phones: http://www.apple.com/ios/feature-availability/

Also, while the 3GS (June 09) is getting ios6, the original ipad (April 2010) is not. Apple will abandon their equipment just as fast if it suits them.


> Also, while the 3GS (June 09) is getting ios6, the original ipad (April 2010) is not. Apple will abandon their equipment just as fast if it suits them.

Indeed. I am quite frustrated that my first-gen iPad is, for whatever reason(s), not deemed worthy enough of iOS 6.


What about the people upgrading phones?


As of today, I don't know of any Apple Maps alternatives in the iOS App Store. And switching a mobile platform is neither trivial nor a short-term perspective … I hope Google is busy worki on its own Maps app for iOS — for the time being, Google Maps in Mobile Safari has to do it for me.


There are 100s of navigation apps and almost all have maps, directions, gps integration.


And can be set as the default app so when I click on a location, it takes me to that location without forcing me to jump through hoops in copying the text, and then clicking over and eventually pasting it? You know, like it was in iOS5?

Awesome!


That is not a "map" thing that's an IOS thing. If you want to change default applications, better switch to android.


Sorry, you missed the point. Maps has changed. Rather than add a new app in called "Directions" or some such, they dramatically changed the default behavior by removing functionality people depended on. And keep in mind, Apple has a long history of having multiple applications that share the same zone of responsibility.

After 5 versions of the OS, people have what amounts to a beta application without any fallback as of yet. A major feature of the device was discarded.

Kind of hard to put trust in a company that will disregard users like that. And, to be fair, this is not new or surprising. It's one thing to do this on the hardware front. But another thing entirely to do it on the software front.

Keep in mind, this is not the first time they've done this (see the FCP debacle), and when that happened, they caved to customer demand.

So yes, it's a Maps thing.


You got it.


Wow, that was easy. I have a bridge to sell you.


Or jailbreak, from what I understand.


Do you have a single recommendation for a native Google Maps replacement?


just use maps.google.com in mobile safari, it works just as well as the old app.


Bing.


Yes there are other maps programs available for iOS - the Google Maps app that comes with iOS 4 and 5 is very capable.


That app has been replaced with the Apple Maps. Google maps is only available via the browser in iOS6 (at this time).


> does apple have a maps program on the android devices?

not that i'm aware of. i don't believe there to be a browser interface for their maps "solution". i could be wrong.

> are there other maps program available on the ios devices?

yes. google maps, or any other maps via the browser. sure, not the kind of integration one gets from an app. but there, nevertheless.


iTunes is certainly going to ask people to upgrade without giving them a warning about the Maps downgrade!


talking of pass, you should checkout the new nokia maps on the lumia. It's f awesome!!!


It seems every comment you've made here in the past few days has been about Nokia's new device. Astroturfing or just a fan?


...but faked.


source?


Busted.


Jobs would have fired the whole Maps team, en masse.

Furiousness is a skill. Tim Cook falls short here.


Actually, Jobs would never have allowed Maps to be released in this state to begin with.


So… you two both personally knew SJ?

And SJ, while he was leading Apple, was always without fault?

If that's the case, how do you explain Ping? MobileMe? The G4 Cube?


At least they were functional, and it's not like they pushed ping and blocked every other social network from working on macs.

As far as what Jobs would have done; the state of the maps is a plain embarrassment - I can't see why anyone has released this, let alone anyone with as much care about details as Jobs.


What is equally sad is that people put up with this substandard implementation of a core smartphone functionality. That Nokia 920 looks more and more appealing at this point of time with Navteq maps an OIS enabled camera, the two most used functions on a smartphone.


If those two were the most important smartphone features, Nokia would have never have gotten to the trouble they're now in. They've had pretty much the best camera and navigation features ever since the circa 2007 N95.

So, camera and maps are clearly not the primary features influencing smartphone buyers.


The best navigation and camera did not work out for Nokia because many did not realiZe that it did. But hey, that seems to be changing.


The G4 Cube doesn't deserve to be mentioned in the same breath. It was a work of art.


Except for the hairline cracking at the corners that happened to most of them.


I'm sorry, but the Cube is the single most important and consequential machine Apple ever made. Its design cues pervade everything from their flagship store to the individual keys on the keyboard on which I'm typing this. Nearly everything they've sold in decade-plus since bears the stamp of that glorious and utterly unprecedented machine. It's the entire Jobs/Ive aesthetic and philosophy in one box, a prototype for an entire company - one which has since grown into the most valuable one on the planet - and they SHIPPED it.

@philwelch is right. It's a work of bloody art. It's in MoMA's permanent design collection for a reason. It's the Neil Armstrong of personal computing. If it's a mistake then so was Newton's Principia, the Declaration of Independence, and Sgt. Pepper's Lonely Hearts Club Band. Seriously, it's that good.

If you're going to slag on something, slag on the hockey puck mouse. THAT really was a POS.


Sorry but I'm not buying that. I can see that squares with rounded corners are everywhere in apple's design. I don't think that comes from the Cube. It was just a result of this love for the rounded corner square.


This is strange. I've never been a Mac person. I've built and modded PCs since I was a teenager. I didn't really remember the Cube and have googled it just now.

(back in the day Macs were for oldies who didn't know what the hell they were doing on a computer so Apple products didn't really register with me at the time)

My first impressions are that it looks like a plastic rubbish bin.

I always loved the G5 tower though.


Take a slice of that rubbish bin's midsection, and you have the Mac Mini. Tilt that Mac Mini on its side, perforate either end, then add some handles, and you've got the G5.

You can play this game with just about everything Apple has sold since this machine was introduced. Virtually all of it has some design cue that can be traced back to the Cube, and no further. It really was the Genesis Box.


Sweet lord, put the jug of juice down son.


Ive's work in plastics hasn't held up as well since the switch to metal and glass, but at the time it was a remarkable, groundbreaking example of industrial design. The next year, of course, they launched the titanium PowerBook that spearheaded that transition, though it would take about a decade for plastics to be phased out entirely.


All of those were relatively minor projects, and likely off Steve's radar, which is why he could only berate the teams after the release. But maps is a major part of any smartphone experience - everyone knows it. And Steve would definitely would have paid close attention to it, especially since it involved trying to outdo a competitor's product.


MobileMe was – and is, as iCloud! – a major corporate initiative. It touched almost every product Apple was working on at the time, affecting iOS, OS X and iTunes. It required significant capital investment in back-end infrastructure, and was announced by SJ himself and demoed by Shiller at the WWDC '08 keynote.

At the announcement it was couched as "Exchange for the rest of us" – it was trying to outdo a competitor's product. (To say nothing for how it countered many of the features Google was trumpeting for Android…)

SJ was absolutely aware of MobileMe, and was intimately involved with many parts of the product.

And, given all of that, it still was a flop of a launch. A launch that was so bad, I'm sure it was a motivating factor in the iCloud rebranding.

And to claim the G4 Cube was a minor product is just amusing. SJ was incredibly proud of that machine when he announced it. And you know he was deeply involved in its design, from day one.


merely blips on an otherwise uninterrupted upward trajectory.


I think it was the MobileMe team he humiliated and necked out of the door. Part of Apple lore.

Now everybody knows that Apple's history with cloud-based initiatives have been less than stellar, and no time was that more clear than during Apple's klunky MobileMe rollout a few years ago. Server down time and extremely slow loading times had many wondering how Apple let a product that seemed beta at best roll out to the masses - for a $99 fee no less.

The MobileMe fiasco was of course not lost on Steve Jobs who reportedly told members of the MobileMe team that they "should hate each other for having let each other down."

At one point, Jobs asked his team what MobileMe was supposed to do. Upon receiving an answer he quickly fired back, "So why the f doesn’t it do that?" Jobs even invoked the name of trusty ally Walt Mossberg - who was critical of MobileMe - to drive home the point that the MobileMe rollout was a flop.

"Mossberg," Jobs said, "our friend, is no longer writing good things about us.

Source: http://www.networkworld.com/community/blog/steve-jobs-mobile...


I know many people who were and are on that team, and am well familiar with the described meeting. That meeting doesn't change the fact that Apple shipped MobileMe while SJ was CEO. It was a bad product that had a horrendous launch; SJ could have delayed the launch or killed the product, but didn't.

Jobs was a marvelous CEO, but Apple made many missteps – some larger than the current uproar over iOS 6 maps app – while he led the company. Without having personally knew the man, one cannot claim what SJ would have done in this situation. Plain and simple.


The one big difference here though is that it's very hard to tell if a cloud service is ready before you subject it to real traffic.

A lot of the problems people are having with maps seem glaringly obvious and a lot of developers were raising red flags on this during the iOS 6 beta.


At least MobileMe didn't replace some other awesome cloud functionality.


Oh Geez, are you for real?, "Jobs would never have". I can't be the only one to notice this ridiculous fanboy behavior.


I would agree with this...there were a lot of features that "cooked" for a long time under the wraps. Better to keep the iOS 5 maps app going for one more iteration while Apple Maps simmered for a bit longer.

then again, they do need the crowdsourced data, but maybe they could have had the iOS 5 app stream a duplicate of whatever it's phoning home to google into the new Maps databank.


I wouldn't go as far as blaming the Maps team for this. It's not their fault they haven't had YEARS to catch up with Google.


It looks like a pretty good product to me. I think it's silly they have forced it onto people already but I wouldn't say it's bad. Just not as good as the competition yet.


>Microsoft got so such pass with WP7 and that was an entirely new OS/platform!

Well, around tech circles, Apple and Google frequently get more free passes compared to Microsoft.

And that's kind of funny because Nokia just put out a comparison with Apple and Google maps to cash in on this hoopla.

http://conversations.nokia.com/2012/09/20/benchmarking-mobil...


Nokia acquired Navteq, which was already a top player in the mapping space. For about a year, their horrible S60-based models were selling well because they all had free high-quality mapping apps with turn-by-turn navigation and TomTom directors were shitting their pants.

Then Apple and Google "divorced" while the iPhone was exploding, Google basically stopped improving Maps on iOS (all features went to Android), and here we are today, with the best-selling smartphone falling 5 years behind. Not Apple's finest moment.


>Google basically stopped improving Maps on iOS

incorrect: maps was an apple app that use google maps service. So it was apple that stopped improving maps on Ios


It's fair to say Apple couldn't improve it without help from Google. It's not like they could just switch to the officially-published API and hope Google would let through all the traffic.


Apple and Google had an agreement in place. It was apple that chose not to continue this agreement. Speculation: I find it hard to believe from a business perspective that Google would want to do anything to harm this relationship as the map and map search provider on the ios platform. Being the default service for maps on ios is a win for google. Even if they release an app at this point, they aren't the default which is a step backwards.


There is no way that it was a unilateral decision by either company. Clearly there was some offer (e.g. more money, dropping patent lawsuits against Android) that Google would have been happy with. Or some terms that Apple would have been happy with (e.g. lower cost, access to more API features). It's not either party's fault alone that they couldn't agree about the terms.


Don't forget that Apple and Google is currently playing in the same game, smartphones and tablets. Probably a strategic move by Apple.


Strategic, perhaps, but terrible nonetheless.


Or it could have been a strategic move by Google knowing the work that needs to be done, and that getting up to speed on maps would take Apple years.


this would be the worst strategy ever. So instead of becoming the major search for web and places/location on what would be close to 90% of the worlds smart phones, they instead would give up all the data and being the default search on the ios platform. Theres no way people are going to abandon ios over a sub par maps app.


It was apple that chose not to continue this agreement.

Do you have evidence of this? I find the history of this fascinating and have my own theories (that I've posted elsewhere), but this is a pretty definitive statement that isn't the way I imagined things going down.


from a business standpoint. Google would be the #1 search for browser and places/location on the top two mobile platforms globally equaling to over 90% of the smartphone searches. What possible reason would there be for google to not want to be the default places/location search on the ios platform ?


Depends on what the terms of the Apple-Google agreement were. It's possible it did not include the additional features.


correct it is speculation, but from a business perspective I wouldn't see it as beneficial for Google for them to not allow apple (at one time the most popular smart phone worldwide) additional features upon request. Googles bread and butter is search and data collection. But yes there could possibly be a reason.


Agreed, but we know how poisonous the relationship became after they started warring. It's possible that reasonable contract extensions and expansions became mired in politics.

For instance, when Google launched turn-by-turn navigation for Android they said that it'd be available on the iPhone as well before long. That never happened.


It's not really fair to qualify Apple's entire product as "falling 5 years behind" based on one app. The phone is far more polished in virtually every other way. Maps is important, other things are important too.


I meant to say "in the mapping space". The post originally had a rant about the inevitable full phone/GPS integration being delayed because of these silly corporate squabbles, but I removed it at the last minute.


I'm surprised by how poor this Nokia comparison is. Maybe it highlights the difference of that company vs Apple or Google.

The post focuses on the reach of their maps by showing lots of numbers in a comparison. They would better demonstrate their point with side by side pictures, like the ones from OP of this thread.

Personally, I wonder about the reach of this marketing angle. I take 2 international trips per year. I'm in the same city 330+ days/year. I don't care if the maps work in Columbia or South Africa. I just want it to work well where I live!


> I don't care if the maps work in Columbia or South Africa. I just want it to work well where I live!

So do people in Columbia and South Africa. :)


Indeed it is a fairly Universal attitude that one's own geographical Focus is Paramount.


I see what you did there.


Personally, I'd quite like it to work in places that I'm going to travel to as well.

I'm also in the same city for the vast majority of the year, but I already know how to get from home to work and back.


> Apple and Google frequently get more free passes compared to Microsoft

Microsoft used up their free passes almost 20 years ago now.


But you can't give them a pass here, the premium value that Apple sells is the amazing experience out of the box. How many years has it been since they got something wrong just out of the box?

[No apple-hater, but postponing upgrading iOS indefinitely]


Or getting a phone with better mapping GS III or Nokia 920


I also wonder how common these problems are. I live in San Diego and everything looks pretty-good to me. It renders my house in 3D and the turn-by-turn navigation worked great. There are obviously problems in some places, but so-far-so-good here.


I'm not surprised that results in California are great. This seems like a great example of why having the majority of your testers in one geographical location is not always a good thing.


I live in São Paulo, Brazil. The maps work well here. I simulated a trip to another city like I did with Google Maps a few months ago and the navigation is just as good.



Tourists and expats are going to have issues in some countries, take for example Thailand.

http://imgur.com/7gkgx

Google Maps has street names in both Thai and English, whereas Apple Maps only has Thai.


You can turn off this feature in Settings -> Maps. Just turn on "Always English" nob.

Edit: Just tested. This does not work for street names. Sorry.


In Switzerland, the information density is much lower in comparison to Google Maps and much of the still available information is wrong or out-dated. Outside rural areas, Apple Maps mostly shows a vast emptiness instead of mountain peaks, hiking trails etc.

There's definitely room for a lot of improvement …


I live in the Netherlands and it seems to work like a charm so far. the whole upheaval sounds like an internet pile-on to me.


After communication, maps are the second most important application on a smartphone for a lot of people. If those maps go from being reliable to being wildly wrong -- which, it seems apparent, has been the experience of a number of people -- then you can hardly expect them to not be upset.

If there were some perfectly reasonable explanation for why upgrading to the new version of iOS/Android/whatever caused text messaging to stop working reliably for a significant percentage of people, I expect we would see more or less the same reaction.

Of course, the fact that it sometimes generates utterly ridiculous visuals is no doubt helping the spread of the meme, but the underlying complaint here seems perfectly valid.


" If those maps go from being reliable to being wildly wrong -- which, it seems apparent, has been the experience of a number of people -- then you can hardly expect them to not be upset."

Agreed and I would add when you're buying a $199 "next-gen" phone, I'd expect things to work properly out of the box.

If it isn't ready, then don't release it.


The bits that have been 'wildly wrong' so far seems to be the business integration (which is probably also the most easily corrected). I wonder if the people who went to the effort of posting screenshots with "lolz, this business should be here" actually reported where the location should have been using the Report Problem button on the location pin.

Searching by address for me has been accurate (and at least a couple of the screenshots on the linked site are obviously playing on that by having street address in one window and business name in another).

In my part of the world (rural Western Australia) the route mapping (which I use Maps for far more than searching for a business name) is looking pretty good, even though we don't get turn by turn until next month apparently. Incidentally route mapping is something that Google has screwed up for me on more than one occasion as well.

The text messaging comparison is just ridiculous.


Tijs, come to NY some time to see how bad it can get. :-)


Planning to, but i bet they've fixed it by the time i'll get there.


See: Clement Valla, Postcards from Google Earth, http://clementvalla.com/category/work/postcards/


I don't think Google has 3D view at all. Those 3D maps were created by a different company whom Apple recently acquired. You can probably find the same errors from here as well, http://maps.nokia.com/webgl/


Google certainly has 3D view. It's on my iPad with Google Earth. They also have the more useful non-textured 3D maps in Google Maps for Android which is a lot more smooth (way less data transfer and being vector it's scalable) and you can even use them offline.

http://www.google.com/mobile/maps/3d/



Yes, indeed http://www.youtube.com/watch?v=N6Douyfa7l8

This is new development though and only on the Google Earth product for mobile, not in the maps app. Maps app for Android has those blocky untextured 3d buildings in select areas.


Google has had 3D buildings for years. That video is only the latest in a long series of improvements on this feature. The level of detail in that video far exceeds what others are doing, but it's still rolling out throughout this year.


They actually have textures if you enable satellite imaging. They just also do the Mirror's Edge rendering of the city.

It's interesting how Google does it. They both contract and scan data in, but they also let you use SketchUp to submit data as well.


That level of detail in elevation data generally requires LIDAR and that definitely doesn't exist for all municipalities, and is pretty expensive where it does.


The 3D view mess-ups are fun to look at but are the most understandable and least unique to Apple. It's not hard to find messed up 3D in Google as well.


You can get elevation data for North America from USGS: http://ned.usgs.gov/


It is either the classic problem of floating point precision or just data a data collection error. See my other answer.


I'm pretty sure some (if not most) of these problems are just polygonization issues i.e. when converting the image based approximation point cloud to polygons at a low level of detail. Those weird zigzag lines are clearly sign of incorrect topology / low polygon density; polygon edges should follow the curvature of the road, not go against it.


What confuses me about Apple's choice of maps here is why they didn't go with OpenStreetMap? It was the perfect opportunity to leapfrog Google and help the open source community at the same time, and they would have had more control over the data - as it is they are beholden to TomTom and other providers to try to get things fixed, or will have to try to merge future map updates with their own patches. As it is they are going to see increasing controversy as people realise just how bad the maps they have bought are, and that this was changed for political reasons, not for the good of their users, and there's very little they can do about it.

They seem to have tried out OSM in the photos app (with a horrible skin), but to have used purchased data for the street maps. Perhaps they felt it wasn't good enough in some locations they tested?

In my experience OSM is superior to Google maps in many locations (even in parts of central London), and it is of course continually improving.


Openstreetmap's doesnt address any of the OP's issues. Having built maps for the past 12 years, I know exactly what of each of those issues are about. The blurry images are underlying base layers that drew first and then probably the upper layer timed out when rendering the tile. The curves are caused by elevation measurements that are incorrect (measuring elevation from a satellite involves bouncing from the ground - when there are structures below, depending on the material, it may go through or bounce differently) or precision problems when generating the elevation grid (very common). The big white thing are clouds, when you buy highly expensive imagery you get them with louds (say 30% cloud blockage) and you need to comnine several images taken a different times, color correct them, and stitch them back to remove it (try to do this for one city and then think about doing it for the entire world). The routes that don't match the pins is weird, but it could be that the snapping point for the routing engine snapped to the wrong street edge (it seems very far though) or that the geocoder and the routing engine use different geocoders (that would be bad). Creating a good mapping product is difficult, but Apple will have something much better in one year.


Apple will have something much better in one year

It certainly will be better but I'm not holding my breath about Apple maps surpassing Google Maps any time soon. Google bought a Rasmussen brothers' company (what eventually became Google Maps) in 2004. That's eight years of product development, data collection, storage and refining -- all at Google's pace. Will Apple find some shortcut to compress this time in one-two year? Unlikely.

It's very easy to underestimate the amount of pure, repetitive effort required to build products of this sort and how hard it is to "disrupt" the industries with players like Google.


I meant "much better" than what Apple already has.

I don't think it will be easy for them to catch up (it would be absurd to say that they can have something better than Google Maps in such a short time).

What bothers me a lot, is that most people blame the data errors to the algorithms or ability of the team to create good software. You can have the best coders in the world, and if they have data that is not good, they can only algorithmically clean it so much.

Google has several vehicles that they drive around and collect all kinds of information themselves. Sure you can hire Navteq (or in Apple's case, TomTom aka TeleAtlas) to go around and do it for you. Guess what? When you license products from either of those companies that means you are relying on their editors. That means no fancy object recognition geotagged image that you can send to a support vector machine to flag an area as needed revision... the product you get from that licensing is the vector line with the attributes already attached to them. So that is what you work with.

Google has an entire army in India, using Google-made custom editing tools that do these things. Unless Apple builds the same, they will always be behind. Can Apple do it? Sure! They have the cash and the talent. Will they? It is up to them to decide if investing 400 million into their mapping infrastructure is worth it. I think it is.


Personally, I certainly never supposed that the current version of Apple's maps somehow proved that Apple had incompetent people on the problem.

At the same time, Apple has a carefully cultivated history of not shipping half-baked products. They famously worked on tablets for years before they built one that they were happy enough with to ship.

Now, for reasons that the end user surely does not care about, they have taken a product that was missing a key feature or two (navigation, street view) and replaced it with something that is much less reliable even for its fundamental task.

Yes, making a really good mapping application is hard, and requires many people on the ground, around the world. So either you need to make the commitment to do what it takes to deliver that app, or you should outsource the whole thing, and use Nokia Maps or Bing Maps or whatever. The third alternative -- doing it yourself and shipping it to end users before it's ready and without having done all the due diligence -- is likely to be embarrassing.


It's not just "data errors" though. Not only are Apple's maps missing huge amounts of detail in many areas, but are missing entire categories of information.

For instance, in the map of the Shibuya station area in [1], besides the general paucity of detail, note that only roads are considered worth mentioning, although the vast majority of people don't arrive by road. That may fly in Cupertino, but it certainly doesn't fly in Japan. This is not the middle of nowhere—it's one of the most popular places in the largest city in the world, and indeed, is iconic even in the U.S.

The impression one gets is that Apple is way out of its depth here, and given the importance of mapping for smartphone users, that seems a pretty major screwup.

[1] http://www.japanmobiletech.com/2012/09/ios-6-maps-fail-in-ja...


It wasn't until about 3 years ago that Google Maps became the polished app that it is now, ie: vector maps, 3d building maps, tilting, etc. (Google has been in the map business for 10 years now?) Apple has a lot of catching up to do but it's very good at trudging ahead regardless of customers complaints until the product is completely polished and competitive.


Are the features like vector maps, 3d buildings, and tilting only on Android? I've only used Google Maps on iOS.


Yeah. Maps for Android is really amazing, the single coolest app for Android. Even two years ago it was really very developed. I missed it.


Maybe this is as good as it gets.

"Sources tell The Verge that Apple began work on the iOS 6 maps system nearly five years ago"

http://www.theverge.com/2012/9/20/3363914/wrong-turn-apple-i...


Hold on a minute... Apple had already started working on replacing Google Maps approximately a year before Google had launched a single Android device?

Wow. Just wow. Now we see how strategically brilliant (and utterly necessary) Android actually was.


I'm sure google is sitting on a treasure chest of map related patents, too.


With TerraServer, Microsoft got into online mapping before Google was even incorporated (and when putting a terabyte of data online was so far beyond the leading edge that it was a Microsoft research project). Their strategic partner Nokia has been in the mobile mapping space for some time as well.

Given the relative sizes of patent portfolios prior to Google's acquisition of Motorola Mobility, I wouldn't bet on Google should the IP wars shift to mapping...of course I wouldn't bet on Apple either.

http://en.wikipedia.org/wiki/TerraServer-USA


The link is to a rolling blog of images, so you might not be looking at the same images I am. Here is an example of one:

http://theamazingios6maps.tumblr.com/post/31923886066/are-yo...

There are a lot of problems with road map and point data (at least in the UK) which are nothing to do with the points you've raised above, though those are fair criticisms too - however the satellite data is the least of their worries, I'm sure they could buy in a better cleaned up set of satelite tiles if they're willing to spend enough money, and people expect some problems with that, but basic search and mapping is not as complete as it should be.


OpenStreetMap would have more accurate information about the locations of towns etc.


OSM doesn't do elevation. OSM doesn't do geocoding. OSM doesn't do routing. OSM doesn't do 3D. OSM doesn't have a cleaned up dataset of Points of Interest.

I love OSM and I use it every day - but I know what it does, what it is good for and what it is not meant to do.

Getting a list of towns for the entire world is easy. Solving the issues in the listed by the OP's tumbler requires data that OSM does not have.


OSM doesn't do 3D

For most people the 3D is an amusing toy, not really useful. I'd be happy without it frankly.

OSM doesn't do elevation

See 3D above

OSM doesn't do geocoding

They have data for searching on street addresses and towns, and the data is available separately for postcodes etc (TomTom for example will have sold a solution for this to Apple, so they could have gone down that route). Google has this down, as you'd expect given their search expertise, and Apple would have done better to pay them at least for access to this service if nothing else as it's a complicated area.

OSM doesn't have a cleaned up dataset of Points of Interest

Yelp does, and that's who Apple are using for POIs

One other point you didn't mention is that OSM doesn't do satellite data (their stuff is from Yahoo isn't it?), so that is a big area Apple would have had to sort out from another provider.

While you're right that there is no one-stop shop for mapping services, and it's a really complex area (i.e. just choosing OSM would not solve all these probs, as you point out) I do think Apple have missed a chance to form a symbiotic relationship with OSM and enhance the quality of their maps with an open process rather than relying on the often out of date commercial data available and having to either fork the commercial data from this point on, or merge changes. Dealing with all these fixes will suck up a lot of time they could spend on improving the app itself.


>For most people the 3D is an amusing toy, not really useful. I'd be happy without it frankly.

The complaints about the "zigzagging" are about the 3D viewer, hence, my comment about 3D.

>They have data for searching on street addresses and towns, and the data is available separately for postcodes etc (TomTom for example will have sold a solution for this to Apple, so they could have gone down that route). Google has this down, as you'd expect given their search expertise, and Apple would have done better to pay them at least for access to this service if nothing else as it's a complicated area.

To have good geocoding, you need to have line segments with correct ranges and topologically accurate (for example splits in the right intersection taking in consideration overpass/underpass and grade changes - the 3D stuff you don't care about - along with no dangling edges). If you think OSM fits this bill in a world-wide dataset you are incorrect. Go ahead and download the entire dataset and see for yourself planet.openstreetmap.org.

> Yelp does, and that's who Apple are using for POIs

Actually, yelp only has coverage in the US and in the few outside countries they are in. Most of the world is not covered by Yelp's POIs, so sorry, but "Yelp" is not a worldwide solution for POIs - which is what Apple needs.

> One other point you didn't mention is that OSM doesn't do satellite data (their stuff is from Yahoo isn't it?), so that is a big area Apple would have had to sort out from another provider.

Yahoo, nor google, nor anybody else have their own satellite providers. That data usually comes from GeoEye, Digital Globe or any other satellite image provider. But yes, you are right, "OSM" has nothing to do with raster data as a whole (except for the elevation-derived contours they have in some places).

Fixing OSM for anything else than displaying maps is a huge undertaking. Then, when you are done, you basically have to share the data with everybody else (including Microsoft, Apple, Yahoo, Mapquest etc etc). OSM is the GPL of databases, so for some use cases, it is not the best choice, for other ones, it is.

The post I replied to claim "Apple just pick OSM", and my answer remains... it would not have solved any of the issues that people are complaining about.


Your arguments all sound perfectly logical and valid to me. Love of the "spirit" of open source projects and other things have no place in making decisions that can have such a gigantic effect on all manner of people / outcomes of project/ etc. Not if you're going to actually be responsible for dealing with bad decisions personally. Geocoding I know is definitely a giant furrball of fuck I've learned in the past year. Thinking of building a map app and associated services like this is mind boggling to imagine.


I am offended. How could you mix up GPL with OSM? Is this some kind of a troll? If so it is very bad taste.

OSM data is licensed under ODbL. It has nothing common with those "license terrorists".


The ODBL license change was done 8 days ago and took 2 years to change. I was referring to the CC-share alike license it had before for the past several years. This was in reference to Apple using it (if they wanted to fix the data, they would have had to share it). I have not had enough time to study the ODBL license yet since as of 8 days ago it was not relevant to me.


The post I replied to claim "Apple just pick OSM", and my answer remains... it would not have solved any of the issues that people are complaining about.

It didn't say 'Apple just pick OSM' (which implies picking OSM would solve all their problems), and as I've pointed out, there are problems with data which it would solve. Here are some examples:

Puna, Peru, roads in the water http://www.openstreetmap.org/?lat=-15.8559322357178&lon=...

Cayman Islands, no road data http://www.openstreetmap.org/?lat=19.2949&lon=-81.343...

These are serious problems with data which Apple will have a nightmare fixing as there are just so many holes in their data outside the US, and they're now waiting for mapping companies like tomtom for updates, or they'll have to fork and then try to merge with tomtom/etc data later again.

For many (I'd say most) users of the maps app, the order of priorities are something like:

1. Accuracy of map data

2. Coverage of map data

3. Accuracy of map searches (streets, postcodes, POIs)

4. Routing (this is hard problem though)

5. Satellite imagery (for some this would be above routing)

6. Streetview (for some this would be higher)

7. 3D stuff

OSM would help with the first three points (along with other sources of course, just as say tomtom needs supplemented), and would also help in future as other people would do the hard mapping and updating work for apple, which will otherwise prove to be a mammoth task.

Everything else is far less important than getting the basic mapping data right first, including 3D renders of major cities, and even satellite data (nice to have, but less important than basic search and display of accurate mapping).

If they used OSM data and imported (say) every month, they could just tell people to visit OSM to make corrections, and problem areas would gradually get better. As it is they're going to have to sift through hundreds of thousands of reports of missing roads etc which just say 'this is broken, fix it', and they're likely to just be submerged under that workload. Anyway, I don't think we're saying such different things - I'm not saying OSM would cure all Apple's problems or even most of them, just that I thought it would be the best choice for them for the most important facet of their map product, the basic vector data, which is sorely lacking at present and unlikely to rapidly improve.


The 3D flyover actually is hugely useful, more so than street view in my opinion, when trying to figure out one's way through the layout of streets in a metropolis.


OSM doesn't do elevation

True OSM doesn't have that, but there are some public domain datasets available for that, e.g. SRTM.

OSM doesn't do geocoding.

True. OSM is just a database, you'd have to make your own "address ↔ position" algorithm. Which is sorta hard.

OSM doesn't do routing.

OSM is just the database. You can (and people have) make a routing engine on top of that (e.g. http://map.project-osrm.org/ http://maps.cloudmade.com/ ). You can do very specific types of routing (e.g. I figured out how to cross Dublin without passing a pub http://www.kindle-maps.com/blog/how-to-walk-across-dublin-wi... ).

OSM doesn't do 3D.

True.

OSM doesn't have a cleaned up dataset of Points of Interest.

Yes and no. OSM is a database and has lots of Points of Interest, e.g. here's a Starbucks in London ( http://www.openstreetmap.org/api/0.6/node/488443269 ), so it's trivial for someone making a map app to make a database of PoIs that an application can look up.


You can easily do geocoding with the OSM data. Nominatim is ready to deploy software that will let you do both normal and reverse geocoding. It is what openstreetmap.org uses for its search box.


And nominatim is open source ( https://github.com/twain47/Nominatim ), so if there's some silly embarassing thing that it gets wrong (like the address of your headquarters), then you can fix it yourself.


"It was the perfect opportunity to leapfrog Google and help the open source community"

The only time Apple helps open source is when they hire the most important people in really important projects, and then they graciously allow them to continue contributing. CUPS, LLVM, it's happened a couple times. They take good care of these guys, but I always feel like their contributions to the projects after Apple are being written with one eye watching over their shoulder to make sure they dont get sued for talking to the public about some super secret project.


First time I heard about CUPS! Apparently it's a kind of printing system. Thanks.

http://www.cups.org/

http://en.wikipedia.org/wiki/CUPS


Ha, hitting http://localhost:631 and using the CUPS interface is the easiest ways to fix a few problems on Lion/Mountain Lion.


you're not alone. apparently, for many people, occasionally hearing the word "CUPS" is the closest they ever get to printing under Linux.


I'm pretty sure that CUPS was shipping by default on some linux distros as early as 1999. I know I installed Caldera OpenLinux (2.2 or 2.3 maybe?) and Mandrake Linux (version 6 or 7 something) and both had it, detected my printers, and "just worked".


People print so rarely nowadays, it's more economical to go to the FedEx office on the occasions when you need something printed out than to buy a printer and ink or toner.


Open Streetmaps is a great project, but it doesn't include orthophotography. Even if they were using it, it wouldn't fix the errors with missing or blurry images, cloud cover, or rubber sheeting errors.


Of course they'd have to get the satellite data from elsewhere (though they couldn't do much worse than the stuff they have frankly), but the vector data and POIs would have been a good start, and probably more accurate and complete than what they have, at least in some countries. They would probably always have to buy satellite imagery.

I'd rather have seen more focus on getting the basics right, even if it meant they had to leave out (for example) satellite imagery in the first iteration. As it is they have broken satellite data, broken street mapping, and incomplete place names.

If they had chosen to back an open project like this they could have had a team of people worldwide fixing their maps for them, rather than trying to collate and correct thousands of bug reports from around the world and push them out in revisions. I wouldn't like to be on their mapping team over the next few months :)


I was under the impression that Apple did make use of Open Street Maps.

http://www.theverge.com/2012/6/11/3078987/apple-tomtom-opens...


They're not using OSM data most of the time, I suspect it's just for a small amount of data - the OSM credit is a tiny one amongst a whole load of others on their credits page for the maps app.

http://gspa21.ls.apple.com/html/attribution.html

It's not clear exactly where they get all the data, and what is used where, but simple searches like Paddington Station are not working (Paddington does, but not Paddington Station), and I'm sure they're not using the OSM vector data (in the UK at least) as it differs and is less complete than OSM in rural areas for example.

It would be interesting to know just how they've put their datasets together and what they used from where, but it looks like they use tomtom map data in the UK (along with Yelp places, and perhaps Royal Mail addresses/postcodes).


OSM is only comparable to commercial data in Europe AFAIK, and there, only in some places.

It's not surprising that densely populated areas in Europe/UK are complete and accurate in OSM.


It's actually pretty good in some quite remote places, but like all mapping the coverage does vary (see examples elsewhere in this thread of remote places). Probably some countries they'd have to either fill in with commercial data, or sponsor efforts to add data to OSM.

The main advantage would be that OSM has all the adding/editing/updating stuff down - that is a major operation and if Apple are trying to do it all themselves while merging inconsistent data from several sources and taking care of customer complaints they'll find themselves falling farther and farther behind people like Google who have devoted years and years of effort and a lot of money to this just to get where they are now.

Perhaps Apple considered OSM as a basis and decided it was just too limited in areas that were important to them - it would be fascinating to find out about their internal tools for this and where the data came from but I suppose we'll never know.


It seems like the quality level maintained by Steve Jobs is quickly deteriorating in favour of business moves designed to wrest more control off Google. They are operating in a very similar way to other companies now.

Google executives must be laughing very hard right now. If I was Google I'd avoid releasing a Google Maps application for at least a year and let the Android handset manufacturers ruthlessly exploit Android's superior maps.


> It seems like the quality level maintained by Steve Jobs is quickly deteriorating in favour of business moves designed to wrest more control off Google.

This stuff gets so tiresome. Apple has been buying maps companies for years. Steve Jobs personally ran acquisitions at Apple. He decided which mapping companies to buy and when he did he probably had a good idea of how they would fit into the platform. Development of the new Maps app was surely underway when Jobs was still alive. What do you think happened? Jobs died and the executive team was like, "Alright everyone, we've got 6 months until the iOS 6 beta is out. Let's cancel our contract with Google and get this shit maps app in there pronto!"

The reality is that Apple has been dependent upon their biggest competitor for a strategically important smartphone feature. The Wall Street Journal reported[1] months ago that Google initially balked at letting Apple have access to Street View, and didn't allow Apple access to turn-by-turn data. If the issue was only quality, Apple could have turned to Bing or Yahoo. They didn't because owning this technology is a strategic necessity in the smartphone market as it stands today. Having features dictated by competitors is not an option.

It's true that the quality of the maps app isn't great. I get looney search results (even when tapping on their search suggestions) and it's extremely frustrating. But there is something to be said for getting it shipped and starting the process of refinement and improvement. It only becomes a strategic problem if the quality doesn't improve noticeably with time.

[1] http://webcache.googleusercontent.com/search?q=cache:FwvSLvr...


It's not that tiresome. Jobs would have clearly done things differently. He would have either 1) paid retail prices for Google Maps API access until Apple could build a shippable product, or 2) Gone on stage and painted Google as a big evil bully who was stealing good Maps from iPhone users -- the media headlines would read "Google Reneges on Loyal Apple customers" or something like that. Notably, the second option is not available to Tim Cook.


> Jobs would have clearly done things differently.

What's almost as tiresome as the now persistent refrain of "this wouldn't have happened if Steve was still alive" are claims to know what Steve would have actually done if he were still alive. Your second option is ridiculous on its face.


Look at what happened with the iPhone 4 antenna issue. He just went on stage and said, "This isn't that big of a problem, and if it really bothers you, put it in a case." That is clearly not an option for Steve Ballmer or Larry Page in the same situation.


> Notably, the second option is not available to Tim Cook.

But they could just send in Forstall, he could easily do it and get away with it.


In that case, I'm glad Tim Cook handled it the way he did. I'm an Android user who would be happy to see people checking out Android 4.0, 4.1 and finding out that it's much better than what they think they know of Android.

At the same time, I totally respect and get why Apple did this. I applaud competition with Google Maps (I'd love to see OSM become a success too).


>> It only becomes a strategic problem if the quality doesn't improve noticeably with time.

The negative PR and reduction in the quality of the core experience might cause a reduction in sales or consumer opinion of Apple.

>> What do you think happened? Jobs died and the executive team was like, "Alright everyone, we've got 6 months until the iOS 6 beta is out. Let's cancel our contract with Google and get this shit maps app in there pronto!"

Your assertion that Apple had a choice between owning strategic maps technology or licensing from others is incorrect as they are not mutually exclusive.

I have to say I don't think it's a smart strategic move -- somebody has acted on a false dilemma and as a result reduced product quality. As you pointed out yourself, Apple could have gone to Microsoft or Yahoo to retain quality or they could have fought harder with Google to keep the contract for a while longer. It was not a bad strategic decision to buy maps companies and to put R&D into creating their own maps solution, however it is a bad decision to release Apple maps in this state.


> The negative PR and reduction in the quality of the core experience might cause a reduction in sales or consumer opinion of Apple.

Could be. Remember though that they also added at least one notable feature (turn-by-turn), so it's more like 1 step forward and 2 steps back rather than just 2 steps back.

Also remember that Apple took a pounding for the whole antennagate thing, to the point where Steve Jobs had to hold a news conference to get everyone to calm down. That was an issue that "regular people" knew about. (I was asked by people at a bar if the iPhone 4 I had at the time had reception issues, for example.) And yet, Apple sold a ton of iPhone 4s, and no long-term damage was done to the Apple or iPhone brand.

So I don't think it's a foregone conclusion that this will cause long-term problems. However, it is important for Apple to improve their maps data quickly.


> Development of the new Maps app was surely underway when Jobs was still alive. What do you think happened? Jobs died and the executive team was like, "Alright everyone, we've got 6 months until the iOS 6 beta is out. Let's cancel our contract with Google and get this shit maps app in there pronto!"

No, I'm sure SJ wanted to get way from Google. But I doubt he would have let Apple release iOS6 maps in the state they're in if he were still in control.

Maybe they should have kept it US only and still use the old Google one for outside the US, as that seems to really be where the quality issue is with the data.


Yahoo is using Nokia's API and Bing is in the process of doing the same thing.


And you came to this conclusion based on one bad app? Quite the leap it seems.

What's missing in all of these conversations is that Apple's contract with Google for mapping ended this year. No one knows what really happened for Apple to make this change.


And you came to this conclusion based on one bad app? Quite the leap it seems.

This isn't about "one bad app," it's about a core smartphone app that everybody uses. That's why so many people are complaining and the story is kicking off all over the place.


I've been using ios 6 maps since beta1, yeah its new, but to wit I don't use transit directions and in a direct comparison with android google maps, ios 6's maps worked fine.

This is in many ways who moved my cheese. I don't care if Google or Apple (who made the google maps app pre ios6 anyway using google apis) is responsible for the old maps app not being on ios6. If google wants their app on the apple store they can submit it.

If apple denies it thats another matter and not worth arguing right now.

ios6 is so much better than 5 overall I think you're being somewhat overly dramatic about one app. Yes it feels rushed, but its likely this is a stopgap due to contractual problems.

And besides, these are just phones. People are so up in arms about this its getting to fever pitch levels. Why everyone expects perfection from the start is beyond me. Its a start, and not yet perfect for everyone. Either it gets better and all this complaining was just for pageviews (most likely), or people actually vote with their wallets and switch.

Until that switch happens, these arguments are getting tiresome and to be honest aren't very constructive.


Apologies, I wasn't trying to represent what I said as fact hence the word "seems". However, I do feel that this has been a very lacklustre update from Apple...

I think it would have been worthwhile to keep the contract with Google (even if it's expensive) while investing in making a better Apple Maps app.


> No one knows what really happened for Apple to make this change.

I find it very unlikely this move was prompted by Google. Honestly, it looks positively amateurish the way the change was implemented by Apple.

I will admit it will drive my next phone purchase: Maps are my #2 usage after mail, I very much depend on it to get around.


Navigon for IOS TomTom for IOS www.google.com/maps in IOS

Take your pick. There are solutions that can be used to work around this issue and meet your needs.


I think this idea that every product Steve Jobs released was 100% quality is largely wrong – people just choose to only remember the hits. Apple has always released early - largely polished, but rough around the edges. Remember the early days of OSX? tons of loose ends. The first iPhone? definitely had stability issues, missing huge core features e.g. MMS. AppleTV? Ping? XCode 4?


Yeah. Maps is one of the most important smartphone apps. They might have just handed the market to Droid.


Android already has market share, this will just widen the gap.


If this had any truth to it, Android would have already walked away with the market due to the iPhone's longstanding mediocre Maps app.


It's just too bad Jobs is dead and is not here to personally fire the apple maps team.


Or, Google can release their Map application ASAP and try to build more of a foothold in the iPhone market. I guess then they would have to fear Apple rejecting their app when the time is convenient.


I'm pretty certain that Google won't be able to release a Maps App for iOS because it would violate the terms of replicating built in functionality. People can use the mobile web version, though.


> more of a foothold in the iPhone market.

More of a foothold? They already had virtually 100% (I'm exaggerating, but I can't think of anybody who used anything else for maps).

They don't have any incentive to make life easier for iPhone users. They have an incentive to remind iPhone users how they're really dependent on Google, not [just] Apple.


So I've been seeing all this hatin' on HN this morning so I figured I should check it out on my device. I mapped my commute (1 hour) and the only oddity I saw was the waviness coming off of a bridge. Beyond that Philly's buildings were all rendered correctly and my route was exactly the same as Google maps. YMMV

P.S. I must say It was really cool to see Cira Centre (The Amtrak Building) rendered in 3d. http://en.wikipedia.org/wiki/Cira_Centre


Try living somewhere that isn't a big US city. Of course the major population centers are going to be highly worked on. It's elsewhere, that google maps has gotten so good on, that people are complaining about.

The satellite imagery is as bad as googles was, but more than six years ago.


Actually, even in big US cities results are really bad in some cases. in Seattle, for example, searching for common well known intersections brings up results halfway across the country.


I hit a maps link for a restaurant in the Maryland suburbs of DC, which had latitude and longitude in it, and it still took me to the wrong place. Removing the restaurant name and just leaving the lat/lon showed the right place, but of course I didn't figure this out until I had already driven past the wrong place and wondered where the restaurant was.

It's just atrocious. OK, so you have some bad POI coordinates, that's bad but somewhat understandable. But how do you prefer your bad POI data to the correct coordinates that you're given? It boggles the mind.


For rural ND, it looks like Apple's maps are about 6 - 9 months closer to current.


What actually bothers me the most, is poor quality of iOS6.

It has several bugs (excluding maps and unfortunate wifi bug), which already have affected me and users around me. Some most notable include following.

* Sometimes iTunes update screen does not refresh,

* You can't disable vibration for notifications per application (i love my email in notification center, still - i do not need it to vibrate; in 5.1 it worked).

* Also, phone from time to time vibrates, though nothing has happened (no new notifications or alerts).

* Most annoying one is that they changed keyboard input, so you can't enter special characters (common in Latvian) by holding and swiping left/right. You have to swipe up and then left/right. Makes big deal, when typing.

I know it all will be fixed in 6.0.1, but still - there is visible decline in quality of provided software, which actually makes me very sad as a user.


Apple's 1.0 release are always kind of buggy. I remember iOS 5.0 was really buggy, and OS X 10.X.0 releases are notorious.


To be honest, despite its flaws, it's going to be ok for most of the people, most of the time. Navigation is going to be a big boon. Using it I haven't noticed major differences personally. Some restaurants are in the wrong location, but on the flip side I like the yelp reviews. I'm sure they will improve on the areas that are flawed.


Directions being ok most for most people, most of the time, is hardly acceptable.

Google Maps had a tendency to drop pins for locations on the wrong spot. That meant I always had to confirm the location with street view, 100% of the time.

Going to the wrong spot can be catastrophic in some instances (wrong or non existent hospital.) In others it can be really bad (missing a critical meeting, walking in during a wedding.) I don't need to give more examples.

Google giving not so great search results is one thing. I can look at the page and quickly tell that its wrong. When maps are wrong, it can add another 30 minutes between figuring out you went to the wrong spot and getting to the right one.

If Apple's management thinks its acceptable to roll out beta products on all of their users, I'll be moving to Android.


  > If Apple's management thinks its acceptable to roll out
  > beta products on all of their users, I'll be moving to 
  > Android.
Sure - because Google never rolls out beta products on all of their users...


A good point for sure.

I think his reasoning is that, if all the options are going to be beta-level products, he might as well use Android. I think Apple has always implicitly presented a deal where they tightly control their phone, but the experience is excellent. You don't care who makes the maps app because it "just works." If that's changing, users might be happier in an ecosystem where choice is more pervasive.


> Apple has always implicitly presented a deal where they tightly control their phone, but the experience is excellent.

That, IMO, is absolutely the deal you make with Apple. More money, less hackability, and better experience.

If Apple starts crapping out stuff, there's no point in buying Apple.


Difference is, it generally says, "Beta" right on the tin.


Directions being ok most for most people, most of the time, is hardly acceptable

Directions that are perfect for everyone, all of the time? Has that ever happened? I don't think so. I think it has always been a steadily improving mess. This may be a step backwards, but let's be realistic, here.


> wrong or non existent hospital.

FWIW: I can see that turning into a lawsuit.


Google's Maps TOS states[1]:

4. Content in the Products. (a) Map data, traffic, directions, and related Content are provided for planning purposes only. You may find that weather conditions, construction projects, closures, or other events may cause road conditions or directions to differ from the map results. You should exercise judgment in your use of this Content.

And Apple's iOS6 License agreement states[2]:

5. Services and Third Party Materials. (e) Neither Apple nor any of its content providers guarantees the availability, accuracy, completeness, reliability, or timeliness of stock information, location data or any other data displayed by any Services. [...] Location data provided by any Services, including the Apple Maps service, is provided for basic navigational and/or planning purposes only and is not intended to be relied upon in situations where precise location information is needed or where erroneous, inaccurate, time-delayed or incomplete location data may lead to death, personal injury, property or environmental damage. You agree that, the results you receive from the Maps service may vary from actual road or terrain conditions due to factors that can affect the accuracy of the Maps data, such as, but not limited to, weather, road and traffic conditions, and geopolitical events. For your safety when using the turn-by-turn navigation feature, always pay attention to posted road signs and current road conditions, and follow safe driving practices and traffic regulations.

There's basically no difference between the two. If the argument didn't arise when Google released their Maps product, or when MapQuest released their product, then there's no reason to be making the same argument against Apple for their maps product. The idea that someone will use Maps to get to a hospital and end up dying or becoming severely injured because they were told to take a left at Alberkerky and got lost is pretty weak. We might as well start arguing about how US Republicans are going to kill grandma and US Democrats are going to redistribute your wealth because that argument has more of a chance of actually affecting the lives of people, but is still as much of a emotionally charged fallacy as maps causing injury or death.

[1] https://maps.google.com/help/terms_maps.html [2] http://images.apple.com/legal/sla/docs/iOS6.pdf


> There's basically no difference between the two.

1. There's more to contract law than reading the contract. 2. There is a huge difference: Google gets the placement right, Apple does not.


There's basically no difference between the two.

It would be one thing if a search for a hospital on iOS failed by returning "Not found." It's quite another if the search returns an abandoned warehouse 6 miles away.

Good luck convincing a jury that this isn't negligence, especially when Apple knew very well that their data was garbage.


>I'll be moving to Android.

Google's Android? As in Google, the inventor of the "perpetual beta"?


As of right now the perpetual beta is a lot better than the supposed "final" iOS6 maps. So yeah.


But they don't usually revert in quality.


The Google Reader redesign fiasco? Google Wave to Google+ transition?

It's not like Apple "usually reverts in quality" either. This was a business decision, probably forced. They had to create something of their own for maps from what they could license and buy quickly.

Goes to show that you should not depend on your competitors for core technology. Which Apple always tries to avoid, but probably in 2007 (when the iPhone come out) the didn't think of Google as a competitor. They weren't in the phone business back then...


They weren't?

In what could be a key move in its nascent wireless strategy, Google (GOOG) has quietly acquired startup Android Inc., BusinessWeek Online has learned. The 22-month-old startup, based in Palo Alto, Calif., brings to Google a wealth of talent, including co-founder Andy Rubin, who previously started mobile-device maker Danger Inc.

-- BusinessWeek, August 16, 2005

http://www.businessweek.com/stories/2005-08-16/google-buys-a...


>They weren't?

Yes, they weren't. The first Android phone appeared one year after the iPhone (HTC Dream, released on October 22, 2008).

That 2005 acquisition didn't automatically make the two companies competitors...


And have you used Android lately?


Thinking that a maps app without transit and biking directions is "good enough", even if the driving and walking directions were accurate, betrays an extreme bias and disconnect with the way a lot of the world gets around.

For Apple's set of rich customers in the U.S., yeah, maybe driving and walking are good enough. But "most of the people" is a huge overstatement.


Uhh...Apple has plenty of customers in metro areas like the Bay Area or New York, Tokyo, etc. that rely heavily on public transit (I'm one of them). There are plenty of reasons to hate on Apple but stupid populist rage is not one of them.


I think it is less about the customers being out-of-touch with transit users and more about the decisionmakers and the developers...


It doesn't matter to customers whether or not the data will eventually improve - there are significant feature and quality regressions today that will cause delays in iOS6 adoption and directly work against the popular perception of their most important product. Everyone get their digs in now, because the titan doesn't stumble often.


Apple has been virtually printing money with the iOS products because they consistently, if incrementally, offered better and better products. Products that, for most users, offered a genuinely good to great experience and products that challenged the market to be better – far better – than they had before. This, as far as I can tell, is the first really big snafu in the user experience and that may be worrisome.

The thing is – and what the apple fans are all afraid of (but few may admit) is that this isn't just a stumble, but rather, the first major indicator of what a post-Steve Jobs Apple product experience is like.

Every good ride comes to an end – it's just a question of when and how.


> The thing is – and what the apple fans are all afraid of (but few may admit) is that this isn't just a stumble, but rather, the first major indicator of what a post-Steve Jobs Apple product experience is like.

I'm not afraid of it because it's bullshit. Where do we lay the blame for the YouTube app then? Or the huge engineering problems with the original MacBook Air? When Steve Jobs tried to kill iTunes for Windows and the App Store, how was he looking out for the user experience? I have little doubt the much-derided contacts app for Mac and iPad was a direct order from SJ. His influence was a mixed bag.

The only people who deify Steve Jobs' every move in Apple like that are people that aren't actually fans or aren't actually paying attention. Steve Jobs had a great vision, but he made bad decisions and good ones. As long as Apple is still doing exponentially better this week than last week, and they are, then the naive ones in this equation are the ones placing any amount of weight on "post-Jobs Apple" yet. We aren't even close to that.


I think you're missing the forest for the trees.

The first macbook air, despite engineering issues, was widely viewed as an amazing step forward for portable computing and it, echoing the iPhone, pushed the industry forward considerably.

Say what you will, it was still a major success and yet another feather in Job's cap, as viewed by the general public.

Don't think for a second that I'm saying Jobs was perfect in any way – but there is a general vision of Apple under his leadership as being the golden goose – Apple hasn't had a huge public fumble in the last decade that has been able to make its core customers question its ability to deliver ever increasingly good user experiences.

There have indeed been mistakes, but none of them have seemed to really injure the giant that is Apple. That generalized success has largely been credited to Jobs – with strong help from Cook and Ive. With Jobs' passing, it has been a real question as to whether Apple can keep that string of big successes and minor, if any, failures going.

What I'm suggesting is that if not fixed quickly, the maps experience downgrade will be viewed as a sign that post-Jobs Apple isn't the same and that may be dangerous for Apple.


I can't agree, I think mythmaking is unnecessary. Steve Jobs put his fair share of cold garbage onto the market.

Apple's bigger than anyone ever dreamed they'd be and they're the global standard bearer in smartphones. Any platform regression anywhere now affects millions of customers. The Mac is a piffle compared to iOS.

Edit: I will definitely agree that the fallout from this problem will be greater than any they've ever faced.

More

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: