Adding hardware keyboard support to your app

At a glance

Project structure

Source bundle/
├── ProIllustratorSample/
│   ├── Model.swift
│   ├── AppDelegate.swift
│   ├── Canvas/
│   │   ├── AddShapeViewController.swift
│   │   ├── CanvasViewController.swift
│   │   ├── ShapeSelectionView.swift
│   │   └── ShapeView.swift
│   ├── FileListViewController.swift
│   ├── MainViewController.swift
│   ├── SceneDelegate.swift
│   └── GlobalKeyboardShortcutRespondable.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── ProIllustratorSample.xcodeproj/
    └── .xcodesamplecode.plist

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 17 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["AddShapeViewController"]
    N3["FileStore"]
    N4["UIKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

ProIllustratorSample/AppDelegate.swift:10 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        // Override point for customization after application launch.
        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
    Shape *-- CGRect : rect
    Shape o-- Style : style
    Shape o-- UIColor : color
    IllustrationFile *-- String : name

Ownership evidence

ProIllustratorSample/Model.swift:16 — stored dependency or nearest verified ownership anchor

class Shape {
    // ...
    var rect: CGRect
    // ...
}

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

ProIllustratorSample/Canvas/AddShapeViewController.swift:10 — representative type boundary

protocol AddShapeViewControllerDelegate: AnyObject {
    func addShapeViewController(_: AddShapeViewController, didSelectShapeStyle style: Shape.Style)
}

The source explicitly defines local protocol relationships: CanvasViewController → AddShapeViewControllerDelegate, MainViewController → FileListViewControllerDelegate, CanvasViewController → GlobalKeyboardShortcutRespondable, FileListViewController → GlobalKeyboardShortcutRespondable.

Access control

Reference code

ProIllustratorSample/Canvas/AddShapeViewController.swift:17 — representative boundary

class AddShapeViewController: UITableViewController {
    // ...
    public weak var delegate: AddShapeViewControllerDelegate?
    // ...
}

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: AddShapeViewController, CanvasViewController, FileListViewController, MainViewController; Delegate: AddShapeViewControllerDelegate, AppDelegate, FileListViewControllerDelegate, SceneDelegate; Store: FileStore; View: SelectionGrabberView, ShapeSelectionView, ShapeView.
• Protocols: AddShapeViewControllerDelegate, FileListViewControllerDelegate, GlobalKeyboardShortcutRespondable.
• Methods: untitledNameForIdentifier, itemForIdentifier, allIdentifiers, createNewFile, deleteItemWithIdentifier, application, buildMenu, addShapeViewController.
• Files: ProIllustratorSample/AppDelegate.swift, ProIllustratorSample/Canvas/AddShapeViewController.swift, ProIllustratorSample/Canvas/CanvasViewController.swift, ProIllustratorSample/Canvas/ShapeSelectionView.swift, ProIllustratorSample/FileListViewController.swift, ProIllustratorSample/Canvas/ShapeView.swift.

Architecture takeaways

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