Menus & Actions
On the Menus & Actions page, we designed navigation and controls to be instantly recognizable and usable. Research shows that “people rely on menus to find content and use features”, so we made sure all main menus are visible and placed where users expect them.
Insights
For menus and actions, I made discoverability and clarity the top priorities. We treat menus (navigation drawers, context menus, popovers) as familiar UI patterns and use them consistently, echoing Apple’s observation that menus are “ubiquitous throughout the interface” and, when used consistently, make the experience feel “familiar and easy to learn”. Guided by this, each menu in APPEX NOW follows the same structure. A clear header (if needed), a list of action items, and an optional footer (e.g. a cancel or settings entry). Every menu item has a concise label. We use verbs or verb phrases for commands (like “Copy”, “Delete”, “Share”). We avoid vague labels like “Click here” or overly cute phrasing, instead we prioritize straight forward wording that conveys exactly what happens when the item is selected.
To ensure accessibility, icons in menus are paired with text labels and optional keyboard shortcuts are shown when relevant. We also group and order items by importance and frequency of use (for instance, putting “Save” before “Duplicate”), so users find common actions where they expect them. These decisions collectively create menus that feel intuitive. Users immediately grasp the available actions and the predictable organization helps them navigate our app efficiently.
Best Practices
Simple & Flat Structure:
Keep menu structure simple and flat, avoid deep nesting where possible. Use submenus only when necessary.
Label Clearly:
Use a verb+object format for actions (e.g. “Open File”, “Logout”) and eliminate filler words. Apple’s HIG suggests a condensed, article-free style (e.g. use “Open Message” not “Open the Message”).
Include Icons:
Include icons sparingly for quick recognition, but always accompany them with text (icons alone may be misunderstood).
Ensure Consistent Placement:
Main menus (like a sidebar or hamburger menu) always appear in the same location, and context menus open near the triggering element. This leverages the “consistent navigation” principle to reduce cognitive load.
Keyboard & Accessibility Cues:
Ensure menus are reachable by keyboard (arrow keys to navigate), and screen readers announce menu items by their text labels.
Visual Indicators:
Highlight the currently focused or selected item with a visual indicator (background or checkmark) so users can see context (as Apple notes, a checkmark can denote an active state.
Actionable Items:
Confirm actionable items are enabled/disabled appropriately and clearly. For example, dim or disable irrelevant actions so users aren’t confused.
