~~This is not correct.~~ AIR was a way of publishing flash (only) content into standalone executables for desktop or mobile - win/mac/android/ios/etc.
As a platform it was basically Flash plus extra APIs for interacting with the OS, and as a tool it was a bundler that also handled stuff like signing certificates for the android and ios app stores (IIRC).
edit: miscommunication, sorry - AIR only rendered flash content, but it could display web content by invoking an OS browser component. So you could have a browser component inside a SWF wrapper, and the runtime could make the wrapper for you so from the author's perspective it was the same as supporting html/js. My bad!
No, it's definitely correct, they definitely supported HTML/CSS/JS at some point, not flash-only content - I myself published a normal SPA back in ~2010, and looking back it's actually kind of insane how similar Adobe AIR is to Electron.
Ohhh, I think one of the OS-integration features was that you could invoke an instance of the OS's web component, is that what you mean? AIR itself didn't do anything with html/js but you could render web content at runtime via the OS component.
Just looked back at some docs now, thanks. The things you forget in ten years..
Yeah, same! I didn't remember that it had been a wrapper (to be honest I have very little memory of -how- we did it), but I suppose it makes sense. TweetDeck was Adobe AIR too at the time, no?
Yeah, I'm almost sure there was no html renderer or JS engine in AIR, but you could have pure html apps with no flash in the source now that I think back. TweetDeck was I'm sure, and one other high-profile AIR desktop app was the launcher/lobby app for League of Legends.
As a platform it was basically Flash plus extra APIs for interacting with the OS, and as a tool it was a bundler that also handled stuff like signing certificates for the android and ios app stores (IIRC).
edit: miscommunication, sorry - AIR only rendered flash content, but it could display web content by invoking an OS browser component. So you could have a browser component inside a SWF wrapper, and the runtime could make the wrapper for you so from the author's perspective it was the same as supporting html/js. My bad!