Google Maps: Under the Hood

Google Maps is apparently taking the triple-w by storm, and deservedly so. In a post from a few days ago, I wondered about the technology behind the drag-to-view map interface. SitePoint has the answer, albeit one fraught with acronyms and other tech references that will probably raise more questions.

The short answer is a combination of DHTML and CSS, but that's like saying that a Rolls-Royce Phantom is simply a collection of bits of metal, wood and plastic.

The SitePoint article makes a good point, however, in recognizing that as cool as Google Maps is, it has some significant drawbacks that keep it from being a universally useful tool. Some of the features don't work in all browsers (the drag-to-pan feature doesn't work in Safari, for example, although Google says that's coming soon), and the site isn't accessible at all in non-Javascript-enabled browsers.

In an ideal world, websites would be equally accessible to all browsers, or would "degrade gracefully" for the older or less-capable. But I have a hard time faulting Google for the approach it's taken with Google Maps. There are plenty of mapping alternatives, so it's not as though people are getting shut out of an entire class of service. When you consider that updated and fully-capable browsers are free, most people have a choice when it comes to staying with an outdated program. And today's cutting-edge technology often becomes the norm, and can even drive browser development to new capabilities. In the end, Google is to be commended for pushing the envelope with this new website.

Technorati tag:

Comments

Oh, oh how useful it would be to have a WAP version that I could get to from my Blackberry. Mapquest Mobile is outstanding, but much more finicky about how you present the search. With google maps, I can just throw it as much or as little info as I have, and it is pretty good about returning results.

Like when I have to tell it, "computer retail in kermit texas". (Might not be a big deal to YOU, but I'm a Dallas boy.)

Posted by: Phelps at April 14, 2005 11:09 AM

It's just a matter of time, amigo. A WAP version is inevitable, whether it comes from Google or via a third-party solution.

I'm still not sure that will help you with your Kermit problem, though. ;-)

Posted by: Eric at April 14, 2005 11:32 AM

And speaking of WAP, when am I going to be able to fire up the Fire Ant on my phone's browser?

After 7 PM it's just me and Sprint PCS out there on the 'net. No land line, no cable, no dsl, no satellite, no TV. Cutting ties to the MSM, year four.

The only regret so far was not seeing my favorite events live at the Athens Olympics. I got caught up daily through the 'net, so I really didn't miss anything.

Great blog, Eric! KUTGW

Posted by: Larry S. at April 14, 2005 05:22 PM

Larry, I wish I knew how to do a WAP version of the Gazette, not because anybody but you would use it, but I've always been curious about how that works. Maybe someday I'll set aside the time to figure it out.

And, thanks for the kind words!

Posted by: Eric at April 14, 2005 08:01 PM

Go Googling for Ajax -- the WSJ did a story about it as Google's underlying architecture for mail and maps and who knows what's next. In short, it's heavy on client-side javascript. I, for one, welcome that. I always thought javascript got a bad rap from the webheads.

Also, for WAP, try to find an MT cellular/PDA stylesheet. My Word Press install came packaged with one that detects the PDA browser, and I could email it to you if you want. I wouldn't read a blog on a phone, but obviously, some will. But note that WAP is dying -- hi-speed cellular is killing that particular one-off protocol. Nowadays, it's about small-screen presentation, and CSS handles that pretty well. If you want to read the interweb on a 2x3 screen, that is. heh heh

Posted by: Scott Chaffin at April 14, 2005 11:24 PM
Post a comment [Take your time...we're in no hurry.]









Remember personal info?