Handwriting fits drawing and geometric markup better; typing fits long prose better; divide labour by content type
Aliases: content-type split · ink annotation · typing for prose
What it is
A pen’s strength is space and graphics: arrows, circles, dimensions on a figure, a symbol. A keyboard’s strength is long character strings: paragraphs, search terms, code, email addresses. Dispatching the default input by content type, to the better channel, is cheaper than switching back and forth inside one paragraph. That is not a moral claim that handwriting is more natural; it is a match of product shape.
Why it happens
Long prose needs a stable character stream, selection, spelling, and wrapping; a keyboard and recognised text beat an ink layer for later processing. Graphics and geometry have no good keyboard encoding (“draw an arrow from this point to that”); the pen does it in one act. Formulae, short markup, and signatures sit between: short and spatially fixed, handwriting is often faster; once they must be searched or pasted into mail, they need characters. The default channel can follow field type: body paragraphs summon a keyboard, a canvas summons a pen, a comment layer on a figure summons a pen. People may override; override should be the exception. Forcing long prose onto handwriting recognition trades error for a posture. Forcing dimension markup onto a numeric keypad drops the arrow’s geometry. The split also cuts switch count—switching itself costs.
Studying it
The same tasks (three captions for a figure vs three dimensions on it) under forced handwriting, forced keyboard, and type-based defaults. Log time, errors, voluntary switches.
Independent variables: whether the default follows type, field kind. Dependent measures: time, recognition/typing errors, switch count, “awkward”.
Where it stops holding
People who cannot type, or who have no keyboard (gloves, standing, no surface), must handwriting even long prose. People who cannot handwrite (motor, need a searchable draft) must be able to turn a canvas field into a keyboard. Classroom dictation may be a whole page of hand; a type heuristic will punish it. Handwriting in a code editor is almost always the wrong default.
Applying it
- Paragraphs, search, and email default to keyboard; canvas, on-figure comments, and signatures default to pen; allow override.
- Do not make the pen the only input in a long-form editor.
- Offer a pen for on-figure markup, and a type box for numeric dimensions, rather than each replacing the other.
- How to check: dimension tasks should be faster with a pen than with typed description; three captions faster with a keyboard than with whole-passage recognition. Swap the defaults; time and awkwardness should worsen. An override should be findable the first time someone uses the “wrong” channel.
Related
- Same group: C5.16.1 Mixing ink and type needs explicit join rules · C5.16.2 Switching must not drop content or the caret · C5.16.4 Switching itself has a cost and is not free
- Adjacent: C5.07 Division of Labor Between Pen and Finger · C5.06 Pen Gestures and Marking Menus
- Search:
input for content type·ink annotation·prose typing