Editing and playing HDR video

At a glance

Project structure

Source bundle/
├── CommonUI-macOS/
│   ├── ContentView.swift
│   └── AppDelegate.swift
├── CIFilter-iOS/
│   ├── AppDelegate.swift
│   ├── ContentView.swift
│   └── SceneDelegate.swift
├── CustomCompositor/
│   └── AVVideoCompositionBuilder.swift
├── CommonSource/
│   ├── Composition.swift
│   └── HDRIndicator.ci.metal
├── BuiltInCompositor/
│   ├── AVVideoCompositionBuilder.swift
│   ├── Base.lproj/
│   │   └── Main.storyboard
│   └── BuiltInCompositor.entitlements
└── CIFilter/
    └── AVVideoCompositionBuilder.swift

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Metal, Swift.
• The verified tree contains 14 project/configuration file(s) and 21 source declaration(s).

Overall architecture

flowchart LR
    Bundle["Sample bundle"]
    V1["CIFilter-iOS"]
    V2["CommonUI-macOS"]
    Boundary["AVFoundation APIs"]
    Bundle --> V1
    V1 --> Boundary
    Bundle --> V2
    V2 --> Boundary

Reference code

CIFilter-iOS/AppDelegate.swift:10 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        return true
    }

    // MARK: UISceneSession Lifecycle

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

}

Interpretation

The branches represent separate entry-bearing project variants in the downloaded bundle, not runtime calls between those variants. Each branch is intentionally collapsed at the documented framework boundary; the detailed target-local flow remains in the cited files. Ownership is claimed only where the next section cites a stored property or assignment.

Ownership and state

classDiagram
    PlayerView o-- Player : player
    Coordinator o-- PlayerView : playerView
    ContentView *-- AlertReason : alertReason
    ContentView *-- ProgressChecker : exportProgressChecker

Ownership evidence

CommonUI-macOS/ContentView.swift:30 — stored dependency or nearest verified ownership anchor

class PlayerView: AVPlayerView {
    // ...
        self.player = player
    // ...
}

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.

No source-visible execution, scheduling, or synchronization boundary was found in the indexed source.

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

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

CIFilter-iOS/AppDelegate.swift:11 — representative type boundary

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
        return true
    // ...
}

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

Access control

Reference code

CommonSource/Composition.swift:37 — representative boundary

    struct ProgressChecker {
        private var exportSession: AVAssetExportSession? = nil
        // ...
    }

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: Builder: AVVideoCompositionBuilder; Coordinator: Coordinator; Delegate: AppDelegate, SceneDelegate; Loader: AssetLoader; View: ContentView, PlayerView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: play, pause, updateNSView, makeNSView, makeCoordinator, triggerAlert, exportAsset, getProgressPercentage.
• Files: CommonUI-macOS/ContentView.swift, CIFilter-iOS/AppDelegate.swift, CommonUI-macOS/AppDelegate.swift, CIFilter-iOS/ContentView.swift, CustomCompositor/AVVideoCompositionBuilder.swift, BuiltInCompositor/AVVideoCompositionBuilder.swift.

Architecture takeaways

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