[FEATURE] Implement infinite scrolling / Lazy Loading

[Ammoton]

Is your feature request related to a problem?

When I'm trying to look through my manga/books, it becomes frustrating because you can only view 40 items by default. This can be changed, but the setting isn’t saved.

Describe the solution you'd like

It would be good to have an option that replaces the paging with infinite scrolling, where the pagination controls are removed.

(This)

Describe alternatives you've considered

It would also be possible to simply save the entered value. But this would not be a very clean solution because it is basically infinite scrolling (with a high value) but still shows pagination controls that aren’t needed anymore.

Additional context

None

[aaronleopold]

I don't mind making the page size persist, I would have to consider infinite scrolling. While it isn't overly complicated itself it add, it would mean supporting another modality within the app which over time becomes cumbersome (e.g., table vs grid, paginated vs infinite scroll, etc). With infinite scroll, this compounds and overall becomes much more complex because of virtualization requirements, which would also entail somewhat different implementations between table and grid, and which also leads to my next point re:

It would also be possible to simply save the entered value. But this would not be a very clean solution because it is basically infinite scrolling (with a high value) but still shows pagination controls that aren’t needed anymore

The larger issue here isn't the page controls (that's more a UI nit) but the performance implications of not recycling things as they exit from view. If I were to add infinite scroll, it would need to be within some virtualized list so that your browser doesn't lock up from trying to load your entire library all in memory

[Ammoton]

Thanks for the explanation. I didn't realize how complex infinite scrolling would be. For me, it's not a very important feature, and it would be fine if only the page size is saved. But in the future (only if you'd like to implement it), I think it would be a good improvement and could even replace paging completely if you and other users don't find it too important. This would also make it more maintainable.

On a side note, I’ve been using the mobile app over the last few weeks and really like it in its current stage. Thanks for making it (:

[aaronleopold]

Yeah of course, no problem!

I think it would be a good improvement and could even replace paging completely

Personally I would never get rid of pagination, mostly because the problem with only having infinite scrolling is that it becomes really annoying to get to the end/middle of (or close to the end/middle of) a list. If I add infinite scroll it would be additive, so we'd have both controlled probably by some user preference.

It is funny though because ironically I feel the opposite towards pagination vs infinite scroll on mobile applications, which I'm sure you've noticed is why the mobile app lacks any pagination. It just feels clunky and in the way for mobile

On a side note, I’ve been using the mobile app over the last few weeks and really like it in its current stage. Thanks for making it (:

❤️ Happy you like it! I think it is shaping up to be pretty usable, too