[Mobile app] v1.2 OPDS use natural order from feed to progress to next book

[Cducharme84]

When using a non-Stump provided OPDS feed with the image reader, currently there's no mechanism to move to the next issue/chapter/volume (whatever terminology is applicable) from within the reader, with a Stump backend the next book in a natural queue (whether via smart list or series etc) will be prompted to pull up. It'd be great if the same could be replicated for the OPDS feed.

Of course OPDS servers vary, but a large portion present the feed in the intended order for the feature being served, a good example of this is the reading list feature in Kavita's feed, while it comes down unnumbered it does come down in the correct order as that's how the feed is generated to allow a "next up" ingestion.

So for a less advanced server this would just be an alphanumeric ordering, which as humans we kinda expect anyway but with a feed presenting the correct ordering already it's just a matter of grabbing next entry. See attached screen for a Kavita present reading list and how the Stump mobile app currently displays it, just to illustrate that Stump's already recognizing the ordering we're really just talking allowing a next book up in reader progression.

[aaronleopold]

The problems I see, some of which you've already pointed out, are mostly:

• Stump isn't "aware" of the originating feed for a book today, or more accurate I guess to say it doesn't track it when you click a book. So I'd have to track from where you entered the reader for OPDS to then issue the same query, find the current book, find the next book, present upon completion (or some iteration of that kinda thing)
  • An edge case I foresee is what if book e.g. 10 is the last book in page 1 of 5, I'd have to traverse programmatically to the next page in order find it
• Stump would be making assumptions about ordering from a server, which I'm okay accepting for this use case but might put it behind an opt-in flag or something

I think this problem would also be more easily solved for OPDS v2, but I'll take a crack at it either way for both 🙂