Drag may start from a long-press or from an immediate down, with different meanings

What it is

Moving an object from one place to another on a touchscreen has two starts. One holds until the object is “peeled off,” then moves. The other follows the finger from the first down—sliders, hue rings, and canvas anchors usually do this. Both are drags. They declare different intent: the first says “I am taking this object out of scroll and other gestures”; the second says “this control’s job is to be dragged.”

Why it happens

The default vertical motion of a list or grid is to roll content, not to carry an object. If down immediately hands the pointer to drag, an ordinary page flip walks a row away. A long-press start is an explicit arming: duration tells the recognizer “this is a carry now; scroll stands down.” Immediate-down start requires that the object itself be a continuous manipulator, with no competing scroll, or that the hit region be a dedicated handle. The two armings change which gesture wins, not the kinematics of tracking. After pick-up the object usually enters a floating layer and drop semantics begin; immediate drag often has no pick-up phase, and displacement is the value.

Studying it

Run a carry task inside a scrollable list, comparing a long-press arm with drag-on-down. Independent variables include arming duration, a visible drag handle, row height, and whether scroll inertia is on. Dependent measures include scrolls read as carries, intended carries that flipped the page, and aborts during arming. Mixing slider widgets and list rows in one experiment entangles the two meanings; report them as separate tasks.

Where it stops holding

On a desktop, dragging a title bar is immediate-down because the pointing device has no scroll gesture competing with it. Shipping that habit into a phone list fails. In a drawing app the stroke is a drag; wrapping it in long-press arming makes every mark sticky. If the system already uses long-press for a menu, arming drag with the same hold collides two second meanings; drag then has to move to a handle or an edit mode. Reordering a string of icons with yielding animations is a later sorting gesture, not this start-semantics question.

Applying it

• Arm objects that live in scrollers with a long-press or a visible handle before dragging. Use drag-on-down for controls whose job is a continuous value, and keep their hit region out of the page-flip fight.
• Signal a successful arm with a state jump (lift, shadow, a gap opening among neighbors) so people know they are carrying, not scrolling.
• Record “I only wanted to flip the list” and “I wanted to carry item three to slot seven.” The first must not float a row; the second must not scroll away a screen. Each failure is a start used in the wrong scene.

Related

• Same group: C3.04.2 Competition between drag-start slop and scroll-direction discrimination · C3.04.3 The drop target must stay visible during a drag · C3.04.4 Auto-scroll and speed when a drag hits the screen edge
• Adjacent: C3.03 Long press · C3.07 Pan
• Search: drag start · press-and-hold to drag · drag handle