162
Replies
For what it's worth, I got a respons from Adobe on their Animate Facebook page when I asked them if they still care about AIR: "As far as I know, there has been no change to our plans for Adobe AIR. ^PK" 
Hopefully someone from the Adobe AIR staff can confirm their ongoing commitment.
Yep, the classic "business as usual" answer and it's good.
For AIR, business as usual means we will keep getting those quarterly updates.
We will get an update in March, and then in June, and another one in September etc.
For all the people that freaking out about the Android 64-bit updates, here my prediction (mark my words LOL)
and yeah I'm not related or connected in anyway to Adobe (I don't know or talk to any Adobe employees),
I have exactly zero insider information, but I can tell you that:
At the very least the AIR release of June 2019 will implement the Android 64-bit update,
just shy of 2 months from the official limit of August 2019 which will give plenty of time to update,
and yeah maybe there will be bugs, which then will be fixed by the next release in September 2019,
and that's the worst case scenario.
Let's see what happen 
ASWC wrote
Unity has simply done what Adobe didn't bother to do (and could have done easily) with its technological monopoly. ...
... Not such threat though about Flash mainly cos Adobe didn't know what to do and how to handle the situation. it was simply safer to not do anything and not care.
You don't know what you're talking about
Adobe, or anyone else for that matter, could not provide Flash for the mobile browser
because Apple changed the licensing to restrict interpreters (other than JS)
and yeah Adobe engineers did something, they took the Flash runtime
added AOT compilation to the already existing JIT compilation / interpreter mode
and they used this AOT to cross-compile AS3 / SWF / SWC / assets / timeline / etc.
to native binary (IPA) for iOS, so Apple could not even dream to kick out AIR apps from the app store
see here Flash Iphone Fitc 2010
Such cross-compilation can work with something like AIR, not within a browser plugin like Flash,
so if you want to blame someone blame Apple.
And everyone else did the same thing (using AOT): Unity, Mono, C#, Java, Lua, etc. because it is the ONLY WAY
Unity did not get a special treatment from Apple, they also had to use AOT to compile a native binary
also
ASWC wrote
...
At some point it's gonna get a make over and some options are gonna disappear like likely Flash/AIR/Projectors etc and eventually be only HTML software.
You don't know that, for one Animate CC is the only tool that can allow such variety of exports
why would they shoot themselves in the foot by removing features other tools do not have?
See it like that, Animate CC is a tool for creative people that are not necessarily hard core dev,
being able to export to something like an IPA or APK via Adobe AIR is a tremendous and very convenient feature.
In itself you could see Adobe AIR as a middleware, Animate CC reuse that middleware to exports stuff,
other people can "program it all" by taking advantage of that free middleware without having to go through Animate CC.
You should be grateful to Adobe for that.
A Unity Pro license end up costing $1500/year, Unity free license only allow you to publish non-commercial content.
Still, though coffee never made me money. AIR, unity, native etc. did.
There is a difference between AIR, which is a free to use delivery platform, and what Adobe put a lot of development time into. Converting AIR to also publish to mobile web, for example, would directly compete with the paid products that Adobe make, that already do the same thing.
Look at some of the improvements to Adobe Animate there have been in the last few months:
What's new and changed in the October 2018 release of Animate CC (version 19.0)
It also publishes to nine different platforms, as well as custom platforms. So, lots of effort from Adobe to publish to these various platforms, but you would need to be using the paid for Animate, and not the free to use AIR.
AdChoices