5 ms·

Still, I have complaints about Google Maps on iOS (and they're blockers). 1.) You can't select a contact and find them on the map. This is just such a miss I

Still, I have complaints about Google Maps on iOS (and they're blockers). 1.) You can't select a contact and find them on the map. This is just such a miss I can't imagine why it's not there. Very likely due to non-technical reasons, because it's one of the major reasons I use a map. 2.) No vector maps. Probably the same reason. Offline caching of bitmap data is ok, but offline vectors scale so much better (zooming them doesn't break the map). I've driven out of the country and with no data service Apple Maps does a way better job of caching my map data giving me a "good enough" view of where I need to go. That said, Google Maps has way way better search, and with a jailbroken phone and the Google Maps default replacement thing it's pretty good, but even with those the two above reasons are why I stick with Apple Maps on iOS (if I can't find something I know is there I'll switch to gmaps).

boucher 13y ago
Both of these are are not true. The search field uses your contacts as a data source (though perhaps it works because I have synced with Google, I can't be sure). The maps are vector.
- Camillo 13y ago
  Contacts and history only work if you share them with Google. It refuses to use the local contact store.
  - fpgeek 13y ago
    What's the user experience around using the local contact store? It seems to me Google Maps would have to preemptively request permission to access local contacts because it wouldn't know in advance if a particular search should match a contact. And some people might be confused by the unexpected request and not understand why contact search isn't working later (or be confused if they disabled Google Maps' contact access because they didn't make the connection). I can certainly see how, from Google's perspective, it seems cleaner to use the contact store they know they have access to and is presumably the same one they'd use on other platforms - promoting consistency. Is that ideal for every user? Clearly not. But, in the spirit of the original article, it is probably the way to get contact search working with minimum friction for most users.
    - Camillo 13y ago
      Right now, when you tap the search field, Google Maps shows me a message saying that I should log into my google account if I want to use contacts etc.; and my contacts are not synced with my google account anyway, so it would either fail silently to find them, or it would try to sync them - which would require asking for permission to access my local contacts anyway. If it used local contacts and I had denied it access when it asked on the first startup, it could instead display a message saying so, offering a button to click to request access to contacts again. It would be strictly less complicated for the user.
- bentcorner 13y ago
  > The maps are vector. I guess I'm wrong about that then :). My assumption was based on the fact that when I traveled into areas with no data coverage, I distinctively remember Google Maps having great difficulty with cached map data, while Apple Maps didn't. (In the hotel prior to driving I would load both maps and directions in both apps, "click through" the directions to give the apps a chance to cache the data, and then go on my way - if I dicked around in Google Maps it tended to just not show anything, or a very very fuzzy view of where I was, whereas Apple tended to show a low-precision (but clear) view of where I was.)

boucher 13y ago

Both of these are are not true. The search field uses your contacts as a data source (though perhaps it works because I have synced with Google, I can't be sure). The maps are vector.

Camillo 13y ago
Contacts and history only work if you share them with Google. It refuses to use the local contact store.
- fpgeek 13y ago
  What's the user experience around using the local contact store? It seems to me Google Maps would have to preemptively request permission to access local contacts because it wouldn't know in advance if a particular search should match a contact. And some people might be confused by the unexpected request and not understand why contact search isn't working later (or be confused if they disabled Google Maps' contact access because they didn't make the connection). I can certainly see how, from Google's perspective, it seems cleaner to use the contact store they know they have access to and is presumably the same one they'd use on other platforms - promoting consistency. Is that ideal for every user? Clearly not. But, in the spirit of the original article, it is probably the way to get contact search working with minimum friction for most users.
  - Camillo 13y ago
    Right now, when you tap the search field, Google Maps shows me a message saying that I should log into my google account if I want to use contacts etc.; and my contacts are not synced with my google account anyway, so it would either fail silently to find them, or it would try to sync them - which would require asking for permission to access my local contacts anyway. If it used local contacts and I had denied it access when it asked on the first startup, it could instead display a message saying so, offering a button to click to request access to contacts again. It would be strictly less complicated for the user.
bentcorner 13y ago
> The maps are vector. I guess I'm wrong about that then :). My assumption was based on the fact that when I traveled into areas with no data coverage, I distinctively remember Google Maps having great difficulty with cached map data, while Apple Maps didn't. (In the hotel prior to driving I would load both maps and directions in both apps, "click through" the directions to give the apps a chance to cache the data, and then go on my way - if I dicked around in Google Maps it tended to just not show anything, or a very very fuzzy view of where I was, whereas Apple tended to show a low-precision (but clear) view of where I was.)