Hacker News new | past | comments | ask | show | jobs | submit login

To offer a counterpoint, I decided to start alternating between Apple Maps and Google Maps a few months ago and — so far — I haven’t been led astray by Apple Maps. I do live in L.A., however, which is probably among the best case scenarios for Apple Maps at the moment.

Google does have the better product, but for the most part I can see Apple Maps being at least “good enough” for my use, much the same way that Safari, for me at least, is “good enough” compared to Chrome. Unfortunately, anecdotes of Apple Maps underperforming are all too common, and I think Apple needs to keep investing (and probably a lot) if they intend to win users over.




The problem for Apple is why would anyone want to use "good enough" when the alternatives are better, free, and easily available?


If it weren't for the fairly deep tendrils Apple Maps has in iOS itself, or if it were possible to change the 'default' maps app to a competitor's, there wouldn't be a particularly compelling reason. As it is, however, using a third-party app sometimes means awkwardly copying and pasting addresses, not having a turn-by-turn map present on the lock screen and so on, so there are compelling reasons against using third-party maps apps.

These limitations are, of course, entirely of Apple's creation.


These limitations are really a byproduct of the deal falling apart between Apple and Google. Apparently, Google wanted access to more user data in exchange for adding turn-by-turn directions to Google Maps. They could not reach a deal, so Apple Maps was hastily created and Google Maps was booted from the default image.

In the end I can understand the limitations on the lock screen because it can be tricky to figure out the right way to give third-party apps special permissions like that. This is not some kind of tacked-on limitation that Apple added, but instead it's something that didn't exist on iOS until Apple added it. Remember that Google Maps, at the time, didn't give turn by turn directions at all never mind on the lock screen. Given how cautious Apple has been with the iOS permissions model (compared to Android, for sure) this shouldn't be even slightly surprising.

The fact that you can't make Google Maps the default handler is stupid, though.


> In the end I can understand the limitations on the lock screen because it can be tricky to figure out the right way to give third-party apps special permissions like that

Interestingly enough, I did some exploring into how Apple was doing this and it seems like there's already an (internal) "API" for bundles of code that work on the home screen and lock screen. Currently it's taken advantage of by apps like Assistant (Siri), ChatKit (I assume this is Quick Reply notifications?), Wallet (which shows up on the lock screen), and the Wi-Fi picker in addition to Maps. Check out /System/Library/SpringBoardPlugins if you're curious.


The amusing thing is that although Android theoretically allows you to change your default map application, no one would do that since Google Maps is installed by default, and it's so much better than anything else out there (as illustrated by the article above).


I don't understand why this would be a problem. Apple Maps is not competing with Google Maps. Apple Maps is simply there so Apple can provide turn-by-turn navigation out of the box without paying Google for it. The fact that Google Maps is free to consumers is irrelevant, because it's not free for Apple to bundle with iOS.


> Apple Maps is not competing with Google Maps.

Uhh, it 100% is. The fact that I don't use Google Maps and use Apple Maps instead means that it's in direct competition.


Maybe you're both right? I do think there's a different type of competition here. Apple has their own mapping app as a hygiene feature of their platform, whereas Google is building out Google Maps as a platform of itself.

I'm sure Apple would love it if you used Maps so much that it created ecosystem locking, but I doubt Apple is too upset that you downloaded Google Maps on your iPhone.


> because it's not free for Apple to bundle with iOS

Would love to see a citation for that. Wouldn't Google want to boost maps usage on iOS?


https://www.forbes.com/sites/timworstall/2012/06/09/apple-is... mentions that, and links to this: https://www.forbes.com/sites/timworstall/2012/03/30/google-m...

I didn’t follow all the links, but apparently this was referenced in a court case.


"better, free, and easily available" is variable, especially if you're in Apple's ecosystem.


The problem with maps is that in order to be reliable, they need to work everywhere - in familiar areas, people know where they're going; but it's the weirder parts where they start to really care about the accuracy of maps. It's not sufficient for you not to be lead astray in LA, the question is whether you're sure enough to rely on it when driving through a rural area in the middle of USA or on a business trip overseas to a country you've never been to - can you be sure that you can just type in your destination, follow the directions, and actually get where you should be even if you have no idea about any of the landmarks?


I can't be certain of that with any maps app. It's not as though I've never had the occasional problem with Google Maps, and even if I didn't, surety is an impossibly rare thing.

With Google Maps I feel I'd have greater confidence for its accuracy, but placing complete confidence in any maps app would be a mistake.


i so badly want apple maps to be good enough but it's not there yet. maps is the only google product i use regularly (i use apple maps maybe 20% of the time).

apple has hundreds of billions in the bank, so they could easily fix the problem if they wanted to. but they (mistakenly, imho) don't see it as core to their business so it limps along like it does.




Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: