When actions overflow one screen, scrolling weakens how scannable the sheet is

What it is

An action sheet is valuable when the verbs for this object can be seen in one glance. When there are more items than one screen holds, the sheet must scroll, and scanability is cut: a verb off-stage might as well not exist, so people conclude there is no Export when it sits below. Scrolling turns simultaneous comparison into memory comparison; the sheet starts to behave like a menu you flip through, not a list you scan.

Why it happens

Scanning wants every candidate on stage. That is especially true of an action sheet — people do not look up a verb alphabetically; they compare a few verbs and pick the one that fits the task. One screen that clips the lower half leaves a partial comparison set, so the user either takes an adequate verb in view or never learns that scrolling is possible. Gestures on a bottom sheet also compete with swipe-down-to-close: intending to scroll for more can dismiss the sheet. Without an overflow cue, the scroll channel itself is undiscovered. Item count grows with the product; perceptual capacity of the sheet does not. Once the list leaves one screen, the discovery cost of each extra item jumps, because one must first know “there is more,” then scroll, then search.

Studying it

Present the same verbs as fitting on one screen, just overflowing, and overflowing a lot, with the target in the first screen or in the overflow. Record time to find, false “does not exist,” and swipe-down dismissing the sheet. Independent variables: item count, overflow cue, whether scroll and dismiss gestures are separated. Dependent variables: discovery of overflow items, accidental dismiss. A target in overflow with no cue should produce the most “does not exist” errors.

Where it stops holding

Section headings can pack a little more onto one screen; they do not make capacity infinite. Desktop menus keep scanning with separators and extra columns; a bottom sheet rarely has extra columns. Experts remember “Export is below,” so skill patches scroll cost; new users and new actions still fall into the clipped stretch. Parking overflow in a “More” sub-sheet trades a jump for a one-screen scan, swapping discoverability for hierarchy, which must be weighed on its own rather than pretending it is still one sheet.

Applying it

• Keep persistent actions on one screen. Send infrequent ones to “More” or to the object’s detail, rather than stacking forever.
• If overflow is required, show a sliver of the next item, and make the scroll gesture easy to tell from swipe-down-to-close.
• Order by use, not by engineering module, so the first screen covers high frequency.
• How to check: put the target below the first screen and give no hint that scrolling exists. Not finding it, or dismissing the sheet, means capacity is already exceeded.

Related

• Within the group: E4.15.1 An action sheet is for several actions that apply to the current object · E4.15.3 Destructive actions must be visually separated from ordinary ones
• Adjacent: E4.05 Inline and bulk actions · E5.15 Number of navigation items
• Search terms: action sheet length · scanability · bottom sheet scroll