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

That's true about San Francisco versus Francisco San but I wonder how well Apple Maps does with "4485 Belmont Portland" versus "Portland 4485 Belmont" and the like.

It gets more complicated when you realize "oh, yeah I need to add 'NE' because it's in the Northeast part of the city". So now it's "Portland 4485 Belmont NE". If you were to think about it before you started typing, it'd be "4485 NE Belmont Portland" but correcting on a phone is so painful that you want to just keep typing.

I'm using a Galaxy Nexus and have been very happy with the standard Maps app. Last weekend the family was walking on trails and it got us back to the trailhead using walking directions. Neat. I've been less than thrilled with how poorly the phone seems to do with finding and keeping a GPS signal, particularly in a car on the freeway in areas I don't know.

Ah, Portland is lucky. Here in Seattle, we have roads that are 1235 NE 40th St (for E-W streets) as well as 12345 University Way NE (for N-S avenues). The latter, as you would suspect, totally breaks Apple Maps.

That is on top of the issue of searching for something like "1st and University", which takes me to some L'ecole in Paris, France rather than the intersection that is a block from me. It's as if they don't factor in your current location at all. I know on the desktop I frequently look at maps of faraway places, but I'd suspect that people tend to look for things near them while on mobile devices.

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