Skip to main content
Enter REZICS

Reading Progress

Preserve personal states such as want to read, in progress, complete, and paused, together with genuinely resumable chapter positions and progress events.

Current statusAvailable

Progress states, percentage, events, chapter-reader reports, work progress pages, statistics, and import interfaces are available.

Core purpose

For an ongoing web novel, “reading” is not only a percentage. A reader needs to know how far a work has updated, which chapter they reached, when they last read, and where to resume.

Reading Progress keeps this data in the user’s own space and does not write personal state back as public fact about a work.

What is available now

  1. Record the states: want to start, in progress, complete, paused, and abandoned.
  2. Store numeric progress, percentage, start and completion times, and notes.
  3. Let readers report a stable content position from a chapter reader.
  4. Show work summaries, statistics, and event timelines.
  5. Let books and media use their own estimation rules.
  6. Provide import interfaces that create or update existing records.
  7. Restore a resumable entry point when a reader opens a work again.

Relationship to Content Structure

Progress should refer to a recognizable structure node and chapter context, not merely to a string such as “Chapter 368.” A string becomes unreliable after chapters are inserted, renamed, or reordered. Content Structure provides the stable occurrence; Progress records how far a particular user has reached.

Value to the reader

Reading trails can improve library sorting, update reminders, recommendations, search, and discovery, but they are first and foremost user data. Anonymous signals can be used only under explicit privacy and aggregation rules; the product must not turn personal history into public social pressure.

In development

Cross-platform automatic synchronization, source-level update tracking, fuller batch import, and additional protocols for gamebook journeys remain in development. Ordinary Progress must not prefill navigation fields for interactive fiction that has not yet been implemented.

Relationships and boundaries

Progress is not complete version history, a collection, or a work state. A serialized work’s completion is public information; a reader’s completion is personal. They can be compared, but they must not be stored in the same field.

Continue through the product network

Books & Web NovelsUnderstand published books and continuously updated web novels together, reconnecting cross-platform sources, languages, chapters, and reading context to one work.GamebooksAdd entry points, choices, branches, convergence, and endings to ordinary book structure while preserving the journey a reader actually takes.Personal LibraryUse collections, following, and reading progress to create a long-term, reading-focused space for works to read, in progress, and completed.
Enter REZICS