Desktop app for keeping track of stories (books, fanfics) you read.
- You read a lot of different stuff. Like in hundreds or even thousands.
- You can't remember everything you read, and you have to keep track of that.
- Also, you like to score stories and write reviews, even if only for yourself.
- Maybe, you even re-read some stories.
- Excel spreadsheet is not enough anymore.
Stuff I Read was created and tailored for my personal use-case, but I will add features by request if there's a need.
Built using Compose Multiplatform framework (selected as
experiment/research).
My personal opinion after working with it: don't use it for serious multiplatform development until 2025 or so.
Standard library is lacking, and framework is fragile. You will waste time re-implementing basic components,
exploring internals because documentation is minimal, and fighting obscure bugs.
You can browse your archive using advanced search. You can search by author, description, publishing/last update dates, tags, score, review, content, word count and other parameters.
Example
Write reviews and score stories, so you won't forget why you enjoyed reading a story.
Multiple score formats are supported, including 5 stars, 10 stars, 10/10, 100/100. Format can be changed at any time without breaking existing scores.
Example
To help with categorization stories can have fully customizable tags.
Category provides order and color of the tag. Ordering can be very useful when story has dozens of tags.
Tags can imply other tags. For example, tag of character can imply their species, and now you can search
for stories with that species without explicitly adding the species tag.
You can edit implications at any moment and all stories will be affected by the change.
Examples of tags, you can create your own at any moment
Easy navigation for story sequels/prequels.
Example
Files with story content can be locally archived. Strictly speaking all formats are supported,
but EPUB, HTML, PDF and TXT have special handling, for example word counting.
Files can represent not only the whole story, but individual chapters as well as any additional content too.
Example
Currently supported:
- archiveofourown.org
Work can be imported in multiple file formats if needed. - pastebin.com
Multiple pastes can be imported as one story. - poneb.in (Pony)
Multiple pastes can be imported as one story. - ponepaste.org (Pony)
Multiple pastes can be imported as one story.
||Don't worry, you can hide pony website integrations in settings||
If website has story tags - they can be imported and mapped to local tags:
Example
Use system theme or select one yourself.
Example
Support at least English and Russian. Also support language-based import sources settings.
Feel free to request other websites!
- FimFiction.net - Pony (has excellent API, but need to request access).
- PonyFiction.org - Pony, Russian
- FicBook.net - Russian
Read Later List: stuff that you want to read sometime. Prioritized, with notes, url, date added, etc.
In Reading List: stuff that you are reading right now.
Also, a way to move stories between lists: Read Later -> In Reading -> Archive
Page with aggregated stats on everything you read, including: total word count, score distribution, time distribution, and so on.
To be able to convert EPUB to PDF, TXT to HTML and so on.
As of now only first read and last read dates are supported, but I think it would be cool to know about specific dates when you read something.
Compose Multiplatform "supports" it, but I personally don't need it. So it's low priority.
Story archive is a folder and consists of tags (tags.json),
stories (individual folders with story info in story.json and archived files).
Q: Why use separate files instead of something like SQLite database?
A: I wanted story archive to be easily versioned. E.g. Git/other VCS, or clouds like Google Drive.
SQLite DB with a thousand stories can be GB-sized - you don't want to upload that each time new story is added.