Adobe’s AIR: The Good Comes With Bad

February 25, 2008

One my favorite morning reads, ReadWriteWeb has a great article about Adobe’s AIR technology. For those not familiar, AIR stands for Adobe Integrated Runtime, and is a cross platform, code once run everywhere, light weight platform for applications. It holds a lot of advantages over other similar platforms. It’s two strong points in my eyes are: 1) it’s sexy looking, which is always a plus for end users. 2) It is easy to program in, especially for those who have worked with other Adobe products and technologies.

However my first experience with AIR was similar to some of my frustrations with .NET desktop applications. I was on the beta program for Pownce, which is written completely in AIR on the desktop side. I went and downloaded AIR, and naturally got the latest version from Adobe. Went to install the Pownce application and it said I needed an older version of AIR, immediately I was derailed. This happens more often than not with these "platforms", developers compile to a certain version of the platform and managing more than one version is a nightmare. Additionally, the last thing you want for a potential customer or user of your product is one more step before they can use your application; especially if that step is going to download another version of .NET or AIR. It’s the main reason I do not code in .NET for BlueCrestStudios.

I understand that with AIR it is just getting it’s official start out of Adobe labs, so it may not hold much weight here, we will see in the future. I hope that Adobe learns from others mistakes and makes the platform backwards compatible, easily distributable within AIR applications, and able to have more than one version installed if developers are going to be compiling against a certain version.

All in all, I think it has great potential, and will definitely be working it into future projects.