What exactly are you talking about when mentioning “Cordova Support”? Don’t we
already have examples that are bundled with Cordova to valid Mobile Apps?
What’s missing here?
Chris
Am 15.01.17, 07:58 schrieb "Alex Harui" <aha...@adobe.com>:
On 1/14/17, 4:00 AM, "Vincent" <vinc...@after24.net> wrote:
>So what would be the interest of choosing technologies like Cordova
>instead of AIR to generate cross platform mobile apps ?
A goal of Apache projects is to do their best to be independent of
corporate influence. Flex is at Apache because a corporation made a big
change that impacted a lot of people. There are no signs of any big
changes around AIR, but the future of Apache Flex is better guaranteed by
not counting on a proprietary runtime for a major target market. I think
FlexJS should support mobile apps, and thus Cordova is a good first
choice. It doesn't have to be the only one.
In fact, a JIRA issue was just filed to request that we produce a FlexJS
release that has no Adobe dependencies. I think we can actually do that
now. Volunteers are needed to make this happen.
Technically, a Cordova app should result in a smaller download than an app
that bundles the entire AIR runtime. That was important to folks at one
point. Don't know if it still is. And a Cordova app can theoretically
run in more places than AIR: Windows Phone was asked about often at one
point. Not sure if it is important anymore.
Finally, Adobe (and I think MS, IBM, and other big names) seem to be
continuing to push Cordova. Aligning FlexJS as the faster way to learn
and use Cordova could bring us much needed resources, attention and
credibility in the enterprise. I will admit I never shopped for an
alternative to Cordova since Cordova being at Apache made it a no-brainer
for me, but if there are alternatives, we can certainly work with them as
well.
Of course, I could be wrong...
-Alex
