>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 thought the eye perception was limited to 24/25 fps (which is the frame rate at the movies) So what's the difference ? Maurice -----Message d'origine----- De : After24 [mailto:vinc...@after24.net] Envoyé : mercredi 2 avril 2014 12:13 À : users@flex.apache.org Objet : 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.
