An action sheet is for several actions that apply to the current object

What it is

An action sheet rises from the bottom edge and lists actions that apply to this object: share this, delete this, move this to an album. It is not global navigation and not a settings page. The sheet’s subject is the row just selected or long-pressed; every verb should take that object as its object. Once the object drifts into “things the app can do,” the sheet becomes a junk drawer, and scanning is no longer a search among one object’s verbs but among unrelated verbs.

Why it happens

An action list compresses choice by keeping the object on stage. The user has just pointed at a record (long-press, overflow); working memory holds that object, and the sheet only has to list verbs that can take it. With a clean scope, even a longer list can be scanned by semantic group. Mix in account-level or app-level actions and the object is washed out; every row has to ask “to whom.” Rising from the bottom also helps: it covers the content region, not the nav region, which implies “act on this content,” not “go somewhere else.” Primary nav or settings inside an action sheet fights that implication. After close, the object should remain selected so a second action on the same object does not require pointing again.

Studying it

For one object, offer an object-scoped sheet, a sheet mixed with global actions, and actions split across entries. The task is “do X to this one.” Record time to find the action, taps on global items, and whether the object is still remembered. Independent variables: whether every action takes that object, whether the object’s name is in the sheet title. Dependent variables: wrong scope, time. Naming the object in the title should drop scope errors.

Where it stops holding

A page with no current object (empty state, a desktop) should not raise an action sheet; it should raise create or a global menu. Bulk actions on several selected objects are a different sheet; the title must switch to a plural scope and must not reuse the singular object’s panel. Desktop usually puts object actions in a context menu or a toolbar; a bottom sheet is a touch spatial solution. Raising a narrow sheet at the bottom of a wide display leaves the thumb’s hotspot and does not read as a menu.

Applying it

• Put the object’s name or type in the sheet title. Every row should be speakable with that name as its object.
• Keep account, settings, and primary nav out of this sheet.
• After close, keep the object selected so a second action is cheap.
• How to check: cover the content and look only at the sheet. Can you say who these actions will affect? If not, scope was not established.

Related

• Within the group: E4.15.2 When actions overflow one screen, scrolling weakens how scannable the sheet is · E4.15.3 Destructive actions must be visually separated from ordinary ones
• Adjacent: E4.05 Inline and bulk actions · E5.13 Context menus
• Search terms: action sheet · object actions · bottom sheet