I think a lot of people have seen this article by Tim Anderson (and Rey’s thoughts on Ajaxian) but I wanted to throw my two cents in. Tim said he was at a couple days worth of briefings about our developer products and had a bunch of takeaways with Adobe AIR. I tend to agree with 99% of what Tim said (on both sides) and I think anyone considering AIR should read the post. There were a couple of points, both cons, that I want to talk about:
7. Schizophrenic development model. AIR supports either Flex development, or HTML applications which run in WebKit. The ugly side of this flexibility is that there are two SDKs, even two JavaScript virtual machines with different capabilities and characteristics. While it is nice to have a way to render HTML, I am not convinced that the web application model is worth it, given the complications it causes. After all, web applications run perfectly well in the browser.
I thought this was really interesting and it was something I hadn’t given much thought before today. I’ve always seen the Flash/HTML flexibility as a good thing and I think the script bridging between the two is one of the most compelling features about AIR. That said, as you really dig into AIR and start pushing it to the boundaries, I can see how dealing with two virtual machines and rendering HTML inside of Flash starts to become complex. I think web developers are a creative bunch, which is what makes AIR so interesting for me. The web application model is very, very different from the traditional desktop application model. Bringing those two worlds together is kind of like mixing oil and water. I’m hoping that the model we’ve chosen is flexible enough for developers to hack around and find interesting solutions to the problems they encounter. I think that’s the spirit of the web and hopefully the spirit of AIR (now that sounds weird).
The second point deals with security:
8. Security concerns. AIR is close to the worst of both worlds, being tightly sandboxed from a developer perspective, but not particularly safe from the user’s perspective. Adobe says it will allow unsigned applications, which I think is a mistake.* AIR has the same access to the file system as the user, which in the case of users running on Windows XP with full admin rights is very extensive. Example bad scenarios would include downloading malware and placing it your startup folder, or searching your file system for bank details and uploading them to some internet location. That said, Adobe says there will be more security features, so conclusions are premature.
Security is a huge issue for us. As someone who sees it from the inside I can promise you that we’re doing a lot of thinking/discussing/inquiring about the best way to handle security in AIR. We’ve talked to people like Rey inside of the Ajax community and a ton of other people to get their feedback. I think that when AIR is released we’ll have addressed most of the security issues while still giving programmers the ability to create the applications they want. Always keep in mind (as both a user and developer) that these are real desktop applications and can act accordingly.
[tags]Adobe AIR[/tags]