Deformation mechanisms are far coarser and slower than a visual display of the same size

What it is

A palm-sized screen has millions of pixels and sixty-plus frames; a pin or bladder array of the same size may have tens of cells across and refresh a few times a second. Deformation is far coarser and slower than a same-size display—not because the implementation is unfinished, but because mass, travel, and force set a floor. How fast a deformation must be to be perceived is another layer. This one compares the two channels fighting for one area: deformation is destined to be sparser and slower, so it cannot be planned as “a display you can touch.”

Why it happens

Each moving cell must accelerate mass, beat seals and friction, and travel millimeters; power and volume scale with cell count. A pixel changes an electric field, with almost no inertia. In the same area, deformation cell count drops by orders of magnitude, and temporal bandwidth is stuck at mechanical resonance and thermal/pneumatic time constants. Content built for a screen’s fineness and frame rate—scrolling, animation, small type—turns the deformation channel into jittering steps. What it can carry are slowly updating, large features: a patch of terrain, a stiffness, a raised control—not a scrolling list. When stacked with a screen, the screen takes high bandwidth and deformation takes the layer the hand must measure. That split belongs in content design, not in hoping the next pin generation catches 4K.

Studying it

Downsample the same content to the array’s pitch and frame rate, and see which tasks survive and which die.

Independent variables: cell pitch, maximum refresh, content type (static terrain / scrolling / animated control). Dependent measures: task completion, vection or waiting, whether people switch to watching a neighboring screen.

Demos of carefully chosen static relief overestimate the channel. Include one animation built on screen habits. Measure time from command to settled height, not only the controller’s command rate.

Where it stops holding

When visually impaired users take deformation as the primary display, there is no “screen beside it” to split with; content must be written to deformation bandwidth, not assume people will look. Fingertip micro-arrays can be denser, with less travel and force; they are not necessarily faster. An image projected on a deforming surface can be very sharp—that is the pixel channel, not deformation resolution. Heat and pneumatics can be fast in some materials, usually by giving up travel or force; the three will not catch a screen at once.

Applying it

• Write content to the deformation’s cell pitch and settle time; do not move UI animation onto it.
• When stacked with a screen, type, scrolling, and color stay on the screen; slope and stiffness stay on deformation.
• Verify: play an existing UI downsampled to the array’s spec and list tasks that break. Those tasks stay on the screen. Measure height settle time as the length of “one frame.” Do not advertise deformation resolution with projection sharpness.

Related

• Same group: C10.15.1 Physical pixels (pin arrays) present shape and texture by locally raising a solid surface · C10.15.2 Deformation output can carry 3D geometry or stiffness that digital content cannot present · C10.15.4 Mechanical parts in a deforming interface wear and drift more than a purely electronic display
• Adjacent: C10.06 Shape-Changing Interfaces · C10.16 Mechanical Reliability and Lifetime
• Search: actuation bandwidth · shape refresh rate · pin resolution