The 'swipe for action' pattern has not been applied in many apps so far, but it provides a nice and quick way to let the user choose an action he can directly perform on a certain item. The actions that are taken up should be the most important and obvious ones that can be performed on the item.
This pattern can exist in two forms. The first is explained in the wireframe: after swiping, the user can choose to perform an action by tapping on an icon. The second kind is when the action takes place directly after swiping over the item. The second set of screenshot examples show how this kind works. The user can swipe over the item in both directions. It is possible though, that the action that is performed after swiping is different in both directions.
Because of the contextual character of this pattern, you can also let a long press gesture instead of swiping, invoke the layer with actions.
The actions that can be called for on swipe, need to be contextual to the selected item, and cannot be global to the current screen. For that you should put actions in the options menu. Or, when the item was tapped and displayed on a detail page, actions can be added to a toolbar.
- It's fast
- It's fun
- When the user gets acquainted with it, he will be seriously engaged and perform the gesture all the time
- Hello! Very good job(this site)! Thank you man. (JohnBush)
- It's very hard to discover, because of the absence of a visual cue
- The item that is swiped over gets covered by a layer, so it could confuse the user which item he just selected
- It may take a while for users to get acquainted with it
- The user doesn't know which actions can be performed before he swipes over the item
- The object has to be big enough to perform a swipe over it. (Alex Debkalyuk)
- it\'s not that\'s trival to close the context menu, you have to click the Back key (cheng)