# Why chat is the right interface for personal data

> Forms fail at the moment of capture. A conversation does not. What that means for how tasks, notes and tables should be created — and what it does not mean.

Canonical: https://memtomo.com/en/blog/why-chat-is-the-right-interface/

Every productivity app dies the same way. You install it with good intentions, enter things for two weeks, and then one evening you have a thought worth keeping and the app is three taps and a form away. You do not open it. The thought is gone, and so, a month later, is the habit.

## Capture is the whole game

The value of a task list is proportional to how much of your life actually ends up in it. Every field in a form is a place to lose the user: which project, which date, which priority. The tools that survive are the ones with the shortest path from thought to record — a text message to yourself, a line on a notepad.

A conversation is that shortest path with a brain attached. “Remind me to call the dentist tomorrow at 3” carries the object, the time and the intent. There is nothing left to fill in.

## What chat is bad at

Reading. Nobody wants to scroll a conversation to find last week's tasks. Chat is the right interface for *creating*; lists, calendars and editors remain the right interface for *reading and editing*. So the assistant creates a real object with a real card, and the app is where that object lives afterwards. The chat is never the store.

## Structure without forms

The trick is that the structure still exists — a task has a status and a due date, a table has columns and types — but it is inferred from what you said rather than requested from you. When the inference is wrong you say so, and the correction is one more sentence, not a settings screen.

## The rule we build by

If something can be created by saying it, it must be. If something is better read in a list, it must have one. Everything else is decoration.