{"id":41409,"date":"2023-12-11T14:59:19","date_gmt":"2023-12-11T19:59:19","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=41409"},"modified":"2023-12-11T14:59:39","modified_gmt":"2023-12-11T19:59:39","slug":"google-maps-in-late-2023","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2023\/12\/11\/google-maps-in-late-2023\/","title":{"rendered":"Google Maps in Late 2023"},"content":{"rendered":"

Tim Hardwick<\/a>:<\/p>\n

When users get directions for driving, walking, or cycling, Google Maps now offers a “multidimensional experience” that can be used to preview bike lanes, sidewalks, intersections, and parking along the route, according to Google<\/a>.<\/p>

A time slider can be used to see air quality information and how the route looks as the weather changes throughout the day, while AI and historical driving trends simulate how many cars might be on the road at a given time.<\/p><\/blockquote>\n\n

Jack Wellborn<\/a>:<\/p>\n

\n

Launching its own mapping service was Apple’s biggest gambit in its war with Google, way more than any lawsuit. The lawsuits were about iPhone verses Android and while many Android device makers did borrow liberally from iPhones and iOS<\/a>, it turns out Apple’s fight with Google wasn’t really about one phone platform versus the other. It was about platforms versus services, and which one might commoditize the other. Up until Apple Maps, Google had the undeniable upper hand because it was a win-win for them as long as Apple had to use its services. Google would certainly win more if everyone suddenly started using Android, but they still won even if people stuck with iOS.<\/p>

[…]<\/p>\n

Google would not be paying billions of dollars annually to be the search default in Safari if Apple needed something equally as important from them. The only thing Apple truly ever needed from Google was mapping data. With its own mapping data, Apple no longer needs anything of significance, and so Google has to pay.<\/p>\n<\/blockquote>\n\n

Elizabeth Laraki<\/a> (via Hacker News<\/a>):<\/p>\n

Last week, the team dramatically changed the map’s visual design.<\/p>

I don’t love it.<\/p>

It feels colder, less accurate and less human.<\/p>

[…]<\/p>

Admittedly, I do think major roads, traffic, and trails stand out more now.<\/p>

But the colors of water and parks\/open spaces blend together.<\/p>

[…]<\/p>

So much stuff has accumulated on top of the map.<\/p>

Currently there are ~11 different elements obscuring it[…]<\/p><\/blockquote>\n\n

Darren Allan<\/a> (via Hacker News<\/a>):<\/p>\n

Google Maps now has gray roads like Apple, rather than white or yellow roads as before, and forests are a darker green.<\/p>

[…]<\/p>

These may not sound like massive changes – and to be fair, they aren’t, they’re essentially tweaks. But they have rubbed a number of users up the wrong way. As Android Authority<\/a> points out, there’s some quite spicy feedback on the new Google Maps on Reddit<\/a>, X (formerly Twitter)<\/a> and other online forums.<\/p><\/blockquote>\n\n

John Gruber<\/a>:<\/p>\n

\n

This is a very long way of saying that Google Maps’s app design should be like Apple Maps. In fact, Apple Maps has fewer<\/em> UI elements obtruding actual map content than she’s proposing for Google Maps.<\/p>\n<\/blockquote>\n\n

As I’ve said, I think the app<\/em> design of Apple Maps is better, but I preferred the map<\/em> design (colors, labels, decisions of what to shown when) of the old Google Maps. It’s frustrating that Google seems to be copying the wrong things from Apple. The new coloring perhaps looks nicer, but it’s less clear. Google Maps seems to be more aggressive about hiding street names that I want to see. I do still prefer it, especially for navigation, because of the way it draws street labels on the actual streets, instead of as horizontal bubbles that cover other parts of the map. Given that maps are now vectors, rather than pre-rasterized images, why can’t some of these details be configurable?<\/p>\n\n

Previously:<\/p>\n