Cool. This is really useful info. Architecturally, Royale was designed to support the same kind of compile-to-native support that Flutter gives you. A big part of the reason we are keeping SWF support alive in Royale is to ensure components can target other platforms. The most obvious platforms other than web is iOS and Android.
Unfortunately none of us has spent any time working on direct-to-native support. I can’t speak for anyone else, but I can tell you that I haven’t because mobile development is not really on my radar right now. Harbs > On Aug 13, 2020, at 4:53 PM, leokan23 <l...@best-web.gr> wrote: > > Sadly, after running a simple example with Cordova (I hadn't tested it for a > couple of years), it looks like I get huge FPS drops even on my 12gb 8core > phone. It dropped in a simple animation from 60fps to 5, which obviously is > a no go. > > The second benchmark I did was going through a for loop to increase a > counter from 0 to 1000. > Royale for web result: 545ms to 678ms > Royale wrapped with cordova (running on webview of android as it doesnt > support directly running using chrome engine): 670ms to 820ms > > Flutter for mobile (running in debug): 53ms to 112ms > > I will extend the test to use a royale project instead, to see if it makes > any difference, but I am not confident that I will get better results at > this point. > > So as I have said in the past, although Royale is a great option to replace > Flex for web, I dont see it working for mobile apps. > > > > -- > Sent from: http://apache-flex-users.2333346.n4.nabble.com/
