Context Menus on iOS: Force Touch, Haptic Touch, and UIContextMenuInteraction

When developing an iOS app, you often encounter a situation: the user long-presses an element, but the menu doesn't appear. Why? Because the code still uses UIViewControllerPreviewing — the deprecated 3D Touch API that doesn't work on devices without Force Touch. Since iOS 13, Apple unified the mechanism: one UIContextMenuInteraction replaces both approaches. We use it in all new projects — it guarantees consistent behavior on iPhone SE, iPad, and iPhone 15 Pro. This approach reduces maintenance costs by 30% compared to having two separate implementations.

Apple Developer Documentation: UIContextMenuInteraction

Why Replace UIViewControllerPreviewing?

Using the deprecated API means that on devices without Force Touch (iPhone XR, SE, 11 and newer), the menu won't appear. This directly loses functionality for 80% of users. UIContextMenuInteraction works identically on all devices with iOS 13, simplifying the code by half.

How UIContextMenuInteraction Works

This class is the only correct way to create a context menu. It automatically adapts to the press type: on older iPhones — Force Touch, on newer ones — Haptic Touch. On iPad with trackpad, the menu opens via right-click. All gesture handling is internal. You only need to define the configuration.

let interaction = UIContextMenuInteraction(delegate: self)
myView.addInteraction(interaction)

func contextMenuInteraction(
    _ interaction: UIContextMenuInteraction,
    configurationForMenuAtLocation location: CGPoint
) -> UIContextMenuConfiguration? {
    return UIContextMenuConfiguration(identifier: nil, previewProvider: nil) { _ in
        let share = UIAction(title: "Поделиться", image: UIImage(systemName: "square.and.arrow.up")) { _ in
            self.shareItem()
        }
        let delete = UIAction(title: "Удалить", image: UIImage(systemName: "trash"),
                              attributes: .destructive) { _ in
            self.deleteItem()
        }
        return UIMenu(title: "", children: [share, delete])
    }
}

For UITableView: Even Simpler

UITableView has built-in support through delegate methods. The implementation is 40% shorter than using UIContextMenuInteraction directly.

func tableView(_ tableView: UITableView,
               contextMenuConfigurationForRowAt indexPath: IndexPath,
               point: CGPoint) -> UIContextMenuConfiguration? {
    let item = items[indexPath.row]
    return UIContextMenuConfiguration(identifier: indexPath as NSIndexPath) { [weak self] in
        ItemPreviewViewController(item: item)
    } actionProvider: { _ in
        UIMenu(title: "", children: [
            UIAction(title: "Открыть") { _ in self?.openItem(item) },
            UIAction(title: "Удалить", attributes: .destructive) { _ in self?.deleteItem(item) }
        ])
    }
}

Single implementation works with Force Touch, Haptic Touch, and iPad trackpad.

Comparison of Approaches

Clearly, UIContextMenuInteraction or the table delegate methods are the only modern choice. We strongly recommend not using the old API to avoid App Store moderation issues — App Store Review Guidelines Section 4.2 requires correct functionality on all supported devices.

Our Implementation Process

We take a systematic approach: analyze where users might need a quick action, design the menu, implement, and test on simulators and real devices.

1. Analysis — Identify elements that need a context menu (list cells, images, links).
2. Design — Compile a list of actions: frequently used at top, destructive at bottom (with .destructive attribute).
3. Implementation — Write code using UIContextMenuInteraction or delegate methods. Add custom preview if detail information is needed.
4. Testing — Check on simulator (long press emulates Haptic Touch) and on devices with Haptic Touch and Force Touch. Special attention to child menus and nested actions.
5. Deployment — Sign, upload to App Store Connect, use TestFlight for beta testing.

What's Included in Our Work

• Turnkey context menu implementation: from prototype to App Store publication.
• Integration with Firebase Analytics to track selected actions.
• Support for Universal Links / App Links to open the menu externally.
• Documentation on implementation and testing.
• Training of your team on working with UIContextMenuInteraction.
• Guarantee of compatibility with current and next iOS versions.

Estimated Timeline

Implementing a context menu via UIContextMenuInteraction or delegate methods in UITableView/UICollectionView — within one working day, including testing on devices with Force Touch and Haptic Touch. If custom preview or analytics integration is required, the timeline extends to two days.

Common Mistakes and How to Avoid Them

• Forgetting to add UIContextMenuInteraction to the view before calling addInteraction — menu won't appear.
• Using UIViewControllerPreviewing in a new project — on iPhone XR and newer, the menu won't work.
• Not handling attributes: .destructive — deletion won't be highlighted in red.
• Trying to customize the standard UIMenu (change color, font) — this is prohibited; Apple doesn't provide such capabilities.

Our experience helps avoid these pitfalls — we've already been through this path and know all the pitfalls.

Contact us for a consultation. Get an assessment of your project and a detailed commercial proposal.

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.