3 ms·
No. AIR was a runtime for desktop environments. You could implement standalone applications (and mobile apps) with it. I also worked on a few embedded systems w
by Matthias247 8y ago
No. AIR was a runtime for desktop environments. You could implement standalone applications (and mobile apps) with it. I also worked on a few embedded systems which utilized a user-interface on top of Flash/Flex/AIR.
As far as I can recall it was pretty good, and mostly fun to work with. The framework was quite powerful, and allowed us to write lots of highly interactive code in a short timeframe. At that point of time (maybe 2011?), it was far ahead of anything based on Javascript/HTML, and I think only more recently the more powerful web frameworks might have caught up.
- jdmichal 8y ago2008~2011 timeline sounds spot on. We had an AIR app, which we started moving to web-based JavaScript around 2011ish I think. It was a lot of custom code; would have been a lot simpler now with something like Angular. And TypeScript would have been alike a chorus of angels.
- Jach 8y agoI really enjoyed Flex and look back at it fondly, when I tried Angular 1 it felt like the first thing on the JS/HTML side that could come close to matching the productivity of Flex (albeit with no helpful IDE). It was good enough to whip out a MVP demo in 48 hours. I've mostly been out of UI development since, occasionally extending stuff written in a NIH corporate framework or some Backbone things. Occasional experiments with the ClojureScript tooling (Reagent-based) seem like the next way forward that maybe the rest of the world can use in another 5+ years.