Compared with a spreadsheetAleph
Aleph
vs your spreadsheet
The spreadsheet works right up until the evening you don't feel like opening it. Aleph's version of that row is a timer you stop.
Download app0Rows to fill in by hand
Why the spreadsheet stops
Manual reading logs fail for a predictable reason: the logging happens after the reading, when the motivation that produced the reading is gone. A row entered three days late is a guess.
Aleph moves the record to the moment — start the session, stop it, and the row writes itself with a real duration and page range.
You keep the analysis
The pivot tables people build by hand — pages per week, pace by genre, longest session, monthly totals — ship as standard views.
And it stays your data: full CSV export of every session means you can drop it back into the spreadsheet whenever you want to run something custom.
Common questions
- Can I import my existing reading spreadsheet?
- Yes. CSV import accepts title, author, dates, and page counts, and will create historical sessions from date ranges where present.
- Can I still get the raw numbers out?
- Yes. Every session exports to CSV with start time, duration, page range, and title.
- What if I read without starting a timer?
- Sessions can be added retroactively with a page range and an estimated duration, so a forgotten session isn't lost.
Keep reading