Google Maps

Much has been said about the beauty of Google Maps and how enjoyable it is to be able to move the map around at will, zoom in and out, and switch between map view and satellite view. I love those features too, but I think the one indispensable feature is its speed. If it weren't responsive and quick in returning your results, no one would make Google Maps their primary choice for maps and yellow pages. When I'm looking for directions, I'm usually in something of a hurry. I don't want to have to muddle through a site or sit waiting for another dozen ads to load before I get my map. It's the same principle that made Google the number one search engine. They relinquish control to the visitor instead of trying to discourage you from leaving their domain.

As I'm reading 37signal's Defensive Design for the Web, it's clear to me that Google Maps has more to accomplish in the area of contingency design (that is, planning for all contingencies). It's probably already met or exceeded the quality of other map sites, but that doesn't mean it's good enough. For instance, if you're using Safari and you enter an address that Google Maps doesn't understand, it just reloads the page and doesn't give you any other feedback.

It is still in beta, so I anticipate these wrinkles will disappear soon. Beta status hardly means much with Google's creations though - the company may label them unfinished, but they're still becoming a staple resource on the web by prioritizing the customer experience above all else.