In versions of watchOS before watchOS 7, people could press firmly on the display to open a hidden menu of actions relevant to the current screen. In watchOS 7 and later, watchOS apps elevate important items out of such menus and into the relevant screen or a settings screen.

Screenshot of a view menu within a gray watch frame. The menu consists of two items stacked vertically. The top item, titled Grid View, is represented by seven dots arranged in circle on top of a light-colored disk. The bottom item shows a three-item bulleted list on top of a light-colored disk and is titled List View.

To begin the task of removing hidden menus from your app, examine each item to determine whether it provides information or performs an action. Handle an informational item by integrating the content into your interface in a way that harmonizes with your design and lets people absorb it quickly. For actionable items, explore the following alternatives.

Consider putting a toolbar button beneath the navigation bar. Even though a toolbar button isn't visible when the screen first opens, people discover it easily as soon as they scroll up. For example, Mail relocates the New Message button from a hidden menu to a position above the list of messages in an inbox. The New Message button is out of the way until people scroll up to refresh the message list. For guidance, see Toolbar Buttons.

Consider integrating actions into a list. It can work well to add actions to an existing list, because people already know to scroll the list when they want to view all its content. For example, Activity relocates the Weekly Summary and Change Goals actions from a hidden menu to the end of the list on the main screen. For guidance, see Lists and Tables.

Consider adding a list header to display list-management actions. If you present a list that people can sort or filter, it can work well to offer buttons for these actions in a header that scrolls with the list items.

Consider using a More button to offer relevant actions in a modal sheet. People are accustomed to tapping a More button to find related actions. (A More button uses an ellipsis symbol, which looks like three dots on one horizontal line.) For example, Camera replaces a hidden menu with a More button that people can tap to manage the timer, front/rear camera, flash, Live Photo, and HDR options in a modal sheet. For guidance, see Buttons.

If you must continue to use hidden menus, follow these guidelines.

Combine a label with a glyph to convey the purpose of each menu action. Both the label and the glyph are required. Labels are limited to two lines, so make sure the text is concise.

Use menus for contextual or secondary actions. Menus give people access to actions that modify the contents of the current screen.

Avoid using menus for key actions or app navigation. Always provide primary actions and navigation in the main interface; use menus only to modify or adjust the current screen.

Avoid replicating the visual style of menus in other parts of your app. If you must use a similar layout, apply color to your interface or arrange items in a way that differentiates them from menus.