Announcing the full roll-out of the updated Google Maps for desktop(productforums.google.com) |
Announcing the full roll-out of the updated Google Maps for desktop(productforums.google.com) |
I have to believe, based on my what I would consider my own moderate google maps power users perspective, that fewer than 1% of google maps users will have any issues with this change.
o Measure distances in google Maps (and put a nice marker on the screen)
o Get the Long Lat for any point on a map.
The thing is - I don't actually know why they are so upset, because they are, for the most part, not really calling out what their issues are, and the ones they have, seem kind of minor, like Missing a zoom bar.Some of their rants are about things that exist (showing distance bars in Metric or Imperial, on the screen)
And some of them seem really, really niche: "Photo icons placed at the location of the photo overlaid on the map, and not in some useless "carousel" feature."
Some of them seem wrong, "Autocomplete not working" - sure works for me. To a spooky degree that makes me wonder how it knows from "St. R " to automatically fill out "St. Regis, Singapore" - I mean, yes, that's what I wanted, but seriously, WTF - how did you know?
Anyways, I'm guessing that their user interaction surveys have shown that nobody except the die-hard classic maps users will care. I wonder if there was a similar uproar when Apple decided to shut down aperture, and move to photos. Probably not, as all the people who cared had probably switched to lightroom a long, long time ago - and the ones left on aperture are probably going to be totally happy with Photos. (raises hand)
- Classic maps is great on all devices New Maps sucks when there is a lower power CPU? Slow and laggy
- Why is there a Honking big Search box Hiding my map
- AutoZoom that randomly decides that a "drag action' is a Zoom
- Where are my previous searches? Why do they show up at-Most one at a time?
-- On and on
This is truly a step backwards.
And I'm not talking about departure/arrival times here. Just basic routing from point A to point B.
I'm not sure what's going on with their setup, but that's my only real complaint.
Apparently Google engineers are using top of the line hardware and nobody is aware of the issue. Looks like some dogfooding is required. :)
Haven't been able to find any comments that mention the API, so I'm hopeful it will be a transparent switch.
I know the team will get there, I cannot fully support their decision to disable old maps but I can understand it. Most of flame in that thread is unfortunate and unnecessary and reminds me of this comic where in the first panel someone introduces a new feature, the customer complains and moans, and say the first version was good enough, then the next panel they introduce yet another version and it's the same behavior as the first panel, they want the one that is just about to get taken from them, always and forever.
The problem with that is a statistical logic one. The majority of people will use a rare <1% feature occasionally. When the feature isn't there the user finally realizes how dumbed down the product is and that it doesn't fit their needs. Even if it fit their need for years it let them down when they needed it most. The PM will respond that it wasn't worth it to have the feature uglyfying the interface for years just so it was available that one time.
I too previously had a complaint about the peg man being removed. It was impossible to find the street view I needed without that.
It pops up when you query directions.