For users in motion or those with limited control, relying on physical movements to trigger actions can be a problem.
Motion Actuation ensures that actions triggered by moving or shaking a device are optional and can be done in a different way—so a bumpy bus ride won’t interfere with your work.
Who this impacts
- People with limited motor control: Motion-based triggers can be difficult to use reliably.
- Users in motion: Whether on a bumpy commute or a walk, users need stability in their interactions without unintentional actions.
- Everyone: Options beyond motion-based inputs provide more control and prevent frustration from accidental triggers.
How to meet motion actuation
- Include non-motion alternatives: Ensure all actions that rely on device movement can also be triggered by a standard button or gesture.
- Allow users to disable motion triggers: Include an option to turn off motion-based interactions entirely so users can choose their preferred input method.
- Test under different conditions: Make sure motion triggers work as intended in various environments, avoiding accidental activation.
Practical example
Catbook allows users to shake their phone to undo a comment, but also includes an “Undo” button for those who’d rather skip the acrobatics.
Exceptions
When motion is essential to the function, such as rotating the screen, this guideline doesn’t apply.
Top tips
- Design with choice in mind: Provide easy access to alternatives for motion-based actions.
- Allow for customization: Give users the option to turn off motion-based actions for greater control over their device.
- Test for environmental triggers: Try using your app in different environments to make sure motion triggers don’t activate by accident.