This article makes a legitimate point about the maps application. But I don't get the strange tangent on Google+ — why would anyone expect Apple to anoint the social network of a competitor which isn't even that popular?
How Apple's Obsession with Google Is Hurting Apple
21–30 of 141 posts
Re: How Apple's Obsession with Google Is Hurting Apple
#22First, to get it out of the way: People are very right in mocking Apple. They deserve every bit of that. What they delivered with their Maps app is embarrassing. I do not want to defend that. The problem, however, is that this article assumes something to be unequivocally true even though we do not know whether it is: That Apple decided to build their own maps in order to hurt Google. It takes two to play. Both Apple…
We have good evidence for turn-by-turn, though: when Apple decided "ok, we cave, here's an SDK and an App Store", the contracts with developers had a weird clause saying you couldn't build a turn-by-turn application that was later changed to only that you could not build a turn-by-turn application using the data that Apple had licensed from Google; while this isn't for certain, the obvious interpretation of this is t…
...the obvious interpretation of this is that when Apple built the iPhone they licensed Google Maps but with the clause "the iPhone cannot do turn-by-turn"
This is from Google's Maps/Earth API TOS:
10.2 (c) No Navigation, Autonomous Vehicle Control, or Enterprise Applications:
(i) real time navigation or route guidance, including but not limited to turn-by-turn route guidance that is synchronized to the position of a user's sensor-enabled device.
- https://developers.google.com/maps/terms
As far as I know, that clause has always been in the TOS (I looked into the licensing in 2010 and it definitely was in there then).
Re: How Apple's Obsession with Google Is Hurting Apple
#23I'm afraid the obsession is not on Apple over Google but on the media and blogs over Apple and every single thing they do. Of course Apple will watch its competitor closely, especially since both are now headed in same direction. And of course they need competing services. Likewise, I'm sure that Google is watching closely every move Apple makes. But nobody in their right mind would say Google has an "obsession" with…
Google maps sucked when it first came out. It will be fixed and both applications will improve. I think this is will only turn out two awesome map applications rather than just relying on google for everything.
Really? I remember when I first used Google Maps coming from being a Map Quest user, I was blown away that I could scroll without having to refresh the page.
Re: How Apple's Obsession with Google Is Hurting Apple
#24The historical revisionism among the Appleistas is a bit disconcerting. This is not a matter of the "suits" overruling Jobs' "pirates". Apple's current anti-Google jihad is Jobs' baby. This is what he wanted. Now, it's entirely possible that he would never have authorized iOS shipping with a broken maps application, but to suggest that Apple's current direction is anything other than his idea and his impetus is naive…
What worries me is that while Jobs was the one to turn the holy war on, he may have been the only one who could have turned it off again. One of his greatest strengths was his ability to believe something incredibly strongly, but then to change that belief quickly (and, at times, mercurially). Jobs's war on Google would have been hot and nasty, but I think he would have moved on to other things after a while. I worry that the remaining leadership at Apple sees this war as their memorial to Jobs, and will take it far further than might be prudent.
Re: How Apple's Obsession with Google Is Hurting Apple
#25First, to get it out of the way: People are very right in mocking Apple. They deserve every bit of that. What they delivered with their Maps app is embarrassing. I do not want to defend that. The problem, however, is that this article assumes something to be unequivocally true even though we do not know whether it is: That Apple decided to build their own maps in order to hurt Google. It takes two to play. Both Apple…
We have good evidence for turn-by-turn, though: when Apple decided "ok, we cave, here's an SDK and an App Store", the contracts with developers had a weird clause saying you couldn't build a turn-by-turn application that was later changed to only that you could not build a turn-by-turn application using the data that Apple had licensed from Google; while this isn't for certain, the obvious interpretation of this is t…
It is worth noting that Google themselves didn't offer turn-by-turn directions until Android 2.0 (October 2009). Interestingly, Google Maps Navigation launched in the US shortly after they had ditched Tele Atlas (owned by TomTom) as a US data provider. It was speculated (though not confirmed, as far as I could find) that Google ended the relationship because it was too expensive/restrictive with respect to turn-by-turn navigation.
That makes me wonder if original turn-by-turn restrictions were Google's idea or a requirement of Google's existing contracts. If so, it's obvious Google decided to continue those restrictions for their own reasons and so history has repeated itself.
Re: How Apple's Obsession with Google Is Hurting Apple
#26The argument that Apple needs their own map for strategic reasons is fine, but it doesn't explain why they needed to ship it before it was any good. I can imagine three explanations: (1) They think they need to start gathering user-generated map content. "Add your business to Apple Maps if you want iPhone users to find it." (2) An internal struggle at Apple. If the supporters of the maps project thought it was at ris…
I think "why did they ship the new maps app before it was ready?" is the most interesting question about this whole debacle.
I don't think they actually gather user-generated map content via iOS maps, so (1) doesn't make much sense to me.
(2) strikes me as weird reasoning. If there's a good argument that Apple needs their own maps, enough to justify the acquisitions, it doesn't seem likely that the project would get dropped.
I don't think (3) makes sense: they cut out critical functionality like public transit in directions. I don't see a reason to ship something which reduces useful features unless there was a very compelling reason.
I think the most likely reason was actually pressure of some kind from Google's side.
Re: How Apple's Obsession with Google Is Hurting Apple
#27The historical revisionism among the Appleistas is a bit disconcerting. This is not a matter of the "suits" overruling Jobs' "pirates". Apple's current anti-Google jihad is Jobs' baby. This is what he wanted. Now, it's entirely possible that he would never have authorized iOS shipping with a broken maps application, but to suggest that Apple's current direction is anything other than his idea and his impetus is naive…
According to the Appleistas, it still counts as "thermonuclear war" if you detonate the nukes over your own cities. Keep calm and carry on!
(Insert joke about the 3D maps.)
Re: How Apple's Obsession with Google Is Hurting Apple
#28How do we know this is Apple trying to hurt Google? How do we know this isn't Google trying to hurt Apple?
The fact that this sucks so bad for Apple's users and seems to be a net positive for Google would seem to indicate it is likely to be otherwise. The fact that Apple extolled the virtues of its map is immaterial. Of course they are going to do that.
Re: How Apple's Obsession with Google Is Hurting Apple
#29Earlier quoted context omitted.
Are you serious? What do you call the patent war between Samsung, HTC and every manufacturer of Android phones and Apple besides a proxy war?
It's overblown because if Apple were really upset at Samsung they wouldn't be supplying parts for iPhone 5. Remember, according to court filings Apple approached Samsung first to try to settle it before resorting to legal means.
Happening already:
The Korean Times is reporting this morning that "Apple has reduced purchases of liquid crystal display (LCD) panels for tablet computers from Samsung Display amid the deepening patent disputes, said a leading market research firm, Friday. Market experts said that the move is aimed at minimizing its reliance on Samsung parts."
http://www.patentlyapple.com/patently-apple/2012/09/apple-cu...
Re: How Apple's Obsession with Google Is Hurting Apple
#30Earlier quoted context omitted.
We have good evidence for turn-by-turn, though: when Apple decided "ok, we cave, here's an SDK and an App Store", the contracts with developers had a weird clause saying you couldn't build a turn-by-turn application that was later changed to only that you could not build a turn-by-turn application using the data that Apple had licensed from Google; while this isn't for certain, the obvious interpretation of this is t…
...the obvious interpretation of this is that when Apple built the iPhone they licensed Google Maps but with the clause "the iPhone cannot do turn-by-turn" This is from Google's Maps/Earth API TOS: 10.2 (c) No Navigation, Autonomous Vehicle Control, or Enterprise Applications: (i) real time navigation or route guidance, including but not limited to turn-by-turn route guidance that is synchronized to the position of a…
While true for the average developer, I would imagine a deal brokered between bizdev teams would look drastically different than those ToS.