Adding menus and shortcuts to the menu bar and user interface

At a glance

Project structure

Source bundle/
├── Menus/
│   ├── MenuController.swift
│   ├── AppDelegate.swift
│   ├── DetailViewController.swift
│   ├── PrimaryViewController.swift
│   ├── SceneDelegate.swift
│   ├── TableItem.swift
│   ├── PrimaryViewController+Table.swift
│   ├── PrimaryViewController+Toolbar.swift
│   └── Base.lproj/
│       └── LaunchScreen.storyboard
├── Configuration/
│   └── SampleCode.xcconfig
└── Menus.xcodeproj/
    ├── .xcodesamplecode.plist
    └── project.pbxproj

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 7 project/configuration file(s) and 16 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["MenuController"]
    N3["UIKit APIs"]
    N1 --> N2
    N2 --> N3

Reference code

Menus/AppDelegate.swift:10 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {

        /** The registration domain is volatile.  It doesn't persist across launches.
            Register the defaults at each launch; otherwise the system's default values are obtained when accessing
            the values of preferences for the user (via the Settings app) or this app (via set*:forKey:).
            Registering a set of default values ensures that this app always has a known good set of values to operate on.
        */
        registerDefaultsFromSettingsBundle()

        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
    AppDelegate o-- MenuController : menuController
    AppDelegate o-- Fontmenustylestates : fontMenuStyleStates
    DetailViewController o-- UILabel : detailDescriptionLabel
    DetailViewController o-- UIView : detailDescriptionView

Ownership evidence

Menus/AppDelegate.swift:27 — stored dependency or nearest verified ownership anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
    var menuController: MenuController!
    // ...
}

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

Menus/DetailViewController.swift:20 — representative type boundary

protocol DetailItemDelegate: NSObjectProtocol {
    func performCutAction()
    func performCopyAction()
    func performPasteAction()
    func performDeleteAction()
    func didUpdateItem(_ item: AnyModelItem)
}

The source explicitly defines local protocol relationships: PrimaryViewController → DetailItemDelegate.

Access control

Reference code

Menus/PrimaryViewController.swift:187 — representative boundary

    private func selectRow(at indexPath: IndexPath) {
        // ...
            tableView.selectRow(at: indexPath, animated: false, scrollPosition: .bottom)
        // ...
    }

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: DetailViewController, MenuController, PrimaryViewController; Delegate: AppDelegate, DetailItemDelegate, SceneDelegate; View: ResponsiveView.
• Protocols: DetailItemDelegate.
• Methods: localizedString, openMenu, newMenu, citiesMenu, navigationMenu, fontStyleMenu, toolsMenu, addCopyCommand.
• Files: Menus/MenuController.swift, Menus/AppDelegate.swift, Menus/DetailViewController.swift, Menus/PrimaryViewController.swift, Menus/SceneDelegate.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches UIKit, SwiftUI 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