Setting up and authorizing a Bluetooth accessory

At a glance

Project structure

Source bundle/
├── ASKSample/
│   ├── ASKSample/
│   │   ├── ASKSampleApp.swift
│   │   ├── ContentView.swift
│   │   ├── DiceSessionManager.swift
│   │   └── Info.plist
│   ├── ASKSampleAccessory/
│   │   ├── ASKSampleAccessoryApp.swift
│   │   ├── SampleAccessoryView.swift
│   │   └── DiceAccessory.swift
│   ├── Shared/
│   │   ├── DiceColor.swift
│   │   └── DiceValue.swift
│   └── ASKSample.xcodeproj/
│       ├── .xcodesamplecode.plist
│       └── project.pbxproj
└── Configuration/
    └── SampleCode.xcconfig

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

Overall architecture

flowchart LR
    N1["ASKSampleApp"]
    N2["ContentView"]
    N3["DiceSessionManager"]
    N4["AccessorySetupKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

ASKSample/ASKSample/ASKSampleApp.swift:10 — architecture anchor

@main
struct ASKSampleApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

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

Ownership and state

classDiagram
    ContentView *-- DiceSessionManager : diceSessionManager
    DiceSessionManager o-- DiceColor : diceColor
    DiceSessionManager o-- ASAccessory : currentDice
    DiceSessionManager *-- ASAccessorySession : session

Ownership evidence

ASKSample/ASKSample/ContentView.swift:11 — stored dependency or nearest verified ownership anchor

    @State var diceSessionManager = DiceSessionManager()

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

ASKSample/ASKSample/ASKSampleApp.swift:11 — representative type boundary

struct ASKSampleApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

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

Access control

Reference code

ASKSample/ASKSample/ContentView.swift:27 — representative boundary

    private var makeSetupView: some View {
        // ...
    }

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: App: ASKSampleAccessoryApp, ASKSampleApp; Manager: DiceSessionManager; View: ContentView, SampleAccessoryView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: makeRollView, presentPicker, removeDice, connect, disconnect, saveDice, handleSessionEvent, centralManagerDidUpdateState.
• Files: ASKSample/ASKSample/ASKSampleApp.swift, ASKSample/ASKSampleAccessory/ASKSampleAccessoryApp.swift, ASKSample/ASKSample/ContentView.swift, ASKSample/ASKSample/DiceSessionManager.swift, ASKSample/ASKSampleAccessory/SampleAccessoryView.swift, ASKSample/ASKSampleAccessory/DiceAccessory.swift.

Architecture takeaways

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