What did I do today? Let your apps answer.
You ask yourself this at the end of every day. Sometimes out loud, sometimes as a half-conscious thought while staring at the ceiling before sleep. “What did I do today?”
And the strange part is: you cannot answer with confidence, even though the day only ended minutes ago.
The question with no clean answer
It is not that nothing happened. You worked. You ate. You exchanged messages with people. You moved between tasks, made small decisions, got stuck somewhere and then unstuck. The day was full. But when you try to account for it, the account is thin.
“I was in meetings most of the morning. Worked on some stuff in the afternoon.” That is what comes out. Not because your day lacked content, but because the content lived in ten different places while it was happening, and no single place holds the whole picture.
Your calendar knows about the meetings but nothing about the two hours between them. Slack knows about the conversations but not why they mattered. Your task manager knows what you checked off but not the order you worked in or how long anything took. Each tool holds a fragment. None of them holds the day.
Scattered witnesses
Think of your apps as witnesses to your day. Each one saw a piece of what happened, from a specific angle, through a specific lens.
Your calendar saw the scheduled blocks. It knows you had a design review at 10, a one-on-one at 2, and a team standup at 4:30. It does not know that the design review ran long and ate into your focus time, or that you spent the gap before the standup reading documentation rather than writing code.
Your task manager saw the checkboxes. Three tasks completed, one moved to tomorrow. It does not know you finished two of those in a single burst before lunch, or that the third took four attempts across the afternoon.
Your messaging app saw the words you exchanged. Twenty-three messages in three channels. It does not know which conversation changed your plan for the day, or which one was a distraction you wish you had ignored.
Your code repository saw the commits. Two pull requests opened, one merged. It does not know that the merged one was the culmination of a frustrating morning, or that you are proud of how the second one turned out.
Each witness is credible. Each witness is incomplete. And none of them will ever compare notes with the others on their own.
The filing cabinet problem
You could piece it together manually. Open the calendar, cross-reference with Slack, check Todoist, scan your commit history. In theory, everything is there.
In practice, nobody does this. It would take fifteen minutes. You would need to hold the timeline in your head while jumping between tabs. And by the time you finished, you would have a rough mental summary that fades by morning, just like the one you started with.
The data is not missing. The assembly is. Your day is a filing cabinet where every drawer belongs to a different app and none of them share an index. The information exists, but it is organized by tool, not by time. No single interface shows you 9 AM through 6 PM as a continuous story.
This is why “what did I do today?” feels hard to answer even when you are still inside the day. The answer is not in your head. It is in your apps. And your apps are not talking to each other.
A day in fragments
Consider a specific example. A Wednesday.
At 9:15, you joined a product sync on Google Calendar. At 9:48, you posted a summary in the team Slack channel. Between 10 and 12, you worked through three Todoist tasks, completing two. At 12:30, you pushed a commit to GitHub that you had been working on since the previous evening. After lunch, you had two back-to-back meetings. At 3 PM, you reviewed a pull request. At 4, you picked up the Todoist task you had not finished and moved it to Thursday. At 5, you sent a message in Slack about tomorrow’s plan.
That is a full, productive Wednesday. Every event in that sequence was captured by an app. But no app captured the Wednesday. Google Calendar saw three colored blocks. Todoist saw two completions and a reschedule. GitHub saw a commit and a review. Slack saw a handful of messages. None of them know it was a day, or that it was yours.
The fragments are accurate but meaningless in isolation. The day only exists as a day when they are laid side by side.
The answer your apps can give
When those fragments are assembled chronologically, something happens. The day acquires a shape.
You can see that the morning was meetings and communication, that late morning was your most productive coding window, that the afternoon was collaborative, and that you ended the day by planning ahead. You can see the rhythm: high-context conversation, then deep work, then reviews, then wind-down. That rhythm was invisible to any single app. It is only visible in the composite.
The assembled day also reveals things you did not notice while living it. That the task you pushed to Thursday has been pushed twice before. That you wrote more Slack messages on this Wednesday than any day last week. That the gap between your last meeting and your last commit was unusually short, meaning you shifted from meetings to code without a break.
These are not insights from a productivity dashboard. They are details of your day that only become legible when the pieces are in one place. The answer to “what did I do today?” is not a number or a score. It is a readable account of how the hours actually went.
A diary entry, not a report
There is an important distinction between an activity log and a diary entry. A log lists what happened. A diary entry tells you what a day felt like.
The difference is in the composition. “Pushed commit abc123 at 12:32 PM” is a log entry. “Finished the authentication refactor right before lunch, after working on it across two days” is a diary entry. Both describe the same event. The diary entry gives it context, connects it to the arc of the week, and makes it recognizable to you when you read it three months later.
deariary connects to the tools you already use, collects the fragments they recorded, and composes them into prose. Not a bullet list of timestamps. Not a dashboard. A paragraph you can read in thirty seconds that tells you what your Wednesday was actually like.
The answer to “what did I do today?” stops being a question you fumble through. It becomes a page you can read.
Tomorrow, you will not remember today
This matters because the question is not just about today. It is about every day.
You will ask “what did I do today?” again tomorrow. And the day after. Some days you will have a clear answer because something memorable happened. Most days you will not, because most days are ordinary. Those ordinary days are the ones that disappear first, and they are also the ones that make up most of your life.
If the answer is already in your apps, it does not need to disappear. It just needs someone to assemble it.
