An action sheet consists of a list of options a user can select from to complete an action. Actions can be clustered if there is not enough space on the screen.
Use the action sheet if:
- You need an option that provides more than one action.
- It is really important that the user stays in context on a phone.
- You only have a small number of actions.
Do not use the action sheet if:
- The menu provides only one option. In this case, consider using a button instead.
- You need to show a hierarchical menu. In this case, use the menu button instead.
- Your users would benefit more from a split button, which offers an easily-accessible default action, with the option to include additional actions.
All elements in the action sheet are left-aligned. Actions are always arranged in order of importance, from top to bottom. The Cancel button uses a negative button type and is centered to differentiate it from the other app actions. The cursor/focus area for buttons within the action spans the full width of the action sheet (which in turn depends on the longest button).
Behavior and Interaction
Depending on the device, a click or tap on the overflow icon (“…”) opens either a popover or a dialog. The user can trigger an action or close the action sheet by clicking or tapping anywhere on the screen. On a smartphone, the dialog can be closed only with the Cancel button.
If the user triggers an action, the action sheet closes automatically and the system provides a message toast.
- Never use only icons in the action sheet. Display text only or a combination of icon and text.
- On smartphones, provide a Cancel button to enable the user to close the dialog without triggering an action.
- Avoid scrolling in actions sheets. If you include too many buttons in an action sheet, users have to scroll to see all the actions in the list. Not only does it take users longer to distinguish between actions, but they also find it difficult to scroll without tapping a button by mistake.
Want to dive deeper? Follow the links below to find out more about related controls, the SAPUI5 implementation, and the visual design.