Word, sentence, and paragraph granularity reduces the need for fine aiming
Aliases: double-tap word · triple-click paragraph · granularity selection
What it is
Most edits want not “character n through m” but this word, this sentence, this paragraph. Hierarchical selection hits those linguistic units with a double tap, triple tap, or long press, so selection ends land on lexical or syntactic boundaries rather than on the gap a finger happened to hit. Fine handle-dragging becomes the exception, not the path every copy must take.
Why it happens
Natural language already has cuts: spaces or a segmenter give words, terminal punctuation gives sentences, blank lines give paragraphs. The system maps a tap onto the unit that contains it and snaps both ends to that unit’s boundary. What the user is spared is two precise gap aims. Only when the unit is wrong (part of a word, or half a sentence across a period) does the task drop to handle nudging. Hierarchy lifts aiming from a character gap to an object-sized target: a word’s visual block is far larger than a gap, Fitts time drops, and the miss shape changes from “off by one character” to “grabbed the neighbouring word,” which is easier to see. Segmentation must match the user’s language: Chinese has no spaces, word edges depend on a segmenter, and a wrong cut makes hierarchical selection feel arbitrary.
Studying it
Give real edit tasks (change a word, copy a sentence, delete a paragraph) and compare handle-only against word/sentence/paragraph shortcuts on completion time and handle-drag count. Independent variables include language (spaces or not), whether segmentation is visible, and whether the gesture is double tap or long press. Dependent measures include unit-hit rate, subsequent handle repairs, and accidental expansion into a neighbouring sentence. Do not score only “final selection correct”: if many handle drags happened in between, hierarchy did not reduce fine work.
Where it stops holding
Code, paths, and unwrapped long URLs have no sentence structure; hierarchy will select a whole line or a nonsense fragment. Table cells and interiors of formulas define “word” differently. Keyboard accessibility maps hierarchy onto unit jumps such as Ctrl+Shift+arrows: the gesture itself does not apply, the unit levels still do.
Applying it
- Offer stable gestures for word, sentence, and paragraph (for example double-tap word, triple-tap paragraph), and still allow handles to shrink after the snap rather than forcing cancel-and-retry.
- For unspaced languages, expose segmentation or allow an immediate shrink to characters, so “I wanted two characters” is not answered with a whole word.
- In logs, see whether copy/cut was preceded by handle nudges; if most tasks still drag after a unit snap, the cut does not match the grain users want.