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.
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.