Using a Cross-Platform Runtime to Build Better Apps

The inherent advantage of using a cross-platform runtime, such as AIR, to develop applications is typically understood to be the boost in productivity that’s achieved by reducing the amount of per-platform work that’s required. While it’s true this is a potential advantage, it’s generally discussed with an implicit assumption that the developer is interested in reducing the development cost.

Suppose, for moment, that this is not the case. If you spend just as much on development as you did before and use a cross-platform runtime, then what happens? You build better apps.

The key is to take all the time you saving writing code once and apply the savings elsewhere in your application. That could be to additional features. Or it could be a better experience: improved responsiveness, more intuitive UI, lower memory use. No matter how you spend this savings, you build a better app.

One Response to Using a Cross-Platform Runtime to Build Better Apps

  1. Ivan Najman says:

    Interesting point. But also often it`s not only about lowering development time , sometimes features also dictates whether you should choose AIR or native development sdk. Currently, AIR doesn’t have access to android or iOS system so you can not use notifications or haptic feedback when pressing the buttons. But again, as times goes by this would be available i guess.

    I agree, business value can be increased , but there must be some type of exact measurements about what is gain of using cross platform runtime