platform-guideline 1 linked patterns checked
Android Developers: Use touch gestures
Documents Android touch-gesture support, including not depending on gestures for basic behavior, following accepted Android gesture conventions, detecting common gestures such as scrolling, flinging, double-tapping, multi-touch, dragging, scaling, and dispatching touch events to their target views.
Read with a purpose
What this source can teach
Use this source to understand a platform convention and the setting it was designed for.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Touch gesture | Choose touch gesture when the design question is the recognition, feedback, fallback, and cancellation behavior of touch input itself. | The gesture starts only from the intended target or gesture region, not from unrelated content. | Supports platform gesture conventions, common gesture detection, multi-touch, drag, scale, touch dispatch, and the warning not to depend on gestures for basic behavior. |
Comparisons supported by this source
- Touch gesture vs carousel vs map view vs bottom sheet vs drag-and-drop upload vs data visualization
Supports platform gesture conventions, common gestures, multi-touch, drag and scale, touch dispatch, and not depending on gestures for basic behavior.
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: Android Developers. Last checked: .