Storywatch launched in July 2024 with a very specific enemy: the open tab you are terrified to close because it contains a WIP you will never find again. Two years of shelves, chapter drops, and “wait, I follow how many stories?” moments made the lesson clearer: readers do not need more hobby admin.
It started with fourteen pinned tabs
Storywatch began with fourteen tabs pinned across Royal Road, AO3, SpaceBattles, and Wattpad, plus a nightly ritual of checking every one for updates. Platform follows worked within one site. The spreadsheet worked exactly as long as it was maintained, which was never long. We wanted one library for supported stories, with new chapters that did not depend on human memory.
The best tracker is quiet
Readers arrive thinking the problem is storage: where can I put all these links? The harder problem is change. A WIP gains chapters, a completed story turns into a series, and an active read becomes something you are quietly avoiding. A good tracker keeps that state visible without asking for a fresh spreadsheet row every Tuesday.
That is why Storywatch focuses on importing useful story details, surfacing unread chapters, and keeping reading states and shelves together. You should notice the fic, not the machinery keeping the list current.
Readers do not stay in one lane
Someone can follow a Royal Road serial, an AO3 longfic, and a SpaceBattles quest in the same week without considering that unusual. The sites still keep separate lists, but readers treat those borders like suggestions. Storywatch supports an expanding mix of fiction platforms because the personal library should match the reader, not the business model of whichever site holds chapter one.
Private beats performative
Reading lists are personal. They contain abandoned stories, embarrassing notes, comfort rereads, and ships nobody needs to explain at brunch. Tracked stories and shelves are private by default, and that decision matters more than bolting on a public feed because every other app has one. Fandom already provides excellent places to be social. The library can be the room where nobody is watching.
Two years in, the job is still the job
Platform coverage will keep expanding, and the library will keep getting easier to use. The standard is simple: does this save a reader from checking, copying, or remembering something boring? If yes, it belongs. If it turns fic into paperwork, it does not. Start a Storywatch shelf with the stories currently eating your brain and let the chapter drops take care of themselves.
What readers have asked for next
Once a library knows what someone has saved, the obvious next question is what they should read after catching up. Personalized recommendations are in development, with the difficult part treated seriously: a useful suggestion needs to understand fandom, genre, reading state, and platform boundaries without turning a private shelf into public performance.
Authors have asked for a clearer home too. A future claim-your-profile flow will let authors verify their Storywatch presence, connect official links, and point readers toward places such as Patreon from one compact profile. That work remains on the roadmap. We would rather describe the real library today and earn the right to announce the rest when readers can use it.
The two-year lesson carries into both projects. Fandom tools work best when they respect context, privacy, and the messy way people actually move between sites. That is still the product brief pinned above the desk.