Hacker News new | ask | show | jobs
by TeMPOraL 2552 days ago
It's not just you. Google Maps seems to be stuck in this sad state of being almost, but not quite, good at being a map. Street names in particular seem like a low-hanging fruit that would vastly improve the UX, but for some reason, they don't do anything about it.
6 comments

I don't know for sure, but I think that's a problem that they had previously solved - I remember being impressed years ago by the fact that the street names always moved on zoom or scroll so they were always in view.

It seems like they've regressed for some reason.

Update: I did some testing and this still works for me - every time I zoom or scroll, the street labels move to remain in frame. Tried on Chrome desktop, iOS native app, and iOS Safari, same behavior in all three.
Just tried it in Chrome, Firefox, and on my phone.

Can't get the street name for the office that I work in. It's a big street here...but nada. Have to shift over a few screens to get the name to finally show up.

Obviously, I know what street I work on. But the problem is that this happens consistently whenever I have a location pin in GMaps (i.e., destination, etc.)--the street of the pin rarely shows up unless I play around with the view.

Street names is definitely borked.

I've never understood these street name complaints on Hacker News either. It's always kept the street names in the frame for me. If I zoom in a lot, it even starts repeating the street name over and over[1], getting denser and denser as I zoom in more.

[1] Example screenshot in Firefox today: https://i.imgur.com/BDa4Dr2.png

I'm not sure why or when. But I often find no matter how far I zoom into a street, it refuses to show me any street name. This is even if it's literally the only street visible on my screen.

I had this happen roughly two weeks ago on my iPad with multiple people around me all scratching their heads. I look at the same location today and I see the street name....

Same area, Google Maps on modern Android: https://ibb.co/18wVw9k https://ibb.co/84tsSYS

It kinda works, but it's not that hard or uncommon to get to a zoom/pan level where it breaks.

OK, so it's probably a browser vs. phone difference. Thanks for the comparison.
It doesn’t work very well in cities. Here is an example from DC. http://i68.tinypic.com/152ygx0.jpg
It happens when there are other points or an overlay. I think the buffer they put around text boxes suppresses the street.

In notice this on my street, as there’s a business, park and firehouse. Most of the time the street name is blocked. Also see it a lot in places like Queens with irregular streets with lots of points.

+1 for street names in view port. I tend to research the route and then put away the phone when I'm on my bike. What is the name of the street where I need to turn right?

Also, if I have to go straight ahead for a long time, the street names might change several times, but I don't care much. I'd rather know I need to go straight for 5km, than go straight for 100m, then go straight again for 800m ....

Perhaps Google's UX experts have decided street names are as important as call and SMS timestamp. That is to say, not important at all.
Even when street names are in view, they are often illegible: tiny font, overprinted on multiple lines & styling, etc.
Google doesn't need to go for any of the low-hanging fruit because their PoI data is still the best of the Google Maps / Apple Maps / Maps.me trifecta. Apple Maps is slowly improving their PoI and other data, but for mobile devices is only available on iOS.
"Google Maps seems to be stuck in this sad state of being almost, but not quite, good at being a map"

Perhaps this is a general phenomenon of our society that is increasing, being almost but not quite competent, because producing the "minimum viable product" is the most economically efficient approach and due to general improvement in data analysis and optimization, companies are getting better at substituting some exploitation of cognitive biases for unnecessary competence.