Why AIR is so kewl

Developers like me, who wanted their applications to look cool, must've surely passed through a phase when we used a Flash UI for a VB application and thought – "Wish Flash could do much more than just being a snazzy UI". It wasn't simple to make the UI look good. Every time you needed an extra bit of functionality, you needed to edit and re-export the SWF. It was also a bit of a mess when it came to the workflow. The VB developer and the UI developer had to keep making changes and pass on the list each time a change request came in. We used to call such apps – "FSCommand Splash". As the Flash versions released, we needed that bit more to help us make better applications. Component Binding was a blessing and so were the Data connectivity components. They certainly made tasks easier. Still, there was something we all wanted and tried to accomplish somehow – FILE IO. Of course, there were third-party applications such as MDM Zinc that gave us quite a bit of power, but, that was a separate investment and a different story altogether.

When AIR was launched, I guess it was a big turning point in most of our lives. We could do much more than just building applications with skins. We had something more powerful than that! Cross-platform and Browser-free meant we could build those "Rich Internet Applications" we always wanted to, whether you using a Flash, Flex or Dreamweaver user. AIR helped us use what we already knew and extend capabilities of our applications by harnessing the power of the internet and combining it with the power of the desktop. With built-in File API, well, it really pushed a lot of hurdles away. You also got a built-in database in SQLLite. We didn't need good ol' VB to do the job anymore. This was good in the business sense too. Not only could they give the client an application that looked great, but, they could also leverage their existing resources to build these applications, thereby, cutting costs. They could also cut costs by employing only necessary resources, eliminating the necessity to have other platform developers. Meaning to say, you team now only had a UI Designer > Flash/Flex/Web Developer > Tester with other platform developers as an optional. Previously this was – UI Designer > Flash Developer > Other platform Developer > Tester.

I think with the launch of AIR 2.0, Adobe would create a much bigger landmark. Reading about the new features made me and a lot of other people go "Wow". With new features such as – File monitoring, Volume monitoring, Asset caching, Native application support, online synching etc, AIR would certainly be a technology that needs no convincing.

For a more detailed list of AIR 2.0 features:

http://www.mikechambers.com/blog/files/presentations/fotb2009/advanced_desktop_development.pdf

It sometimes takes a lot to convince the client when he questions the choice of the development platform. It takes more convincing when you mention the fact that an extra layer needs to be installed on the user's machine to run the application. They don't really care about the development friendliness or the fact that we are using one or two technologies instead of using 4 or 5. A lot of times, we used to say that we are using Flex and keep the AIR deployment a secret. With the Installer doing the silent AIR runtime installation, nobody has to know. J