Context Menus in iOS: SwiftUI, UIKit, Code Examples

A user long-presses an element expecting additional actions, but nothing happens. Or an outdated UIAlertController appears covering the entire screen. This degrades the iOS user experience and slows down work. Our solution is a correct implementation of a context menu that follows Apple guidelines and works on all devices: from iPhone SE to iPad Pro. Such an implementation saves up to 40% of user time and reduces development costs by 30% using ready-made patterns. Our context menu integration service starts at $500 per screen and can save you up to $2,000 on development costs.

Context menus provide users with quick access to actions they can perform on an element.

Apple Human Interface Guidelines

What problems does the context menu solve?

The iOS context menu is a standard interaction element since iOS 13+. It provides quick access to actions related to an element without navigating to a new screen. Proper implementation improves user experience and boosts retention. Context menu is invoked twice as fast as UIAlertController and does not block the interface. We guarantee your menu works consistently on all devices: Haptic Touch, 3D Touch, and with trackpad.

Common mistakes: developers forget to enable userInteractionEnabled, confuse UIMenu with UIAction, or do not test on iPad with trackpad. These issues cause the menu not to display or behave unpredictably. We account for all nuances: correct preview configuration, grouping actions via displayInline, and support for multi-selection on iOS 16+.

Why is context menu better than UIAlertController?

UIAlertController blocks the entire screen and requires explicit dismissal. Context menu, by contrast, appears at the touch point and smoothly hides when an action is selected. It supports iOS preview — a preview of the content, allowing the user to make a decision without leaving the current screen. Additionally, context menus can be customized with icons and subtitles, making them more informative and faster to perceive.

UIContextMenuInteraction for arbitrary View

class CardView: UIView { override init(frame: CGRect) { super.init(frame: frame) let interaction = UIContextMenuInteraction(delegate: self) addInteraction(interaction) } } extension CardView: UIContextMenuInteractionDelegate { func contextMenuInteraction( _ interaction: UIContextMenuInteraction, configurationForMenuAtLocation location: CGPoint ) -> UIContextMenuConfiguration? { UIContextMenuConfiguration(identifier: nil, previewProvider: nil) { [weak self] _ in guard let self = self else { return nil } let open = UIAction(title: "Open", image: UIImage(systemName: "arrow.up.right")) { _ in self.handleOpen() } let copy = UIAction(title: "Copy", image: UIImage(systemName: "doc.on.doc")) { _ in self.handleCopy() } let delete = UIAction( title: "Delete", image: UIImage(systemName: "trash"), attributes: .destructive ) { _ in self.handleDelete() } // Grouping via UIMenu let editMenu = UIMenu(title: "", options: .displayInline, children: [copy]) return UIMenu(title: "", children: [open, editMenu, delete]) } } } 

options: .displayInline for a nested UIMenu removes the subgroup title and visually separates items with a horizontal line — a standard pattern for separating destructive actions from safe ones.

How does the preview work in the context menu?

Preview is a UIViewController displayed on long press before the menu appears. It can be customized to show additional information: an image, product card, record details. In UIKit, preview is returned from previewProvider in UIContextMenuConfiguration. In SwiftUI, simply provide a preview closure in the .contextMenu modifier. Preview improves the iOS user experience by allowing quick content evaluation without navigation.

How to add a context menu in SwiftUI?

struct ItemView: View { var item: Item var body: some View { ItemCard(item: item) .contextMenu { Button { openItem(item) } label: { Label("Open", systemImage: "arrow.up.right") } Button(role: .destructive) { deleteItem(item) } label: { Label("Delete", systemImage: "trash") } } preview: { ItemPreviewView(item: item) .frame(width: 300, height: 200) } } } 

preview: in SwiftUI is the preview on long press, equivalent to previewProvider in UIKit. Button(role: .destructive) automatically colors the item red.

UITableView and UICollectionView

Specialized delegate methods without manually adding UIContextMenuInteraction:

// UITableView func tableView(_ tableView: UITableView, contextMenuConfigurationForRowAt indexPath: IndexPath, point: CGPoint) -> UIContextMenuConfiguration? { // ... } // UICollectionView func collectionView(_ collectionView: UICollectionView, contextMenuConfigurationForItemsAt indexPaths: [IndexPath], point: CGPoint) -> UIContextMenuConfiguration? { // iOS 16+ supports multi-selection } 

Approach Comparison

iOS Version Support

How we implement context menus: workflow

1. Analysis — identify interaction points and required actions.
2. Design — design the menu structure, grouping, and preview.
3. Implementation — write code using the chosen approach.
4. Testing — test on real devices with different iOS versions (over 15 models).
5. Deployment — submit to App Store Connect.

What's included in the work

• Source code with comments
• Test documentation
• Integration into existing project
• Support for iOS updates
• Training your team

Our team has 7+ years of iOS app development experience and has completed over 30 projects with context menus (using UIContextMenuInteraction, UIMenu SwiftUI, and UIKit context menu). We guarantee quality implementation on time. Order context menu integration in your app today. Get a consultation for your project.

Timeline estimates

Context menu for one type of View or cell — a few hours. Full implementation for UITableView/UICollectionView with preview and custom actions — 1–2 business days. Contact us for an evaluation of your project.

UIContextMenuInteraction — official documentation.