# Pull-down buttons

Source: https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons
Skill: hig-components-menus
Snapshot: 2025-02-02

---
<!-- hig-doctor:attribution -->
> **Source**: Apple Inc. Canonical content at https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons.
> This file is a structured index of that content, snapshot 2025-02-02.
> Apple HIG text and imagery are © Apple Inc.; this repository provides organization and cross-referencing for AI agent consumption only.

# Pull-down buttons

## Best practices

**Use a pull-down button to present commands or items that are directly related to the button’s action.**

  * An Add button could present a menu that lets people specify the item they want to add.

  * A Sort button could use a menu to let people select an attribute on which to sort.

  * A Back button could let people choose a specific location to revisit instead of opening the previous one.

**Avoid putting all of a view’s actions in one pull-down button.**

**Balance menu length with ease of use.**

**Display a succinct menu title only if it adds meaning.**

**Let people know when a pull-down button’s menu item is destructive, and ask them to confirm their intent.**

**Include an interface icon with a menu item when it provides value.**

## Platform considerations

### iOS, iPadOS

**Consider using a More pull-down button to present items that don’t need prominent positions in the main interface.**

---

<!-- hig-doctor:canonical-footer -->
For the complete guidance, including worked examples and illustrations, see the canonical page: https://developer.apple.com/design/human-interface-guidelines/pull-down-buttons