Design · 4 October 2026 · 2 min

One field is a design decision - why the capture box has no title, no list picker, no buttons

Most capture forms ask for a title, a list, a date and a priority. Jot's box has one text field. Why every other field was pushed into the sentence or removed.

Open the “new task” dialog in most apps and count the fields: title, notes, list or project, due date, reminder, priority, tags, sometimes assignee. Each one is reasonable on its own. Together they turn a four-second thought into a thirty-second form.

Jot’s capture box has one text field. That was the most important design decision in the app, and it was a decision about what to leave out.

Every field is a question

A field asks the user something. “Which list?” “When?” “How important?” At the moment of capture, every question competes with the thought you are trying to save, and the thing you were doing before you pressed the key. Two questions in, people start abandoning captures or putting everything in the default list with no date.

The capture moment is the worst possible time to ask questions. So the box asks none.

Where the fields went

The information did not disappear. It moved into the sentence:

If you know these things, you type them in the same breath. If you do not, you leave them out and decide later. The structure is read out of what you wrote, and shown as small chips under the line so you can see what was understood. See four tokens and a date.

No buttons

The box has no Save button. Ctrl + Enter saves and closes; Enter saves and keeps it open for another thought; Esc closes and keeps a draft. A button invites the mouse, and reaching for the mouse is a context switch the hotkey was meant to avoid. Keyboard hints are shown as small keycaps so the shortcuts are discoverable without a tutorial.

No settings button either

There is also no gear icon in the overlay. Settings live in the app window, which you open on purpose. See the overlay has no settings button for the longer argument.

What we gave up

One field has costs:

The test we used

Every proposed addition to the box got one question: does this make the four-second case slower? If yes, it went somewhere else - the app window, a later step, or nowhere. The Nielsen Norman Group’s writing on form design makes the general case that every field you remove improves completion. For a capture box, the logic is the same, just more extreme.

Jot is on the Microsoft Store.

Jot is a quick-capture app for Windows: one hotkey, one line, back to what you were doing. What it is, or what is still unproven.