Adding context menus in your app

At a glance

Project structure

Source bundle/
└── ContextMenus/
    ├── AppDelegate.swift
    ├── BaseCollectionViewTestViewController.swift
    ├── BaseTableTestViewController.swift
    ├── CollectionViewPreviewProvider.swift
    ├── ControlPreviewProvider.swift
    ├── ControlPreviewViewController.swift
    ├── DetailViewManager.swift
    ├── InitialDetailViewController.swift
    ├── Model.swift
    ├── PreviewViewController.swift
    ├── SceneDelegate.swift
    └── TableViewPreviewProvider.swift

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 6 project/configuration file(s) and 41 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["BaseCollectionViewTestViewController"]
    N3["DetailViewManager"]
    N4["CollectionViewPreviewProvider"]
    N5["UIKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

ContextMenus/AppDelegate.swift:10 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate, UISplitViewControllerDelegate {

    func application(_ application: UIApplication,
                     didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        return true
    }

}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into UIKit.

Ownership and state

classDiagram
    BaseCollectionViewTestViewController *-- UIEdgeInsets : sectionInsets
    BaseCollectionViewTestViewController o-- UICollectionViewDiffableDataSource : dataSource
    BaseTableViewTestViewController o-- UITableViewDiffableDataSource : dataSource
    ControlPreviewProvider o-- UIButton : buttonMenu

Ownership evidence

ContextMenus/BaseCollectionViewTestViewController.swift:12 — stored dependency or nearest verified ownership anchor

class BaseCollectionViewTestViewController: UICollectionViewController {
    // ...
    private let sectionInsets = UIEdgeInsets(top: 6.0, left: 6.0, bottom: 6.0, right: 6.0)
    // ...
}

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Concurrency, scheduling, and thread safety

Evidence limit: actor isolation, async/await, or Task creation does not by itself prove background-thread execution; Sendable conformance alone does not prove thread-safe mutation.

No source-visible execution, scheduling, or synchronization boundary was found in the indexed source.

@MainActor/MainActor.run, DispatchQueue.main, and RunLoop.main are reported as distinct isolation, queue, and event-loop mechanisms. A plain Task is kept separate from Task.detached; neither is labeled as a background thread.

State propagation, frameworks, and dependencies

Evidence limit: an import proves a source-level compilation dependency at the cited line; it does not prove runtime use, architectural adoption, or whether a Swift package is a direct application dependency.

receive(on:) describes downstream delivery scheduling, while subscribe(on:) describes upstream subscription/request/cancel scheduling. An import Combine alone establishes neither behavior nor a Store, reducer, Redux, or other application architecture.

Class and protocol design

ContextMenus/ContextMenu.swift:10 — representative type boundary

protocol ContextMenu {

    // Adopters of this protocol implement the actual actions.
    func performInspect()
    func performDuplicate()
    func performDelete()
}

The source explicitly defines local protocol relationships: CollectionViewBasic → IndexPathContextMenu, CollectionViewPreview → IndexPathContextMenu, CollectionViewPreviewProvider → IndexPathContextMenu, CollectionViewSubmenu → IndexPathContextMenu, CollectionViewTitled → IndexPathContextMenu, ControlBasic → ContextMenu.

Access control

Reference code

ContextMenus/BaseCollectionViewTestViewController.swift:12 — representative boundary

class BaseCollectionViewTestViewController: UICollectionViewController {
    // ...
    private let sectionInsets = UIEdgeInsets(top: 6.0, left: 6.0, bottom: 6.0, right: 6.0)
    // ...
}

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: Controller: BaseCollectionViewTestViewController, BaseTableViewTestViewController, ControlPreviewViewController, InitialDetailViewController, PreviewViewController; Delegate: AppDelegate, SceneDelegate; Manager: DetailViewManager; Model: Model; Provider: CollectionViewPreviewProvider, ControlPreviewProvider, TableViewPreviewProvider, ViewPreviewProvider, WebViewPreviewProvider.
• Protocols: ContextMenu, IndexPathContextMenu, WebViewContextMenu.
• Methods: application, viewDidLoad, itemSize, collectionView, performInspect, performDuplicate, performDelete, buttonAction.
• Files: ContextMenus/AppDelegate.swift, ContextMenus/BaseCollectionViewTestViewController.swift, ContextMenus/CollectionViewPreviewProvider.swift, ContextMenus/ControlPreviewProvider.swift, ContextMenus/ControlPreviewViewController.swift, ContextMenus/DetailViewManager.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches UIKit, SafariServices, WebKit through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• Local protocol relationships provide an explicit substitution boundary.

Source map

• Official Apple documentation