Feature Request: “Recent Reads” Or „Reading now“ Tab/View for web & app reading

[S.Raven]

Feature Request: “Recent Reads” or „Reading Now“ Tab or View

For:
*readers on the Web App
*readers on the iOS/android App

Purpose:
To allow users to easily access and continue reading their most recent books, including catching up on older releases, without manually searching through all books in a Series or all favorited Books.

Current Situation:

*The “Favorite” feature shows new releases of chapters, which is great for staying up to date.
*However, if a user wants to catch up on older chapters or return to their most recent read, they have to manually search through their list of favorite books and then through all of the books in that series to find where they left off.

Proposed Solution:

*Add a “Recent Reads” or „Reading now“ page or view that displays the last 30 books (or a customizable number) the user has read.
*The list should be sorted with the most recently read book at the top, followed by the next most recent, and so on.

Functionality:

*Direct links to the last-read chapter: Each book entry should link directly to the last chapter the user read or, if availiable, the next unread chapter.

*Visual indicators for updates:
-If the user has read all available chapters, the entry should be marked blue (or another easy-to-recognize color).
-If there are new chapters available, the entry should be marked white, and it should link to the next unread chapter, not the newest chapter, so that the user can continue in order.
*User-friendly navigation in a List: This list makes it much easier to quickly pick up where the user left off, especially when reading multiple series in parallel.

Benefits:

*Efficiency: Users no longer have to open multiple books to find where they left off.
*Convenience: Makes bulk reading and catching up on older chapters easier.
*Enhanced user engagement: With a clearer view of what’s been read and what’s available, users are likely to read more frequently and stay engaged.

[Shiny]

I agree it's hard to catch up with the current reader.

The approach taken by the https://jnc-reader.wscr.dev/ third party reader is much better for this use case