Embedding controls in an immersive space

At a glance

Project structure

Source bundle/
├── SampleApp/
│   ├── SampleApp.swift
│   ├── AppModel.swift
│   ├── ScenePhaseMonitor.swift
│   ├── SphereModel.swift
│   ├── ContentView.swift
│   ├── ImmersiveView.swift
│   └── Control Views/
│       ├── ControlsAttachment.swift
│       ├── ControlsWindow.swift
│       ├── DebugMainSceneStates.swift
│       ├── ImmersiveControls.swift
│       └── OpenSpheresMenuButton.swift
└── Packages/
    └── RealityKitContent/
        └── Sources/
            └── RealityKitContent/
                └── RealityKitContent.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 4 project/configuration file(s) and 20 source declaration(s).

Overall architecture

flowchart LR
    N1["SampleApp"]
    N2["ContentView"]
    N3["AppModel"]
    N4["SwiftUI / RealityKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

SampleApp/SampleApp.swift:17 — architecture anchor

@main
struct SampleApp: App {
    @State private var appModel = AppModel()
    // ...
}

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

Ownership and state

classDiagram
    SampleApp *-- AppModel : appModel
    AppModel *-- Dictionary : mainSceneStates
    ScenePhaseMonitor *-- Logger : state
    SceneStateWindowViewModifier o-- ReferenceWritableKeyPath : keyPath

Ownership evidence

SampleApp/SampleApp.swift:19 — stored dependency or nearest verified ownership anchor

@main
struct SampleApp: App {
    @State private var appModel = AppModel()
    // ...
}

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

SampleApp/AppModel.swift:11 — representative execution boundary

@MainActor
@Observable
class AppModel {
    // ...
        case closed
    // ...
}

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

SampleApp/SampleApp.swift:18 — representative type boundary

@main
struct SampleApp: App {
    @State private var appModel = AppModel()
    // ...
}

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

Access control

Reference code

Packages/RealityKitContent/Sources/RealityKitContent/RealityKitContent.swift:11 — representative boundary

public let realityKitContentBundle = Bundle.module

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: SampleApp; Model: AppModel, SphereModel; View: ContentView, ImmersiveView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: updateWindowState, unregisterWindow, windowState, monitorScenePhase, body.
• Files: SampleApp/SampleApp.swift, SampleApp/AppModel.swift, SampleApp/SphereModel.swift, SampleApp/ContentView.swift, SampleApp/ImmersiveView.swift, SampleApp/Control Views/ControlsAttachment.swift.

Architecture takeaways

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