Playing Haptics on Game Controllers

At a glance

Project structure

Source bundle/
├── HapticControllers/
│   ├── App/
│   │   ├── AppDelegate.swift
│   │   └── SceneDelegate.swift
│   ├── HapticsManager.swift
│   ├── User Interface/
│   │   ├── MainViewController.swift
│   │   └── Base.lproj/
│   │       ├── LaunchScreen.storyboard
│   │       └── Main.storyboard
│   ├── Extensions/
│   │   └── UIViewExtensions.swift
│   └── Info.plist
├── Configuration/
│   └── SampleCode.xcconfig
└── HapticControllers.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 6 project/configuration file(s) and 5 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["MainViewController"]
    N3["HapticsManager"]
    N4["CoreHaptics APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

HapticControllers/App/AppDelegate.swift:10 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    func application(_ application: UIApplication,
                     configurationForConnecting connectingSceneSession: UISceneSession,
                     options: UIScene.ConnectionOptions) -> UISceneConfiguration {
        return UISceneConfiguration(name: "Default Configuration", sessionRole: connectingSceneSession.role)
    }
}

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 Core Haptics.

Ownership and state

classDiagram
    HapticsManager o-- GCController : controller
    SceneDelegate o-- UIWindow : window
    MainViewController o-- HapticsManager : manager
    MainViewController o-- UIButton : highlightedButton

Ownership evidence

HapticControllers/HapticsManager.swift:21 — stored dependency or nearest verified ownership anchor

class HapticsManager {
    // ...
    private var controller: GCController?
    // ...
}

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.

Class and protocol design

HapticControllers/HapticsManager.swift:12 — representative type boundary

protocol HapticsManagerDelegate: AnyObject {
    func didConnect(controller: GCController)
    func didDisconnectController()
}

The source explicitly defines local protocol relationships: MainViewController → HapticsManagerDelegate.

Access control

Reference code

HapticControllers/HapticsManager.swift:19 — representative boundary

    private var isSetup = false
    
    private var controller: GCController?
    // A haptic engine manages the connection to the haptic server.
    private var engineMap = [GCHapticsLocality: CHHapticEngine]()

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: MainViewController; Delegate: AppDelegate, HapticsManagerDelegate, SceneDelegate; Manager: HapticsManager.
• Protocols: HapticsManagerDelegate.
• Methods: application, didConnect, didDisconnectController, startObserving, controllerDidConnect, createEngine, controllerDidDisconnect, playHapticsFile.
• Files: HapticControllers/App/AppDelegate.swift, HapticControllers/HapticsManager.swift, HapticControllers/App/SceneDelegate.swift, HapticControllers/User Interface/MainViewController.swift.

Architecture takeaways

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