5 ms·
> I don't get it: why hassle them over their underdog competitor? Laud them for daring to compete against the market leader. Focus the argument about the walled
by izacus 7y ago
> I don't get it: why hassle them over their underdog competitor? Laud them for daring to compete against the market leader. Focus the argument about the walled garden and right-to-repair instead.
Because they gave themselves an edge when competing against Google by not allowing Maps all of the same capabilities from start. And to do that, they abused their OS and store to block GMaps from having same capabilities as AMaps. Even today, GMaps isn't allowed to be the default maps provider.
No customer wishing for a healthy free market should approve of this.
- scarface74 7y agoThat’s not what happened. Google didn’t allow Apple to use turn by turn directions without Apple giving Google more telemetry from its users.
- greggman2 7y agoBut now Apple is disadvantages competing maps apps by making all maps links open in Apple Maps. It sucks. As a Google Maps user I have tons of labels and bookmarks in Google Maps. When I click a maps link in any iOS app I get shuffled over to Apple Maps and then have to try to find a way to manually copy the address over to Google Maps so I can add a bookmark and access it in other places.
- thu2111 7y agoThat's also not what happened. I was on the Google Maps team at the time and the issues were far deeper and more problematic than "not getting telemetry" which was at any rate, not an issue - what sort of "telemetry" do you think a Maps app could report that isn't search queries or tile requests? Maps apps are just rendering frontends for giant server farms after all. Claiming it's about telemetry is just Apple propaganda. The real problem was that Apple wrote the Google Maps app, and wasn't willing to cooperate with Google on it at all. Literally, they demanded some basic protocol specs and then wrote the app themselves. This led to several problems: 1. They refused to tell Google what changes they were making to their app, which led to: 2. Repeatedly screwing up their implementation in ways that very seriously threatened the stability of the entire Google Maps services (think: slamming the servers with way more traffic than any reasonable implementation should). Apple love to claim the best results arise from integrating hardware, software and services. Well, guess what, that logic works in both directions: by preventing even basic cooperation between the Apple team writing the GMaps app, and the rest of the GMaps team, they created massive problems. Especially because at this time Apple engineering had no serious experience with large online services ... MobileMe was a disaster ... and so they kept making basic mistakes no Google team would ever make. They also refused Google's help to stop making them. 3. The GMaps team was much larger and better funded than the iOS team, so iOS rapidly fell behind the featureset available on Android and the web. Google attempted to fix this by writing their own GMaps app, which Apple then blocked on the grounds it was competitive with their own (this was back when they had this policy). Basically the relationship was antagonistic from the start from Apple's side, and rapidly spiralled downhill as Google's own services accelerated away from what Apple was capable of. The whole Apple schtick that Google was desperate to violate privacy or get telemetry is just an advertising attack angle: it shouldn't work on the sort of people who read Hacker News. Apple Maps is architecturally identical to Google Maps, after all.
- scarface74 7y agoThe GMaps team was much larger and better funded than the iOS team, so iOS rapidly fell behind the featureset available on Android and the web. Google attempted to fix this by writing their own GMaps app, which Apple then blocked on the grounds it was competitive with their own (this was back when they had this policy) Since the integrated map apps didn’t have turn by turn directions, there were plenty of 3rd party apps that were in the App Store. I used MapQuest. This was during the iOS 4 era. Apple had a policy that no maps app could use turn by turn directions until iOS 3 or 4. I’m of course in no position to know the technical details of the Apple Maps/Google Maps spat. But the negotiations as far as licensing wasn’t happening on the engineering level - it was happening on much higher levels of the org chart. Are you sure you had the entire political picture?
- throwaway938693 7y agoI happen to know the other side of this. I get the impression from your post that we were probably looking at the same thing, just from very different angles. I think there were aspects to it that you either weren’t privy to or just couldn’t see from where you sat. I don’t think anyone involved in this from Apple still works there anymore, and it’s been 10-11 years now so probably not even Apple itself really knows all the details at this point. From what I’ve heard the same may be true at Google; these stories are basically folklore to the current crop of the Maps team there. In any case, as I recall it, advertising data and location tracking absolutely were sticking points. It’s possible you weren’t part of those aspects or you just saw it differently than Apple did. On the other hand, this was all before Apple had a public marketing campaign around user privacy. The antagonism in the relationship around Maps also predated any discussion with Google of location data or ads and it arose from Android. Jobs saw Android as an attempt to copy the iPhone, and this lead to mistrust of Google in all things. With that perspective, maybe you can start to see the other side of it. Apple didn’t want to let slip any detail of upcoming iPhone features because the concern was about them being copied in Android. While the G Maps folks gave lip service initially to being separate from Android and the idea that features wouldn’t be held back from Apple to benefit Android (and this was true initially, eg with Street View), Apple folks didn’t believe that would last. And I think it didn’t last. As time went on, the Apple perspective was that Google was asking for things that were anathema, just so Google could point to them and say this is why you aren’t getting vector data or nav, but only as a pretext in the larger war of being able to use Maps as a competitive advantage for Android.
- briandear 7y agoThe healthy free market can choose Android if they want.