Playing immersive media with RealityKit

At a glance

Project structure

Source bundle/
└── RealityKitImmersivePlayback/
    ├── RealityKitImmersivePlaybackApp.swift
    ├── Models/
    │   ├── AppModel.swift
    │   ├── VideoModel.swift
    │   ├── PlayerModel.swift
    │   ├── PlaybackReadiness.swift
    │   └── VideoModes.swift
    ├── Views/
    │   ├── ContentView.swift
    │   ├── ImmersiveControlsView.swift
    │   ├── LoadingIndicator.swift
    │   ├── TransportView.swift
    │   └── VideoPlayerView.swift
    └── Scenes/
        └── PlayerImmersiveSpace.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 26 source declaration(s).

Overall architecture

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

Reference code

RealityKitImmersivePlayback/RealityKitImmersivePlaybackApp.swift:10 — architecture anchor

@main
struct RealityKitImmersivePlaybackApp: App {
    @Environment(\.openWindow) private var openWindow
    // ...
}

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
    RealityKitImmersivePlaybackApp *-- AppModel : appModel
    AppModel o-- AVPlayer : player
    AppModel o-- PlayerModel : playerModel
    AppModel o-- WindowState : windowState

Ownership evidence

RealityKitImmersivePlayback/RealityKitImmersivePlaybackApp.swift:17 — stored dependency or nearest verified ownership anchor

@main
struct RealityKitImmersivePlaybackApp: 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

RealityKitImmersivePlayback/Models/AppModel.swift:13 — representative execution boundary

@MainActor
@Observable
final class AppModel {
    let player: AVPlayer
    // ...
}

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

RealityKitImmersivePlayback/RealityKitImmersivePlaybackApp.swift:11 — representative type boundary

@main
struct RealityKitImmersivePlaybackApp: App {
    @Environment(\.openWindow) private var openWindow
    // ...
}

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

Access control

Reference code

RealityKitImmersivePlayback/Extensions/VideoPlayerComponent+Extensions.swift:17 — representative boundary

    public var displayMessage: String? {
        // ...
        case .play:
        // ...
    }

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: RealityKitImmersivePlaybackApp; Model: AppModel, PlayerModel, VideoModel; Scene: PlaybackScene; View: ContentView, ImmersiveControlsView, TransportView, VideoPlayerView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: closeImmersivePlayer, makeDefaultScenes, openImmersivePlayer, transitionStageFromBrowsingToPlayback, transitionStageFromPlaybackToBrowsing, transitionPlaybackStages, transitionStage, commitStage.
• Files: RealityKitImmersivePlayback/RealityKitImmersivePlaybackApp.swift, RealityKitImmersivePlayback/Models/AppModel.swift, RealityKitImmersivePlayback/Models/VideoModel.swift, RealityKitImmersivePlayback/Models/PlayerModel.swift, RealityKitImmersivePlayback/Views/ContentView.swift, RealityKitImmersivePlayback/Views/ImmersiveControlsView.swift.

Architecture takeaways

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