Sencha performances improvements / best practices

Hi Guys,

We are at the moment optimizing the beta version of our app based on Sencha, especially regarding the fluidness of animations / transitions where we have several raised points by our testers.



I have so a couple of questions, hope it's not too much, (FYI we are on Sencha 2.4.1)



- Views creations / destructions
I've read several times that the DOM manipulation is quite consuming for the webview and in some cases we should try to have all of our views in the DOM from the beginning.

In the other side, you guys are trying to say that a view unused should be destroyed or created at the moment of its use.



So, who's right ?



- Using store VS data config
So if we are pushing new views containing a list (or any view needing a data behind, with a XTemplate for ex...), should we use a Ext.Store object to handle the data or just pass the data through the list object created.

I've doubts about the performances if we use everytime Stores (creating new object for no real reason)...



Your thoughts ?



- Scroll views management (Android / iPhone <=5)
We are encountering several scroll issues (latencies / freezes) on some phone as Android (randomly) or iPhone (5 and below). Quite painful for the user experience prooving the bad quality of our work :/



Do you know anything about improvements / best-practices to improve this subject ?



- Slow App init
Launching the app could be really slow sometimes, same... especially for Android users with phones from early 2014 and below.



- Production build unstable
The production build is eliminating Ext.* objects access.

The app is working well except when we use methods as Ext.ComponentQuery / Ext.Store etc..



Weird. First time i'm seeing that.



Thanks for your feedbacks !

Alex

Sencha performances improvements / best practices