Skip to main content

about daylogg.

I built daylogg because I'd been writing in notebooks for years and the apps kept asking for more.

I journaled in paper notebooks for years. Most days a sentence. Sometimes a paragraph. I rarely went back to read them, but knowing they existed mattered. The act of writing was what built the habit, not the length of what got written. A single line was enough.

When I tried journaling apps, every one of them asked too much. Streaks. Prompts. Mood meters. Insight cards. The friction of opening the app, deciding what kind of entry to make, picking a mood. By the time I got there, I'd lost what I came to write. I wanted ten seconds and a sentence. So I built that.


how I journal.

One sentence a day. A name, a place, a feeling, a line I'd forget by Tuesday otherwise. Some days I write more, when something specific has happened that I want to keep. Most days, less than a tweet. I write in present tense, never bullets, never curated. Years from now I'll have something to read. That's the whole point.

I don't track streaks because journaling is a long game and a missed week doesn't undo a decade. I let entries age before I read them back. The calendar view in /read pulls up what I wrote a year ago. Three years. Five. Those are the days that catch me.


daylogg has no.

  • prompts.
  • streaks.
  • notifications.
  • AI-generated reflection.
  • shareable cards.
  • shimmer skeletons.
  • analytics on what you wrote.

reaching peter.

happy to hear what daylogg gets right or wrong for you.

githublinkedinemailblog

pv.