Online maps get flashy

Flash smartypants Paul Neave has taken the public APIs of Google Maps and Microsoft Virtual Earth and built his own Flash interface to browse the satellite imagery offered by both of these services. And, may the JavaScript gods forgive me, it’s far smoother and more pleasant to use than either of the services’ respective Web interfaces.

For now, it lacks the flat maps, local search features, and other useful bells and whistles of the Google and Microsoft originals, but as a demonstration of what is possible with Flash as a frontend technology, it’s very effective. In particular, the ability to rotate the view is something that is a long way off in pure DHTML interfaces.

I wonder how long it will be before some enterprising folks attempt to produce a 2D clone of Google Earth in Flash. I’d be surprised if Google didn’t buy out such a project, were it to come to fruition.

Free book: Jump Start HTML5 Basics

Grab a free copy of one our latest ebooks! Packed with hints and tips on HTML5's most powerful new features.

  • http://www.sitepoint.com AlexW

    Yep, you have to admit, it’s pretty slick. Fast, responsive and has a nice glidey feel.

  • lepezdok

    That is pretty cool. Except for the CPU usage staying around 60% all the time while it’s on. That bothers me.

  • cw

    Hey Kevin…have you seen this video from the Virtual Earth folks? Pretty funny. http://www.virtualearthinfo.com/video.asp

  • Etnu

    It’s a bit smoother than the current implementations, but that’s pretty much only because it wasn’t until recently that javascript performance became important to web browser manufacturers. I fully expect javascript to perform 5 times faster than it currently does within the next 3-4 years.

    Of course, there are plenty of other problems with flash:

    1.) You have to install it. It doesn’t come with the browser.
    2.) Most applications take a long time to load (this one doesn’t, but the developer is much better than most flash developers)
    3.) Accessability is completely impossible.
    4.) Design is tied to the swf file. So much for separation of content from design.
    5.) Ever right-clicked a flash app? Yeah.

    I don’t think anyone was ever really doubting flash’s ability as a front end. The whole POINT of the hype around Ajax and such is that they allow us to achieve flash-like things without flash’s shortcomings.

  • tswalling

    I would say a few of those points aren’t completely accurate or could be argued against easily.

    1. Current numbers point to a 96% adoption rate for Flash 6 and about 90% for Flash 7. I pretty much don’t hear the concern over end users having to install a plugin. In the media services industry its pretty much accepted that Flash is a viable way to go and most people have it. For a comparison, several sources say that Javascript penetration is also in the low 90-95% range. That’s pretty much the same as Flash.

    http://www.macromedia.com/software/player_census/flashplayer/version_penetration.html

    2. Can’t say much here. I guess it depends which apps you’re seeing. I wouldn’t generalize all Flash apps as being slow to load though.

    3. Have you taken time to read all the accessibility features:

    http://www.macromedia.com/resources/accessibility/

    4. You don’t know how the developer built the swf. You can very much so seperate content and design. It’s all dependent on how the developer wishes to build his/her flash app. I’ve built apps that are completely OO oriented, are data driven and skinable via xml markup. Flash also supports CSS with its textfield styling. Many options here. Just because its delivered in a swf doesn’t mean the content, business logic and design isn’t seperate.

    5. Not really sure what the point is, so I don’t know what to say but here goes: As a flash developer you can define whatever menu items you like in the right click context menu so if you’d like to put a “view source” option or a “save as” option, feel free. Many people in the opensource flash community are doing it now as a way of distributing source code.

  • Draconian

    Etnu:

    I have no idea what your employer does with its time, but for most companies that prioritize making money, 3-4 years is a lifetime.
    Plus, concidering the fact that JS differs from browser to browser (and most likely allways will), Flash has an advantage over JS: If it works on one client, it works on all others as well.
    That makes for an easier (cheaper) production/testing cycle.