Google Abandons Maps for Adobe Flash/Air

Main menu:

Topics

Recent Posts

Feeds

RSS Feed RSS - Posts

September 2011
M T W T F S S
« Aug   Oct »
 1234
567891011
12131415161718
19202122232425
2627282930  

Past Posts

Java/Java EE

JDBC

Other

Google Abandons Maps for Adobe Flash/Air

September 21st, 2011 by Scott Selikoff

On September 2, 2011, Google announced it was deprecating the Google Maps API and actively encouraging users to migrate to JavaScript Maps API v3. While abandoning support for the Flash API comes as a bit of a shock, it is not completely unexpected, as Google has not released an update for the API in the last year and support for issues related to the Adobe Air version had deteriorated. As a silver lining, Google’s depreciation policy indicates the product will continue to function for three years until September of 2014.


Disappointed with Adobe

As JavaScript has radically evolved over the last few years, it is understandable that Google wants to settle on a single, browser-independent platform for its Google Maps API. In fact, the more I ponder the loss of Google Maps on the Flash/Air platforms, the more I am disappointed with Adobe for the current Flash situation. Following the release of Flash Builder 4, Adobe decided to take Flex in a different direction, one I objected to in my review of Flash Builder 4, focusing more on wooing designers than developers with its new skinning interface. In fact, prior to Flash Builder 4, I encouraged Java developers to learn Flex given the similarities in syntax and the richer user interface than Swing/JavaFX. These days, I do not encourage anyone to learn Flex, as the current API is erratic and future of Flash/Air is unknown.

The Future(?) of Adobe Flash and Adobe Air

The loss of Google Maps for Flash/Air feels like another nail in the coffin for Adobe Flash. Flex developers may recall that Adobe launched Air more than three years ago as a stand-alone Flash application platform. Adobe Air provides a run-time environment, similar to the Java JRE, that offers developers a richer feature set and more customization than a standard web-based Flash application allows. Unfortunately, with the growing mobile market, Adobe has virtually abandoned all efforts to market the Adobe Air platform. In fact, I can count on one finger the number of individuals, myself included, who I know have the Adobe Air runtime installed.

Final Thoughts

The last few years has seen the rise of mobile platforms in a big way, so much so that proprietary web platforms like Flash, Silverlight, and others have fallen by the wayside. I think Adobe’s biggest mistake regarding Flash in the last few years was in not actively pushing Adobe Air as a general purpose platform. Despite adding a number of Flash-specific features in the latest CS5.5 release, Adobe has not done a lot to encourage developers to stick with the platform. The loss of Google Maps for Flash may be just one in a series of events that leads to the end of the Flash platform as we know it.

Comments

Comment from Darren
Posted: September 22, 2011 at 8:16 pm

One workaround is to show content using the Javascript Maps API over part of your Flash content using an iFrame shim. I agree that the whole Spark/Halo thing is erratic but if you can make do with the Spark components, having the option to reach desktop, iOS and Android with practically the same codebase is a bonus. And good frameworks like Robotlegs do make the Flex coding experience worthwhile.

Comment from David O’Meara
Posted: September 25, 2011 at 8:20 am

Nice article, Scott 🙂

Comment from Mike
Posted: September 25, 2011 at 9:36 am

When searching for a map API, take a look at the MapQuest developer area. They have a Flex/AIR/Actionscript API that is quick and easy to use. I delved into the Google API and quickly discovered it wouldn’t work. But no problem, I still have maps in my app. Just because Google doesn’t offer it doesn’t mean it’s not available someplace else!

Comment from Michael
Posted: April 11, 2012 at 5:34 pm

Interesting article. thanks for the headsup Mike! i’ve definately taken a look at the mapquest API. Since the AIR mobile isn’t any different from AS3 api’s, it sucks that AS3 support is falling away because of Adobe’s decision. too bad really.

Comment from Grit
Posted: July 18, 2012 at 3:54 pm

Well… Articles like this also don’t help adobe’s poor coverage on the flash’s future. This all can be solved. Air and flash now have native extensions, also providing google map support like this one here:

http://code.google.com/p/air-maps-ane/

I’m still working with flash+air, the new openGL support + native extensions make it one of the most powerful development platforms in delivering fast cross mobile apps

Comment from james
Posted: March 12, 2015 at 2:45 am

Hi Wonder, how people easily say about some technology that its gone!.. Its a 4 year old article saying adobe AIR is dead. Yet we are building everyday adobe AIR apps. We built multi-million dollar cross platform apps with adobe AIR just last year i.e 2014. Every other app in google store is built with AIR. Who wants to ruin months developing in native codes for both platforms individually. If any part or component is not supported in AIR then it can easily be incorporated using native extensions of adobe AIR. So, nutshell its far from over. I see atleast a decade more of mobile apps development with adobe AIR if not less..

Write a comment