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.

Why is Native iOS Development the Best Choice for Complex Apps

The app crashes on cold start — EXC_BAD_ACCESS at the moment of initializing a singleton that accesses another singleton that hasn't been initialized yet. Or: a ViewController leaks memory because a closure captures self without [weak self], and that ViewController hangs in memory two transitions after the user left it. These are not hypothetical scenarios — they are the two most common classes of problems on iOS projects that come to us after another team.

We have been doing iOS development for over 5 years, delivered 40+ projects of varying complexity — from startups to enterprise solutions with millions of users. Each project undergoes 3 stages of Code Review, a custom set of UI tests (150+ test cases on average), and a mandatory run through Xcode Instruments before release.

Native iOS development with Swift means direct access to the platform. No middleware, no performance compromises, full control over what happens on every frame.

What Makes Native iOS Development on Swift the Choice for Enterprise Apps?

Native code guarantees compatibility with new Apple APIs on the day they are released, not after months of adaptation in cross-platform frameworks. For apps with latency-sensitive logic (financial terminals, medical monitors, AR navigation), this is critical. Swift with ARC and strict typing allows maintaining a crash-free rate of 99.9% with proper architecture.

SwiftUI or UIKit: What to Choose for Native iOS Development

By now, SwiftUI covers the vast majority of production tasks. But UIKit is not deprecated and will not disappear — Apple does not deprecate it but continues to add APIs. The real picture on large projects: a hybrid approach. SwiftUI for most screens, UIKit where SwiftUI hits limitations.

Which Scenarios Does SwiftUI Win Unconditionally

SwiftUI's declarative syntax reduces UI code by 3-5 times compared to UIKit. A settings screen with List, Toggle, Picker — that's 40 lines of SwiftUI versus 200 lines of UIKit with UITableViewDataSource delegates. Time savings on UI development reach 60%. Apple recommends starting new projects on SwiftUI (Human Interface Guidelines).

@State, @Binding, @ObservableObject (and with iOS 17, the @Observable macro) create a reactive link between data and UI without manual reloadData(). Changing a @State variable automatically redraws the affected part of the hierarchy. This works correctly if you understand how SwiftUI computes the diff — via Equatable and id in ForEach.

AsyncImage, NavigationStack with type-safe routing via NavigationPath, searchable, refreshable — these are ready-made patterns that UIKit requires implementing manually.

When UIKit Remains Necessary

UICollectionView with compositional layout and diffable data source — complex grids with different cell types, horizontal sections inside vertical scroll, dynamic cell sizes. SwiftUI LazyVGrid / LazyHGrid do not provide such control.

Custom transitions between screens. UIViewControllerAnimatedTransitioning and UIViewControllerInteractiveTransitioning — interactive pop gesture with partial progress, custom hero transition with precise frame control. SwiftUI matchedGeometryEffect covers some cases, but not all.

UITextView with TextKit 2. Rich text editor, custom attributes, custom rendering — TextKit 2 (available since iOS 16) switched to async layout, solving performance issues on long documents. SwiftUI TextEditor is a wrapper around UITextView without direct access to TextKit.

UIScrollView with custom behavior. scrollViewDidScroll, parallax effects, sticky headers with custom logic, pull-to-refresh with custom indicator. SwiftUI ScrollView with scrollPosition and onScrollGeometryChange (iOS 17) covers some cases, but not all.

How Do We Integrate SwiftUI and UIKit Step by Step

1. Identify screens where SwiftUI gives maximum gain (lists, forms, settings) — usually 70-80% of screens.
2. For performance-critical areas (complex collections, custom animations) leave UIKit.
3. Use UIHostingController to embed SwiftUI views into UIKit navigation stack.
4. For backward compatibility, wrap UIKit components via UIViewRepresentable.
5. Coordinator pattern (UIKit) manages navigation at the flow level, screens are implemented in SwiftUI.

One pattern we use on projects: UIKit coordinator manages navigation, while the screens themselves are in SwiftUI. The coordinator creates a UIHostingController, passes ViewModel via initializer or @EnvironmentObject, and manages transitions. This gives clean separation: SwiftUI handles UI, Coordinator handles navigation.

How async/await and Combine Work Together

Before Swift 5.5, asynchronous code on iOS was built on Combine or callback chains. With the advent of async/await and Actor, concurrency has become part of the language. On new projects we use async/await as the primary tool for network calls and business logic, and Combine for reactive UI state binding.

// Correct — @MainActor guarantees UI updates on main thread
@MainActor
class UserViewModel: ObservableObject {
    @Published var user: User?
    @Published var isLoading = false

    func loadUser(id: String) async {
        isLoading = true
        defer { isLoading = false }
        do {
            user = try await userService.fetch(id: id)
        } catch {
            // handle error
        }
    }
}

Combine remains indispensable for debouncing input, merging multiple Publishers (CombineLatest, Zip), and functional processing of value streams (map, flatMap, filter). In practice, 80% of projects use both approaches, choosing the tool for the task.

iOS App Architecture

MVVM — the basic pattern. ViewModel contains logic and @Published state, SwiftUI View subscribes via @ObservedObject or @StateObject. One rule: View knows nothing about URLSession, CoreData, UserDefaults.

Clean Architecture adds Repository and UseCase layers. UserRepository abstracts the data source (network vs cache). FetchUserUseCase contains business logic. UserViewModel calls UseCase and manages UI state.

TCA (The Composable Architecture) — a stricter pattern from Point-Free. State, Action, Reducer, Effect — everything explicit, testable, composable via Scope. Works well in large teams (5+ iOS developers) where predictability is important.

What's Included in iOS App Development

Tools Without Which No Release Is Complete

Xcode Instruments. Time Profiler shows where CPU spends time. Allocations — memory leaks and excessive allocations. Leaks — objects that are not freed. Before every release — a mandatory run.

Firebase Crashlytics. Crash-free rate, grouping by stack trace, breadcrumbs of events leading to crash. Set up in 30 minutes, provides visibility across the entire device fleet. On our projects, average crash-free rate is 99.8%.

Fastlane match. Manage certificates and provisioning profiles via an encrypted git repository. Eliminates the 'it builds locally but not on CI' issue once and for all. Saves up to 4 hours per build when signing manually.

XCTest + XCUITest. Unit tests for ViewModel and UseCase, UI tests for critical flows (onboarding, payment, authorization). On average, code coverage is 75%.

Process and Timelines

Cost is calculated individually after analyzing the technical specification and design. Typically, the first 2 weeks are spent on design, after which we finalize the timeline and budget.

Order turnkey development — we will evaluate your project in 2 business days and propose the optimal architecture. Contact us to discuss your task: we guarantee code quality, compliance with App Store Review Guidelines, and experience with projects of any scale. Get a consultation — we will help you choose the right stack and avoid common mistakes at the start.