We have an interesting challenge - we have a categorized listing and we need to limit the initial amount of entries to load.
This leads us into Pagination vs Infinite Scroll warfare, but quite honestly, the problem is a little more elaborate. I normally have quite a good feel for when to use one over the other.
Implementing either at a page level, you could load more easily, but then the page height increases and you lose context of where you are/were. Not so ideal.
Sure, pagination could work if we implement per category block, but it just has such a horrible flow to it. I'd rather avoid it if I can.
Implementing Infinite Scroll at a category level will stop you from easily scrolling over your list entries because of the load time and then your list will suddenly grow, leaving you clueless as to where in the list you are.
Any thoughts? I'm struggling to find examples of this out in the wild. I THINK I have an idea, which would then need to be tested, but if there is a common solution then that would be helpful
We cannot simply filter by category because the user may need context of Category 233rd entry but should still be aware that Category B's entries