Sencha Touch Performance Optimization

Official website said Sencha TOUCH2 more Sencha Touch1 performance has been greatly improved, but through the practice, still feel Sencha TOUCH2 performance needs to be optimized.

In fact, in the process of using Sencha touch to develop dashboard, when the data volume is large, the components are many, in addition to the case of many icons, Sencha Touch2 efficiency will be abnormally low, the user experience is very bad. Based on personal combat experience and the summary of mobile app developers on the web, here are a few points I think can be optimized for Sencha touch performance:

1. There is no doubt that we should try to deploy less unnecessary component on the page, and the whole application should not be so bloated.

2. The view was expressed that we should try to consider the xtype of each compont. This completely agrees, as to what kind of xtype we need to replace what kind of xtype, I really do not dare to say, yet to be practiced.

3. Now everyone is brushing the micro-blog, we can see every time the Weibo display page will not be all the new news list out, will only show a portion, when the user after reading the current page, you can use the drop-down event to refresh the list, and Sina Weibo each refreshed bar number of 20. (⊙o⊙) ... Amount In fact, I think this is not a technical optimization, is the optimization of operation and maintenance, good: Later when we meet the need for a large list of data, we can completely reduce the list of items add-ons to control its performance.

4. We should try to use the caching mechanism to handle the views that the page needs to load ... We can use the controller with the corresponding code to the current page needs to load a certain amount of views to cache. This way, you don't have to wait too long when the user needs to access the next view.

Cond.