Mobile Bewegung und Haptik

Motion & Haptic Feedback Design

Use motion and haptics purposefully to orient the user, communicate spatial relationships, and confirm actions without slowing down tasks.

Purposeful Motion

• Spatial orientation: Use transitions to show where a screen comes from and where it goes (hierarchical push/pop, modal sheet slide-up/dismiss, shared-element expansion) so users maintain a clear mental map.
• Fast & responsive timing: Keep mobile transitions crisp and non-blocking (typically 150–300 ms); never let decorative animation delay user input or block navigation.
• State continuity: Use subtle layout transitions and skeleton-to-content crossfades to prevent jarring layout jumps when asynchronous data arrives.

Haptic Feedback

• Meaningful tactile cues: Pair light/selection haptics with discrete physical interactions (picker detents, toggles, pull-to-refresh threshold) and distinct notification haptics with important outcomes (success, warning, error).
• Avoid haptic noise: Do not attach haptics to every tap or scroll event; overuse dulls their signal.

Accessibility & Fallbacks

• Reduced motion support: Specify how transitions behave when prefers-reduced-motion / OS Reduce Motion is enabled (replace large spatial slides, zooms, or looping motion with instant state changes or subtle opacity fades).
• Multi-sensory redundancy: Never rely on motion or haptic feedback alone to communicate critical status or errors; always pair them with clear visual and screen-reader-accessible feedback.

Handoff & Acceptance

• Specify each meaningful cue's trigger, purpose, duration, cancellation behavior, final screen/focus state, and reduced-motion or no-haptics fallback. Tie success cues to confirmed outcomes; suppress duplicate cues from repeated renders or resumed requests.
• On a supported target device, try reduced motion, disabled/unavailable haptics, rapid repeated input, interrupted navigation, and background/resume. Verify input remains usable, cancellation leaves a coherent screen and focus, and status remains understandable visually and with a screen reader. State when validation used only a simulator or prototype; do not claim physical haptic quality from either.