Return should reverse the forward direction

What it is

If forward was a push from right to left, return should play that same displacement backwards rather than picking another axis to whisk the page away. Return is an undo in time, so its direction has to be the mirror of forward for it to be perceived as going back the way one came. Closing a right-arrived page out the bottom sends the person down a different corridor.

Why it happens

Motor systems expect reversible trajectories: the path that arrived can be retraced. Playing the forward path backwards visually walks the object file back to its origin, so stack pop and spatial retreat coincide. If return takes a vertical axis, there is nothing to reverse; the step must be recoded as a new navigation rather than an undo. Failed undo feels like “I was moved somewhere else,” even when the document structure has already restored the previous page.

Gesture back makes the coupling brutal: the finger drags against forward, but the picture drops downward, and the perception–action loop conflicts. The gesture is then judged broken or accidental.

Studying it

Hold forward direction fixed, pair it with a mirrored return versus an orthogonal-axis return, and measure time to re-orient after return, whether people re-enter the level they just left (thinking they never went back), and completion of a back gesture. Independent variables: whether return is the time-reversal of forward, whether a gesture is used. Dependent variables: re-orientation time, re-entry rate, gesture abandonment.

Eye movements on a mirrored return should retrace the original path; an orthogonal return typically triggers a fresh search.

Where it stops holding

• If forward had no travel (a fade), return has no trajectory to reverse; the counterpart is the same fade out, not a newly invented slide.
• A system-level “swipe up to dismiss” that was never used for forward is not the reverse of a push; it is a separate dismiss grammar and should not be named as stack return.
• When a shared element succeeded on the way in, return should reverse that morph rather than run a page-level slide, or the identity weld is torn on the way back.

Applying it

• For every forward transition, write its time reversal: same axis, same object, opposite direction.
• A back gesture’s drag axis must be the axis of that mirrored displacement; after release, finish along that axis.
• Check: play forward and return as a pair, then reverse the pair. If the reversed clip does not match forward, return is not a reverse.

Related

• Same group: F7.05.1 Direction encodes entering and leaving a hierarchy · F7.05.2 Inconsistent direction breaks the spatial model
• Nearby: G4.01 Back stack and back semantics · F7.04.1 A shared element keeps the object's identity continuous
• Search terms: reverse transition · back gesture · time reversal