To be honest, my first impression of the new Google Maps design was how sluggish it seemed. My iMac has a quad-core Ivy Bridge Core i5, a dedicated graphics chipset and a 20-Mbps Internet connection, so I found that a bit disappointing. I didn’t think “resource intensive” would have implications for my current setup. It seemed a little better, though not perfect, using Chrome instead of Safari; Chrome also supports integrated 3D Google Earth mode (Safari is relegated to Lite mode). Performance is going to be something to keep an eye on; I hope they can optimize it.
Eliminating whitespace gives you a nice gigantic map, which is hard to consider bad in any way, but it does feel a bit overwhelming, like there’s too much map to process. Google keeps most of the map, except for major highways, dim for the most part, highlighting relevant content for specific uses—i.e., click on a location and nearest intersecting main streets highlight, ask for directions and exit numbers appear even at high zooms. It’s very, very subtle, something you might not notice. Much of the interface is moved from the sidebar to the map: Street View is accessed by clicking the road, for example—Pegman is nowhere to be seen.
Kenneth Field has some thoughts on the new maps, particularly in terms of whether Google has succeeded in creating personalized cartography. AppleInsider’s glee at discovering the same sort of image distortions that were called out in Apple’s maps last fall is plain for anyone to see.
Have you had a chance to play with it yet?