That's every VC's dream isn't it?
I have no interest in seeing where the nearest McDonalds is, unless I search for it. POI markers for places I need to go (via bookings/appointments) are good, but POIs for places I have never been are bad.
For whatever reason I can never see the street name I want to see anymore. Between the excessive labelling, there is simply no space, and Maps decides to prioritise other labels instead of the STREET NAME.
When I am navigating, I really _really_ need to know the street name.
It's been this way for years, and it's my #1 gripe with Maps. It's particularly bad in a dense grid like NYC, where some streets only appear for a block or two. If Maps doesn't decide to print the name on that block...I guess I'm not allowed to know what street that is?
I vaguely recall reading about this on HN when it happened, and the consensus was that the logic for determining whether to print the street label had been changed for aesthetic reasons.
Peak form over function.
Anecdotally, I don't see any rhyme nor reason for whether it decides to show the street name or not. Oftentimes, it will value a side-street over the main street, and in _some_ cases this makes sense (e.g. you are on the larger street, and want to see intersecting streets), but Maps doesn't seem to read contextual clues... if I am not navigating, or zooming in from further away, showing larger streets first would be better.
I’ve worked on similar problems and it’s not the easiest to solve. And I’ve never solved it because it was never that important of problem to solve and we just moved on to the next issue.