Motion and gesture directions must be mirrored together
Aliases: gesture-motion consistency · RTL transition direction · directional congruence
What it is
RTL gesture-motion congruence means that when navigation order reverses, the triggering gesture, current-page exit, target-page entry, and page-stack mutation must express the same forward or back state transition. Their motion vectors need not all point the same way: a page may track the hand while its neighbor enters from the adjoining side. What must agree is the causal mapping and final destination.
Why it happens
Direct manipulation depends on spatiotemporal coupling between action and feedback. A drag establishes an immediate directional prediction, animation continues its trajectory, and the landing page confirms forward or back. If one stage uses physical left/right while another uses logical start/end, a single interaction produces contradictory cues. The mismatch increases directional trial and error and can trigger the wrong navigation around edge-back gestures.
Where it stops holding
Only actions tied to reading or navigation sequence should mirror. Object rotation, map panning, drawing, game control, and media timelines usually retain an object- or domain-centered coordinate system. Operating-system edge gestures may also be reserved and unavailable for application redefinition. Where users have a strong target-platform convention, an application-specific reversal is more hazardous than consistency with the platform.
Applying it
- Model forward, back, start, and end logically, then map gesture thresholds, animation vectors, and layout positions from the active direction.
- Test drag feedback, release animation, back icon, and page-stack change as one behavior rather than configuring them separately.
- Mark object manipulation and spatial navigation as physical-coordinate interactions so RTL cannot alter maps, canvases, or rotation controls.
- With RTL users on the target platform, test repeated forward/back, cancelled drags, and rapid reversals; content must track the hand, land correctly, and avoid system-gesture conflicts.
Related
- Same group: S1.02.1 Mirroring applies to layout and direction, not every graphic · S1.02.2 Icons expressing time and progress need mirroring · S1.02.3 Icons with physical direction should not be mirrored · S1.02.4 Numbers and Latin-script runs remain left-to-right inline
- Adjacent: C4.06 Swipe and drag gestures · I4.02 Spatially continuous page transitions
- Search terms:
RTL gesture direction·motion congruence·logical navigation direction