N3.10.4surface snappingdesignresearch

Snapping a panel to a surface removes several clipping classes at once

Aliases: plane snap · stick-to-surface · UI on surfaces

What it is

A panel floating in the middle of a room fights for volume with hands, with people walking past, with a chair back leaned into, with a lamp arm that stabs across. Surface snapping — to a desk, a wall, the face of a monitor — makes several of those volume fights vanish together: no growing out of the wall, no fighting the tabletop for thickness, no standing in the walkway waiting to be walked through. Snapping does not make depth estimation more accurate. It takes the UI out of the empty regions where clipping is most likely.

Why it happens

A free-floating thin plate has two faces and a rim, with enterable cavities on every side. Stick it to a physical surface that already exists and the back-side class of interpenetration is forbidden by the surface itself — content cannot grow out of the wall because it is spawned at a safe offset in front. Body clipping in the walkway is removed because the panel is not in the walkway. Hand clipping remains, but becomes “sliding on a desk” rather than “grabbing an unresisting plate in mid-air”, and contact has a real table edge as reference. Snapping also collapses environment-depth error from 3D to a 1D offset along the normal: a little float if the estimate is shallow, a little embed if it is deep, easier to repair than a simultaneous x/y/z bias in a cavity. The cost is the viewing angle that floating had bought, and dependence on that surface still being there — move the chair, and the snap point is void.

Studying it

The same task in three placements: free-floating, snapped to a horizontal plane, snapped to a vertical plane. Deliberately send a hand, a second person, and a chair back into the panel’s volume.

Independent variables: placement mode, surface type, safety offset on or off, whether the surface is removed mid-task. Dependent variables: clipping-event counts by class (hand, body, furniture, wall), completion time, time to recover after the placement is broken, a rating of “is this plate still in the way”.

Count clipping by class; do not collapse to one score. Snapping claims to remove several classes at once — which class remains must be visible.

Where it stops holding

Empty lots, outdoors, and pure voids have no plane to snap to; floating remains the only option and clipping must be handled another way. A 3D object that must be orbited (a sculpture, a part) is wrecked by being stuck to a wall. On optical see-through a bright panel stuck to a wall still cannot hide the wall’s real texture; snapping removes geometric interpenetration, not optical covering. Vertical surfaces are harder on the arms than horizontal ones: a wall menu raises the shoulder. When plane detection fails, a wrong snap (onto a phantom mid-air plane, onto glass) creates new clipping and must be undoable.

Applying it

  • Offer “stick to desk / stick to wall” as the default for reading and operating panels. Floating is an explicit exception, not the default.
  • Snap with a small safety offset along the normal so a slightly deep depth estimate does not embed the panel; keep the offset small enough that “on this surface” still reads.
  • When the snapped-to surface vanishes or moves, let the panel follow briefly and then prompt to re-stick. Do not leave it in mid-air pretending it is still attached.
  • How to check: after snapping, have someone walk through the volume where the panel used to float, reach, and lean a chair back. If clipping remains in those classes, snapping did not remove them. If only “hand sliding on the desk” remains, that is residual hand contact and is handled elsewhere.

Related

  • Same group: N3.10.1 A hand clipping through a virtual object is the most glaring class of interpenetration · N3.10.2 Disabling the depth test to force a panel on top wrecks the whole scene · N3.10.3 Environment-depth accuracy sets how bad real–virtual clipping becomes
  • Nearby: N3.03 Depth Conflict · N5.03 Plane Detection and Environment Understanding · N2.12 Precision Loss Without Physical Support
  • Search terms: surface snapping · plane snap · UI on surfaces

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/N3.10.4