This is why I mentioned trying to leverage some basic starling/feathers capabilities for some of the most used components like scrolling lists. I'm not sure if that would be possible but that slight lag plays into that whole narrative about slowness, memory hogging, battery life etc that has plagued the runtime on mobile.
My experience is that pretty much none of that is true or accurate but if there's a specific rendering lag on lists that aren't hardware accelerated it gives people and excuse to class the whole thing is somehow slow or bad or whatever else. Meanwhile the framework itself is great because it makes things easier and faster for development and control over the runtime. David -----Original Message----- From: OmPrakash Muppirala <bigosma...@gmail.com> To: users@flex.apache.org Sent: Wed, 02 Apr 2014 9:51 AM Subject: RE: Coding a better flex mobile app "Just to test performances I created an Hello World app in Objective-C, AS3 and Flex, just a pair of views with a few buttons, and the Flex one was dramatically slow and heavy compared with the others." This doesn't sound right to me. Forget 60fps graphics, it seems Gabriele is not able to get a very simple UI working properly. Do you want to post some code so that we can test and figure out what is going on? Thanks, Om On Apr 2, 2014 6:38 AM, "After24" <vinc...@after24.net> wrote: > Hi Mark, > > Yes but like you said it's a Nexus 5... and it will probably take time > before this level of power reaches low-end devices. > > > > > Mark Line wrote > > Not sure how it was coded, but on > > http://flex.apache.org/community-showcase.html > > > > CityU Mobile runs really really nice on my nexus 5 (I know it's a higher > > end), you should check it out > > > > -----Original Message----- > > From: After24 [mailto: > > > vincent@ > > > ] > > Sent: 02 April 2014 11:13 > > To: > > > users@.apache > > > Subject: Re: Coding a better flex mobile app > > > > Hello, > > > > From my personal experience, it's not possible to get a super fluid app > > using flex mobile (especially on mid range phones and tablets). I think > > this perception is mainly due to the list component which never reaches > > 50/60 fps even when its itemRender is well optimized. > > > > I know that this need of smoothness is very subjective, but for me it's > > essential and greatly improves the user experience and the pleasure to > use > > an app. > > I understand that the flex framework wasn't originally designed to run on > > mobile devices and that optimizations are limited because of the > > architecture of the framework (14 000 lines of codes for UIComponent for > > example). I'm absolutely not complaining about it and the situation is > > going better and better with new generations of mobile devices. > > > > But for now I'm forced to choose other solutions to get a fluid mobile > > app, to be specific I use : > > > > - Starling > > - Feather UI > > - Robotleg > > - AS3 signal > > > > I'm very happy with the result but frankly, the choice between this stack > > and flex will be a no brainer if flex was able to perform as well on > > mobile. > > This is the trap with flex, it's so good and easy to develop with it that > > others solutions, even if they works well, are very far from approaching > > the ease of working with flex :-) > > > > One more time, it's not a criticism, I'm absolutely not complaining, it's > > just my personal opinion about flex on mobile. > > > > > > > > -- > > View this message in context: > > > http://apache-flex-users.2333346.n4.nabble.com/Coding-a-better-flex-mobile-app-tp5888p5895.html > > Sent from the Apache Flex Users mailing list archive at Nabble.com. > > > > > > -- > View this message in context: > http://apache-flex-users.2333346.n4.nabble.com/Coding-a-better-flex-mobile-app-tp5888p5906.html > Sent from the Apache Flex Users mailing list archive at Nabble.com. >
