Hi,
Regarding performance using standard display list, it is already
possible with Flex to develop mobile applications indistinguishable from
native ones.
My understanding of FlexJS is that the framework is much lighter than
flex so the generated swf should logically perform even better.
So what would be the interest of choosing technologies like Cordova
instead of AIR to generate cross platform mobile apps ?
Vincent.
Le 13/01/2017 à 19:35, Carlos Rovira a écrit :
Hi Peter,
2017-01-13 19:22 GMT+01:00 Peter Ent <p...@adobe.com>:
I was speaking to a friend that has some JavaScript developers working for
him. They use React and React/Native for their mobile apps. His feeling is
that web-centric apps (e.g. Amazon.com) are going to be replaced with
mobile apps since mobile devices are cheaper than laptops. They are
concentrating their app development to server-side services with native
apps delivered via React/Native.
IMO then, what FlexJS needs is the ability to go native. This isn't
necessary for a 1.0 launch, but having FlexJS/Native with applications
constructed in ActionScript and MXML and then cross-compiled into Swift or
Java could go a long way to make FlexJS the platform for cross-device
development.
I already see that. but for 2.0, as you said native (swift or java) seems
huge work.
But...what about SWF *native* ?
I mean, SWF Stage3D mode is very performant (I think even native) right?
I think FeathersUI is Stage3D powered and is performant on Native. someone
correct me If I'm wrong.
So maybe SWF should be not display object ready but stage3d ready to allow
us to have the same performance as native
That's is for me the main reason for SWF existence. Alex said that actual
SWF FlexJS framework based on display list could be very performant...I
don't know since we didn't make any benchmark here and that it had the
advantage of have accessibility implemented...
