Hi Andrew,



Our organization’s concern, when I mentioned this announcement, is that the 
Harman-based AIR SDK may institute per-seat licensing. Are there any 
generalizations you can reveal concerning the future licensing plans? To 
provide some background, we are converting a major Flex app from browser-based 
Flash into AIR. My boss essentially had a heart attack when he saw today’s 
announcement. To provide perspective, our software handles substantial portions 
of the logistics operations for a company that might be considered the Home 
Depot of office supplies, as well as other similarly-sized businesses.



Best,

-Jeff



________________________________
From: Frost, Andrew <andrew.fr...@harman.com>
Sent: Thursday, May 30, 2019 5:58:43 PM
To: users@flex.apache.org
Subject: Re: Adobe AIR Maintenance and support changes

Hi

I just added a little more information into the Adobe forum post [1], hope that 
helps.

>From a Flex perspective, there's still the option to create Flex-based AIR 
>apps, and these will now be supported on Android 64-bit platforms when using 
>the updated SDK, no difference there really.

For web-based applications, they could perhaps be converted to AIR apps (if 
your customers are okay with having to install an app rather than accessing a 
browser), or you could look at migrating to a web-native format e.g. via Apache 
Royale.

We have another option now, which is basically less/zero work in terms of 
migration effort, which is that we are able to also license the Flash Player 
beyond the normal (EULA) licensing terms. Which means that it would be possible 
to wrap up a special version of the player along with a browser engine (e.g. 
Electron.js) and have this locked to your content, and then this can be 
distributed (again as it if were an application, so it needs local installing). 
For security reasons, this is only possible if we lock down the content that 
the player is able to load, e.g. a whitelisted set of URLs, but it does mean 
that you can just have an application that goes and displays your existing web 
page with the Flex content running in it, without having to change anything 
other than the deployment of the app via this installable package..

Feel free to contact me for more details but I may be slow in replying, my 
inbox is filling up..!

thanks

    Andrew



[1] https://forums.adobe.com/thread/2603957?start=120&tstart=0


-----Original Message-----
From: bilbosax [mailto:waspenc...@comcast.net]
Sent: 30 May 2019 21:23
To: users@flex.apache.org
Subject: [EXTERNAL] Re: Adobe AIR Maintenance and support changes

This sounds a little exciting to me.  From my understanding, Harman has been 
involved "behind the scenes" since 2006, so this gives me the impression that 
the transition won't be horribly bumpy.  I also like that there will be a 
pricing structure to AIR, a paid product is much more likely to be able to 
deliver the kind of support and development that we will need.  My only concern 
is that I don't know if it will be associated with the Adobe brand anymore.  I 
don't know if people will be as excited to sign up for Harman AIR as they were 
about Adobe AIR.

How about all of you Flex developers here at Apache?  What does this 
announcement mean for all of you? How do you feel about this transition in AIR?



--
Sent from: 
https://clicktime.symantec.com/3QbAF7LfRzsSeMw47dLf3Tn7Vc?u=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F

Reply via email to