Listview scrolling becomes very laggy after more than 30 or so items are bound via endless scrolling or pull-to-refresh. In the article below by Chris Love he discusses Facebook's decision to abandon html5 for native apps and states the fault isn't necessarily with html5. He suggests techniques such as removing DOM elements when the markup is scrolled far out of view and not reachable with 2-3 flicks that could drastically improve performance for scenarios such as the Facebook infinite scroller. Would it be possible to implement a performance-enhancing technique such as this as a built-in feature of the KendoMobileListView scrolling? I have already made it a practice to never use With Blocks in my ListView item templates by assigning { useWithBlock: false } and would appreciate any other performance optimization options.

http://professionalaspnet.com/archive/2012/12/27/Don_2700_t-Make-Facebook_2700_s-Mistake_2C00_-Architect-for-the-Modern-World.aspx