A diary without feelings is just a log
Open the App Store, search for “journal,” and you will get thousands of results. Search for “diary,” you will get thousands more. Search for “log,” and the results overlap with the first two by about half. Line ten of them up and the interfaces converge on the same shape: a date, a text field, a mood selector, sometimes a photo slot. The three words are being used to sell the same product.
The words are not the same. A log, a journal, and a diary belong to three distinct categories, and the differences matter more than the interchangeable labels suggest. Most of the apps that call themselves journals are logs with a form. Almost none of them produce a diary.
What each word is actually for
The three words answer different questions.
A log answers “did it happen?” A log exists to be referenced, usually by someone other than the person who wrote it. A captain’s logbook is read by the next captain, the insurance company, the port authority. A gym’s sign-in log is read by staff. A server’s access log is read by an engineer looking for an anomaly. The facts a log records matter because they may need to be looked up. Nothing in a log is written for pleasure, and nothing in a log is written to be re-lived.
A journal answers “when did it happen?” The word comes from jour, French for day. A journal is any record organized by day, regardless of content. A farmer’s journal of planting dates, a scientist’s journal of experiments, a merchant’s journal of transactions. A journal is a log with a calendar discipline. It is still, for the most part, a reference document.
A diary answers “what was it like?” This is the question the other two do not attempt. A diary has no external reader. The information in it is of no use to any institution. Its only purpose is to let a person, at some future date, recover the experience of a day they no longer remember.
The three categories overlap on the surface. All three are dated. All three can be read later. But they diverge on the axis of purpose. A log cares about facts. A journal cares about dates. A diary cares about meaning.
The ingredient missing from logs
A log can be correct without meaning anything. A journal can be complete without meaning anything. A diary cannot skip meaning and still be a diary. This is the whole difference.
Take any event from yesterday. You sent a message. You had a meeting. You walked home. Each of these can be captured as a fact: time, duration, participants, location. That capture is a log. You can add a date and call it a journal. Neither version tells you, or anyone else, what it was like to be the person inside that event.
The ingredient missing from a log is interpretation. Not flowery language, not emotional depth, not sentence structure. Interpretation is the act of marking which parts mattered and why, however briefly. A few words can do it: “the message I wish I had not sent,” “the meeting that ran long and left me angry,” “the walk I took the long way because I needed the extra minutes alone.”
Interpretation is what the log does not have and cannot manufacture. It is the hinge on which the entire category turns.
Why the apps collapse the distinction
Most products called “journal apps” are logs with a form field. The form assumes you will arrive at the end of the day and supply the interpretation yourself. You will open the app, read the date, look at the blank text box, and type the sentences that turn the record into a diary.
This is a reasonable architecture. It is also the reason the apps do not work for most people.
The problem is that the form asks you to produce the exact thing that is most expensive to produce. A blank box says: write what mattered about today. On a good day, that is a pleasure. On most days, it is a command to summon reflection at 11 PM, which is the time your reflection is least available. The task is structurally similar to being handed a jigsaw puzzle and told to produce the one piece you do not yet have.
Most people do not produce it. They fill in “Good day. Productive. A bit tired.” and close the app. The record now exists, technically. But it is not a diary. It is a log with a mood emoji and three generic adjectives. The part that would have made it a diary was left to someone who had already been asked for too much that day.
The failure mode is not laziness. It is an interface designed to collect a product that cannot be manufactured on demand.
What automatic journaling adds, and what it does not
deariary is built against this problem. Instead of asking for the interpretation at the end of the day, it reads the data your day produced in the tools you were using (calendars, tasks, messages, check-ins, commits, posts) and assembles a narrated paragraph from it. Not a bullet list. Not a dashboard. A paragraph that reads in the order the day unfolded and joins the separate facts with ordinary connective prose.
Here is the honest version of what that is. A narrated paragraph is not yet a diary. It is much closer than a bullet list, and more useful than a form the user never filled in, but it is still a third category. The missing ingredient is still interpretation. An automatic entry can say that you had coffee with a friend at 10 AM. It cannot say that the coffee was the best thing about the day, or that the friend is moving in August, or that you suspect you will not see them again. Only the person who was there can mark those parts.
What the automatic entry can do is make the marking cheap. A blank page asks you to produce the meaning and the context together. An entry that already contains the context asks only for the one thing the writer can contribute: a sentence that says what mattered. Two words of annotation can convert the whole paragraph. “Laura is moving.” The narrated facts around that sentence immediately become a diary entry, because the reader now knows which part of the day carries the weight.
Most users never add the sentence. And something interesting happens anyway.
The re-reader supplies what the writer did not
There is a second path from log to diary. Not through interpretation at the time of writing, but through re-reading at a later date.
When you come back to a detailed entry from a year ago, your present self supplies the meaning your past self did not. You read “coffee with Laura at 10:30” and remember (or are reminded by the name on the page) that Laura moved to Lisbon in August, that the coffee was one of the last ones you had together, that you did not realize it at the time. The entry did not contain that knowledge. You brought it. The log, in your hands, has become a diary without ever being written as one.
This is why coverage matters more than craft for the kind of record that has to survive for years. A log rich in names, places, and small facts is a diary waiting for its reader. A handful of beautifully written sentences per day is usually a diary only to the person who wrote it, and only in the weeks immediately after. A complete narrated record of the day is a diary to a future self with no effort required from the past self at all.
We wrote about this effect in more detail in Re-reading your diary three months later, which is worth reading if this idea is new. The short version is that the experience of returning to a full, boring-looking record of an ordinary day is almost nothing like what you expect before you have tried it.
A diary is a retroactive category
The shortest way to put all of this is that “diary” is a retroactive label. Nothing you write today is a diary yet. What you write today becomes a diary on the day someone reads it and feels something the writer could not have felt while writing. If that day never arrives, the record stays a log, no matter what word was printed on the cover.
The good news is that the becoming does not require the writer to be a diarist. It requires a complete record, and a person willing, on some later day, to open it.
Most apps ask you to be the diarist. They ask for the interpretation up front and leave the archive thin because the interpretation is hard. An automatic record flips the order. Build the complete log first. Let it accumulate. The interpretation arrives, later, from the only person who can produce it, at the only moment when it is cheap.
deariary does the recording automatically, from the tools you already use. The diary part happens when you come back to read.
