Every function still has to work without the pen

What it is

A tablet can ship with a pen, but the pen is not part of the device: it is in the silo, in a bag, dead, borrowed, or never paired on this shared unit. Pen-optional reachability means every step of the task—including markup, signing, and precise hits—can still be finished with fingers and system controls alone. A division of labor can make the pen-present path smoother. It cannot make the pen the only path. This is not the desktop case of “no mouse, use the keyboard”: a keyboard is a resident desktop device, a pen is a detachable accessory to a tablet.

Why it happens

A pen supplies pressure, tilt, hover, and nib-level precision that fingers do not match. If the product writes those abilities as the only path—markup opens only with the pen, tiny controls hit only with a nib, a signature field rejects a finger—the task ends when the pen is absent. Reachability is not faking pressure with a pad. It is a second path for the same intent: a tool button that enters markup for a finger, hit targets sized for a pad, a signature that accepts a finger stroke or a typed name. In classrooms, counters, and living-room sharing, a missing pen is the normal case. Treating the pen as default input locks those people into a demo. Pens are also easier to lose and easier to drain than the tablet, so the failure mode is more frequent than touch failure.

Studying it

Run the same task set twice: pen in hand, and pen removed (or the digitizer disabled in software). Cover markup, signing, fine selection, and ordinary navigation.

Independent variables: whether key commands are pen-only, whether hit targets are sized for a nib, whether an equivalent finger or button path exists. Dependent variables: completion without the pen, extra steps on the fallback, points of abandonment.

A faster pen-present path is not a defense of pen-absent failure—the comparison is “can it be finished,” not peak efficiency. If participants get up to fetch a physical pen, the task has already been designed around the accessory. Shared-device sessions should actually omit the pen, not leave it within reach and pretend it is gone.

Where it stops holding

Professional drawing, CAD, and music engraving can treat pressure and tilt as core; without the pen they may degrade to “view and select, but not draw at native precision,” provided the degradation is stated and the canvas is not silently locked. If a legal signature must be a handwritten trace, a finger stroke may not qualify; the pen-absent path is then an uploaded scan or a qualified e-sign, not a pad pretending to be a nib. Hover preview does not exist without a pen, so information that appears only on hover cannot be required. Active-pen protocols differ by platform; a synced “pen gesture” is even less entitled to be the only entry.

Applying it

• Inventory every action that looks pen-shaped and give it a finger or control path: a markup tool button, larger drag handles, an ink toggle that draws with a pad.
• Size hit targets for touch. The pen can use the same larger area; precision comes from contact classification, not from a smaller hot zone.
• When the pen disconnects, dies, or was never paired, do not lock the canvas read-only without saying so. Offer “write with finger” or another input.
• Verify by taking the pen into another room and walking the main path. Any step that says “use the stylus” with no alternative has written the accessory as if it were the device.

Related

• Within the group: K3.02.1 Pen and finger need an explicit division of labor · K3.02.2 An inconsistent mapping makes every contact a test
• Adjacent: C5.07 Division of Labor Between Pen and Finger · C5.17 Pen Pairing, Battery, and Loss · K3.04 External Keyboard Mode
• Search terms: pen-optional · stylus fallback · input reachability