Under Review
Last Updated: 27 May 2021 11:33 by ADMIN
Adrian
Created on: 24 Jul 2013 08:51
Category: Kendo UI for jQuery
Type: Feature Request
27
MobileListView EndLess Scrolling Grouping
The previous KendoUI mobile listview respected datasource grouping when endlessScroll was enabled. This functionality has regressed in the Q2.2013 release.

An extract from my support ticket 718079:

For our application, it is not acceptable that the ability to group with endless scrolling has been lost. Grouping is fundamental to the user experience in our app - especially when there can be a lot of items in a listview. It is just as important as the performance that endlessScroll enables. One, without the other is a backwards step.

Telerik response extract:

Thank you for your feedback. I fully agree with you - grouping of a large dataset improves the user experience and provides the necessary visual clues for the user to determine the current position in the list. The only reason why this is not supported is the high complexity and performance implications of the task, when combined with virtual mode, which is a requirement for a large list support - our previous implementation easily crashed the mobile browser when 100+ items were displayed. I would like to suggest that you post this feature request to our UserVoice feedback  site; we are actively following the popular items and responding to our customers demand with each release.
---

I do not believe the complexity is quite as high as has been described. The datasource can identify how many groups there are - for any current filters and adjust the endlessScroll height accordingly. The listview items themselves can be adjusted down in position by the number of group headers above them.
2 comments
Rodney
Posted on: 13 May 2014 17:06
Add Support for Grouping with Endless Scrolling. 
Yanik
Posted on: 03 Sep 2013 15:16
We have the exact same issue. I am surprised and disappointed that so little interest and effort has gone into making this work. It seems like for any mobile application of size, this would be an unavoidable feature.
I hope this gets bumped up the priority stack really fast!