Building an immersive media viewing experience

At a glance

Project structure

Source bundle/
└── DestinationVideo/
    ├── DestinationVideo.swift
    ├── Views/
    │   ├── VideoInfoView.swift
    │   ├── visionOS/
    │   │   ├── ProfileButton.swift
    │   │   ├── ImmersiveEnvironmentPickerView.swift
    │   │   └── TrailerView.swift
    │   └── VideoCardView.swift
    ├── Player/
    │   ├── InlinePlayerView.swift
    │   ├── PlayerModel.swift
    │   ├── SystemPlayerView.swift
    │   └── PlayerView.swift
    ├── Model/
    │   └── visionOS/
    │       └── EnvironmentStateHandler.swift
    └── SharePlay/
        └── WatchingCoordinator.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 6 project/configuration file(s) and 69 source declaration(s).

Overall architecture

flowchart LR
    N1["DestinationVideo"]
    N2["ContentView"]
    N3["Coordinator"]
    N4["EnvironmentStateHandler"]
    N5["SwiftUI / SwiftData APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

DestinationVideo/DestinationVideo.swift:13 — architecture anchor

@main
struct DestinationVideo: App {
    // ...
    private let modelContainer: ModelContainer
    // ...
}

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
    DestinationVideo o-- ModelContainer : modelContainer
    DestinationVideo *-- PlayerModel : player
    DestinationVideo *-- ImmersiveEnvironment : immersiveEnvironment
    DestinationVideo *-- ImmersiveContentBrightness : contentBrightness

Ownership evidence

DestinationVideo/DestinationVideo.swift:16 — stored dependency or nearest verified ownership anchor

@main
struct DestinationVideo: App {
    // ...
    private let modelContainer: ModelContainer
    // ...
}

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

DestinationVideo/Model/Data/Genre.swift:38 — representative execution boundary

extension SampleData {
    @MainActor static let genres = [
        Genre(id: 0, name: "Drama"),
        Genre(id: 1, name: "Romance"),
        Genre(id: 2, name: "Comedy"),
        Genre(id: 3, name: "Action"),
        Genre(id: 4, name: "Adventure"),
        Genre(id: 5, name: "Documentary"),
        Genre(id: 6, name: "Mystery"),
        Genre(id: 7, name: "Animation"),
        Genre(id: 8, name: "Sci-Fi")
    ]
}

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

DestinationVideo/Views/VideoInfoView.swift:11 — representative type boundary

struct InfoView: View {
    @Environment(\.horizontalSizeClass) private var horizontalSizeClass
    // ...
}

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

Access control

Reference code

DestinationVideo/ContentView.swift:12 — representative boundary

struct ContentView: View {
    @Environment(PlayerModel.self) private var player
    // ...
}

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: Coordinator: Coordinator, WatchingCoordinator; Delegate: PlaybackCoordinatorDelegate; Handler: EnvironmentStateHandler; Model: PlayerModel; Observer: PlayerViewObserver; View: CategoryListView, CategoryView, ContentView, DetailView, GenreView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: dismissAfterDelay, makeUIViewController, updateUIViewController, makePlayerUI, willEndFullScreenPresentation, playerViewController, observePlayback, configureAudioSession.
• Files: DestinationVideo/DestinationVideo.swift, DestinationVideo/Player/InlinePlayerView.swift, DestinationVideo/Player/PlayerModel.swift, DestinationVideo/Player/SystemPlayerView.swift, DestinationVideo/Model/visionOS/EnvironmentStateHandler.swift, DestinationVideo/Player/PlayerView.swift.

Architecture takeaways

• DestinationVideo is the main source-visible entry or composition anchor for this sample.
• Framework work reaches SwiftUI, SwiftData, AVKit, GroupActivities 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