C5.07.1Pen inks content, finger operates the viewdesignresearch

Pen for stroke content and finger for the view is a common division

Aliases: pen inks · finger navigates · bimanual tablet

What it is

On a touch-capable pen device, a stable split is: the pen deposits content (ink, markup, selection) and the finger operates the view (pan, zoom, page, tool taps). The nib addresses objects in document space; the finger addresses the camera/viewport. That is not a law of physics. It is a contract that cuts mode switching: people need not pick “brush / hand” before moving.

Why it happens

Pen events carry pressure, tilt, and a high sample rate, which suit a visible trail; finger events are large contacts that suit two-finger scale gestures. Routing the two device types to different semantics lets the system dispatch on hardware rather than toolbar state. Typical map: pen move draws ink; one-finger drag pans; pinch zooms; finger tap hits UI. Palm rejection fits this split—the palm is a suppressed third contact, the finger an admitted second effector. The split also matches two hands: the dominant hand writes, the other pinches or taps tools on the left, and the two motions do not share hit-testing. If both pen and finger can ink, every canvas contact must guess intent, and view operations interrupt ink. If the pen cannot pan, a one-handed user must put the pen down to touch, and the contract shrinks to two-handed use.

Studying it

Compare three dispatch rules: pen-inks / finger-views, both can draw, both can pan. Tasks mix annotation and inspection (write a line, zoom elsewhere, write again).

Independent variables: dispatch rule, whether the pen may pan, whether a hand tool remains on the bar. Dependent measures: unintentional ink, times the pen is put down to zoom, mode errors, completion time.

Log which hand did view operations, to see whether the contract became true bimanual work or only a slogan.

Where it stops holding

When only one hand is free (holding a book, on a train), finger-for-view may be unreachable; the pen needs a way to pan (a barrel button remapping). A finger-only device has no such contract. Some people use the pen as a pointer on buttons; forcing “only fingers hit UI” wastes hover. Finger painting as content is legitimate in drawing tools and must not be cut by “fingers only navigate”, but it should be an explicit on-switch.

Applying it

  • Default: pen into document content, one/two fingers into the viewport; say so in settings, not only in marketing.
  • For one-handed use, offer a barrel button or a temporary hand so the pen can pan; do not default to both effectors inking.
  • Let the pen still tap finger-oriented UI so buttons are not finger-only.
  • How to check: write a passage with zoom and paging; count pen-downs and unintentional ink. Turn the split off (fingers can draw) as a control; unintentional ink should rise. Repeat one-handed and confirm a temporary hand exists.

Related

  • Same group: C5.07.2 The division must stay consistent or people probe every time · C5.07.3 Every function must remain reachable without the pen
  • Adjacent: C5.04 Palm Rejection · C5.16 Switching Between Handwriting and Typing
  • Search: pen finger division · ink versus navigation · bimanual tablet

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/C5.07.1