It’s the age old UX question. I’m pretty sure there is some UI guidance on this someplace, but I’ve not had support for one way of making sure that users (and of course test automators) can handle things like a list slowly populating while calls to the back-end return.
Search engines somehow manage for example by making sure that there is not requirement to “sort” the results list, which means it’s never going to happen that a user clicks on an item and then finds that it “moved”. It’s rather frustrating when Windows Explorer (other OS filesystem search tools with GUI’s on them do exist) , and a lot of people find other file search tools create less friction by somehow magic. The built in search tool is not great for many other reasons, but this “scrolling” while results return thing is complexified when the results need to be in a sorted order. I guess I’m looking for two things here.
- Infinite lists that scroll forever
- Paged or chunked lists (which are much easier)
Had anyone seen a good published and reviewed explainer on this kind of UX problem? I’m mainly trying to work out if a uniform approach in a web based test framework which might help enforce consistent list user experiences is good or not achievable.
- When lists are shown in pages not as one huge list, we should expect each “page” of results to be almost instantaneous for that page.
- When the list is “infinite”, sorting the list becomes evil and I’d like to avoid reshuffling annoyance
- Are spinners or hourglass and disable user from interacting while it loads a standard way to deal with both infinite lists or paged lists?