Overview
How might we design gesture input so people can trust and act on AI output?
When this pattern fits
- Ideal for touch interfaces, creative applications, and mobile tools where gesture-based input provides intuitive, natural interaction methods.
When to skip or lighten it
- Precision tasks better served by keyboard shortcuts.
- Accessibility requirements mandate non-gesture alternatives.
- Gesture recognition latency breaks drawing flow.
States
State model coming soon
Key UX elements
Key UX elements coming soon
Anti-patterns to avoid
Gestures with no on-screen legend or tutorial.
Conflicts with OS-level system gestures.
No undo when gesture misfires.
Requiring perfect shapes with no tolerance.
How products use it
| Product | Implementation |
|---|---|
| Apple Pencil | Scribble and lasso selection in Notes and markup. |
| Samsung S Pen | Air actions and circle-to-search gestures. |
| Surface Pen | Ink to shape and gesture shortcuts in Windows ink. |
| Creative apps | Circle lasso for AI edit regions on canvas. |
Implementation
Copy this prompt to generate a production-ready implementation in Cursor, Claude Code, Lovable, or any AI coding agent.
Generate a production-ready implementation of the "Gesture Input" AI interface design pattern.
Pattern Definition:Frequently asked questions
What gestures work for AI actions?
Circle to search, lasso to inpaint, swipe to dismiss suggestions, pinch to zoom canvas regions.
Feedback during gesture?
Show live stroke, recognized intent label, and cancel zone.
Gesture vs voice commands?
Gestures are spatial on touch or pen. Voice commands are spoken action triggers.
Discoverability?
First-run overlay, settings cheatsheet, and hover hints on pen hover where supported.