Swizec Teller - a geek with a hatswizec.com

    Five reasons you should develop in Adobe AIR

    Some weeks ago I've spoken about clean code and speed coding, that tried to allude to the fact of how writing code that is clean helps you write code quicker and better. Everything focused around Twitulater and how well its development was going, but today I'd like to give mention of another very important reason development is going so well. Adobe AIR.

    AIR is simple

    Because Adobe AIR is based on javascript and html everyone with a history of serious web development should be able to pick it right up and start working practically without a learing curve. Design your GUI in html+css and all the logic goes in javascript, even things like jQuery and other javascript frameworks can be near fully utilised to make the transition quite seamless.

    Personally the biggest problem I've ever had with desktop development was building the GUI's; since I'm not an IDE kind of guy my life is really made miserable by having to add all the event listeners, positioning items etc. In Adobe AIR I just do it the way I'm used to.

    AIR is multiplatform

    Ever developed a really cool application for Linux and then wanted to have it run on Windows? Or maybe you're a windows kind of guy, but your public is suddenly starting to switch to better platforms? What do you do?

    Well up until now you had to build from scratch, or worse, take great pains in porting your software over to another platform. But Adobe AIR theoretically deals away with all of this. Since all the porting pains are done for you by Adobe so all you have to do is develop your application on a system and there is a big chance it will run everywhere. Sure there might be some issues with certain features, but those can be quickly amended.

    One css/js/html implementation to rule them all

    The biggest issue us webdevelopers ever encounter are differences between browsers. Everything has a few quirks of its own, be it an odd javascript implementation, a differing DOM object model or even something as simple as miriads of css bugs. To be honest these issues are fast driving me out of webdevelopment because I simply don't want to bother anymore and would rather turn to a platform that at least tries to be developer friendly.

    Users like AIR

    Users in general are quite fond of Adobe AIR and prefer installing apps that run on Adobe AIR than native applications. This is because running a native application always poses a certain level of risk, if you don't trust the issuer then they could be doing pretty much anything to your system or maybe they're installing a bunch of crap alongside their app. So for small-time developers it's much better to work under an umbrella system like AIR.

    What this does to users is they can be certain the application won't mess with them too much and most of all it's easy. Most Adobe AIR applications can be installed automatically right from the browser where the download and installer running are completely transparent to the user. Another reason I believe users prefer AIR to native applications is that most small-time applications look like crap whereas with AIR nearly everything has a decent look to it.

    Bigger target audience

    Because users love Adobe AIR so much and because there are already so many applications developed for it there is a large target audience for these kind of applications. People want and need a whole bunch of small, quick and painless applications which would be too cumbersome to use if they were native. Think widgets and dashboards and that Vista thing. Why are all of these popular? They enable a simple way of displaying critical information without anything cluttering up the user experience or their taskbar or whatever.

    AIR fills that niche rather nicely, so if you have something of the kind to develop then there's a big chance your users will already have AIR installed and won't think twice about installing yet another such application or they will be lured into the AIR world by its simplicity. Even before I started working on Twitulater I asked my followers if they'd prefer it to be native or AIR and the response was resoundly in favour of AIR.

    So there you have it, five reasons you, as a developer, should use Adobe AIR. Join me in a few days when I will try to find five reasons why not to use it, because every coin has three sides.

    Did you enjoy this article?

    Published on November 27th, 2008 in review,

    Learned something new?
    Read more Software Engineering Lessons from Production

    I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.

    Subscribe below 👇

    Software Engineering Lessons from Production

    Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.

    "Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"

    ~ Ashish Kumar

    Join 15,883+ engineers learning lessons from my "raw and honest from the heart" emails.

    ⭐️⭐️⭐️⭐️✨
    4.5 stars average rating

    Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.

    Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.

    Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.

    Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev

    Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization

    Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections

    Want to brush up on modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com

    Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog

    Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com

    By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️

    Created by Swizec with ❤️