Adobe AIR: Native OS Integration Problem
Filed Under (AIR, Flex, InfoQ.com, RIA) by jonr on January-29-2008

I did a write-up yesterday on InfoQ.com about the OS integration limitations of the AIR platform. Mike Chambers of Adobe offered up some ideas on how to work around this issue, which seem to start a flame war with Scott Barnes of Microsoft. Regardless of the religious war, I do believe this is a significant issue for the AIR platform, which will need to be addressed sooner rather than later.

Checkout the InfoQ.com post at:  http://www.infoq.com/news/2008/01/adobe-air-native-os-integration

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • DZone
  • Digg
  • del.icio.us
  • Reddit
  • Facebook
  • LinkedIn
(2) Comments    Read More

Comments:
Michael on April 18th, 2009 at 3:41 pm #

It you start integrating with the native OS, the AIR platform stops being truely cross platform, and you are back to “write once, test and revamp everywhere”. Adobe obvously made the decision to avoid that.

jonr on April 18th, 2009 at 4:06 pm #

I understand the dilemma for Adobe. However, the choice to limit the ability to integrate with the native OS limits the number of applications that developers will be able to build on the AIR platform. For example, if you require peer-to-peer integration, you either have to find ways to break out of the sandbox (like Merapi) or use a different platform. Either way, you end up with the same challenges … you just are unable to use the native AIR platform for building your application.

Post a comment
Name: 
Email: 
URL: 
Comments: