Gesture typing turns discrete taps into a continuous path
Aliases: glide typing · swipe typing · ShapeWriter
What it is
Gesture typing (shape writing) does not split a word into independent taps. The thumb traces a continuous path on the key plane: down on the first letter, through the middles, up on the last. The system matches that path as the shape of a word, not as a sequence of hit-tests. Tapping is a string of aims; gliding is one open-loop gesture.
Why it happens
Per-key tapping demands a Fitts aim and a lift for every letter, plus a lift between letters. Gliding folds those discrete constraints into one path: once the movement starts, middle letters only need the trajectory to pass nearby, not to stop on each key. A word forms a relatively stable polyline template on the keyboard geometry; recognition compares shape to template rather than point hits. Time structure therefore resembles one ballistic action plus a terminal correction, and throughput is no longer capped at “letter count × time per tap.” The cost is that the path must correspond to a word that can be templated: spaces, punctuation, and one-letter words still fall back to taps, so two motor programs have to coexist on the same key plane.
Studying it
A contrast task has people enter the same word set by tapping and by gliding, logging time per word, path length, and mid-word switches to tapping. Independent variables include word length, key width, whether the keyboard is visible, and a residual ink trail; dependent measures include time per word, abandoned gestures, and the fraction that revert from glide to tap. WPM alone hides which words cannot be glided. Count words that cannot be glided (punctuation, digits) separately.
Where it stops holding
One-handed on a large screen, the path spans half the display and the ballistic advantage is eaten by distance. On a nine-key pad letters overlap, path shapes collapse, and gliding degrades into a meaningless polyline. Fields that must be letter-exact (passwords, short codes) should not take gliding as the main path. A system with no word templates (lexicon off) cannot glide.
Applying it
- Offer gliding for word-sized short text, and keep per-key tapping; do not turn one of them off.
- Draw a brief residual trail so people see which polyline the system is following, rather than only popping a word on lift.
- In acceptance, report completable-by-glide and not-glidable words separately; errors from forcing a non-glidable word through a glide are a product problem, not a user who “cannot swipe.”