Best Practices For Speed/Performance in View Management and ListViews

2 posts, 0 answers
  1. Eric
    Eric avatar
    4 posts
    Member since:
    Mar 2013

    Posted 11 Mar 2013 Link to this post

    We have been testing kendo mobile's robustness to see if we can switch our entire development over to this framework.

    On our initial tests everything worked beautifully. After we started to stress test it we found that due to the frameworks lack of memory management features we hit jumpy scrolling and delayed view transitions.

    We would look at documentation and find bits to make things work better however, we are still looking for best practices in keeping responsiveness quick and memory usage down.

    Our two main culprits/memory hogs are large listViews with images and transitioning between views.

    What techniques have you used? We are thinking of destroying views after transitioning away from them.  

    Also, what are all the possible events that a view can fire and is there documentation about these? I have found init, beforeShow and show.
  2. Petyo
    Petyo avatar
    2437 posts

    Posted 13 Mar 2013 Link to this post

    Hello Eric,

    After a view is navigated away from, it is hidden using CSS display: none. I don't think that destroying it would help a lot, but it may work in your particular case. 

    All view events are described in our API reference. The hide event in particular may be useful for disposing certain resources. 

    Our upcoming release will introduce a new event - 'afterShow', which will be triggered after the transition to the view is complete. A simple trick which may increase the app responsiveness is to hide the view complex contents (listviews with images, etc), and display them after the transition is complete. 

    the Telerik team
    Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
Back to Top