#TURN OFF STATUS BAR IOS SOFTWARE#
Software issues (iOS & iPadOS issues) are permitted.Īll posts must foster reasonable discussion, posts shouldn't just be "Wow x feature is so cool" or "I hate x feature" Posts should have actual content, and shouldn't be rants or "circlejerking" posts. No hardware support issues, instead go to r/applehelp or r/iphonehelp. We don't allow spam or irrelevant self-promotion without authorization from the moderators. For all discussions about Apple, iPhone, iPad, Apple Watch, or any other off-topic discussions, please move the discussion to the relevant subreddits. Posts must be discussions about iOS or iOS beta only. No posting of app release notes (funny or otherwise) except for updates to iOS. No blogspam or news with minimal/recycled content.ĭo not submit photos of codes, or just the codes (from places like Starbucks) themselves. Don't post links to your own YouTube videos or blog posts. You shouldn't be gaining anything from links posted.
No Amazon affiliate links or self-promotion (unless it's the official reddit one). No posts highlighting throttling issues, speedtest results, bragging about battery life.Īnd hilarious Siri answers. People can tap to open the item they’re previewing, so there’s typically no need to provide an explicit Open button.įor developer guidance, see UIContextMenuInteraction.Join Our iOS Discord! Tech Support FAQ Rules For additional guidance, see Edit Menus.Īvoid providing an action button that opens the item preview. It can be confusing to people and hard for the system to detect intent when both features are enabled for the same item. Typically, you don’t want more than three groups in a context menu.Īvoid providing a context menu and an edit menu for the same item. For example, you might use a separator to group actions related to editing the item and another to group actions related to sharing the item. Creating visual groupings can help people scan a menu more quickly. Use separators to group related menu items. Placing the most common items at the top of the menu helps people find the item they’re looking for. When people open a context menu, their focus is on the top area of that menu. Place the most frequently used items at the top of the menu. Although submenus can shorten a context menu and clarify the commands that people can perform, more than one level of submenu complicates the experience and can be difficult for people to navigate. Concise, action-oriented titles also let people skip over submenus they don’t need in their current context. Give submenus intuitive titles that describe their contents so people can predict the submenu's commands without revealing them. A submenu is a context menu item that reveals a secondary menu of logically related commands. If your context menu includes a submenu, you don't need a glyph for it because it automatically displays a system-provided chevron symbol that indicates the presence of additional commands. When you use SF Symbols, you can choose an existing symbol that represents your command or edit a related symbol to create a custom glyph. A glyph reinforces the meaning of a command, helping people instantly understand its function.
Include a glyph with each command in a context menu.
Listing too many commands can overwhelm people. For example, in the context menu for a Mail message, it makes sense to include commands for replying and moving the message, but it doesn’t make sense to include formatting or mailbox commands. Include only the most commonly used commands that apply to the item. If you provide context menus for items in some places but not in others, people won’t know where they can use the feature and may think there’s a problem with your app. People can choose a command or drag the item to another area, window, or app.Īdopt context menus consistently. When open, a context menu displays a preview of the item and lists the commands that act on it. To reveal a context menu, people can use the system-defined touch and hold gesture or 3D Touch (3D Touch can make context menus appear more quickly).