Supporting Game Controllers

At a glance

Project structure

Source bundle/
└── Swift/
    ├── Shared/
    │   ├── GameController.swift
    │   ├── ChaserComponent.swift
    │   ├── HapticUtility.swift
    │   ├── ScaredComponent.swift
    │   ├── BaseComponent.swift
    │   └── PlayerComponent.swift
    ├── iOS/
    │   ├── AppDelegate.swift
    │   └── GameViewController.swift
    ├── macOS/
    │   ├── AppDelegate.swift
    │   └── GameViewController.swift
    └── tvOS/
        ├── AppDelegate.swift
        └── GameViewController.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 10 project/configuration file(s) and 30 source declaration(s).

Overall architecture

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

Reference code

Swift/iOS/AppDelegate.swift:10 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    var window: UIWindow?
}

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 Game Controller.

Ownership and state

classDiagram
    Bitmask *-- Int : rawValue
    Bitmask *-- Bitmask : character
    Bitmask *-- Bitmask : collision
    Bitmask *-- Bitmask : enemy

Ownership evidence

Swift/Shared/GameController.swift:17 — stored dependency or nearest verified ownership anchor

struct Bitmask: OptionSet {
    let rawValue: Int
    // ...
}

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.

@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.

Reference code

Swift/Shared/Character.swift:332 — representative execution boundary

class Character: NSObject {
    // ...
    var lightQueue = DispatchQueue(label: "lavaLightFlash", qos: .default)
    // ...
}

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

Swift/Shared/UI/Menu.swift:10 — representative type boundary

protocol MenuDelegate: NSObjectProtocol {

    func fStopChanged(_ value: CGFloat)
    func focusDistanceChanged(_ value: CGFloat)
    func debugMenuSelectCameraAtIndex(_ index: Int)
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

Swift/Shared/BaseComponent.swift:14 — representative boundary

class BaseComponent: GKComponent {
    // ...
    public static let EnemyAltitude: Float = -0.46
    // ...
}

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: Component: BaseComponent, ChaserComponent, PlayerComponent, ScaredComponent; Controller: GameController; Delegate: AppDelegate, ButtonOverlayDelegate, MenuDelegate, PadOverlayDelegate.
• Protocols: MenuDelegate, ButtonOverlayDelegate, PadOverlayDelegate.
• Methods: setupGameController, setupCharacter, setupPhysics, setupCollisions, setupFollowCamera, setupAxisAlignedCamera, setupCameraNode, setupCamera.
• Files: Swift/Shared/GameController.swift, Swift/iOS/AppDelegate.swift, Swift/macOS/AppDelegate.swift, Swift/tvOS/AppDelegate.swift, Swift/Shared/ChaserComponent.swift, Swift/Shared/HapticUtility.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches SceneKit, SpriteKit, GameController, GameplayKit 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.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation