Storywatch launched in July 2024. Two years later, the platform tracks stories for thousands of readers across 100+ sites. Here's what two years of data and community feedback have taught us about how web fiction readers actually read.
It started with fourteen pinned tabs
Storywatch began the way most reader tools do: with a frustrated reader. Fourteen browser tabs pinned across Royal Road, AO3, SpaceBattles, and Wattpad, and a nightly ritual of checking every one of them for new chapters.
The tools that existed each solved a slice of the problem. Platform follows worked within a single site. NovelUpdates covered translated novels and nothing else. The spreadsheet worked exactly as long as it was maintained — which was never long. Nothing offered one library across every platform, with updates that arrived on their own. So we built it.
Readers follow more than they admit
The average Storywatch user actively tracks 12-15 stories. Most estimated 5-8 before seeing their actual numbers. Web fiction readers consistently underestimate their reading volume because manual tracking fragments the count across platforms. A unified library reveals the real number.
Cross-platform is the norm
82% of Storywatch users track stories on two or more platforms. Royal Road + AO3 is the most common combination. Platform-loyal readers who use only one site are a minority.
The DNF rate
For every three stories started, approximately one is actively followed to current, and two are dropped or paused. This isn't failure — it's the natural shape of web fiction consumption. Readers try more than they finish. The medium is built for exploration.
What's coming
Push notifications, public profiles, community reviews, and an official PWA are in development. Storywatch started as a tracker. It's evolving into a community platform built around how web fiction readers actually read — across platforms, with high churn, managing more stories than any platform-native tool can handle.