Supporting HDR images in your app

At a glance

Project structure

Source bundle/
├── HDRDemo23/
│   ├── HDRDemo23App.swift
│   ├── RenderView.swift
│   ├── AdjustView.swift
│   ├── ImageView.swift
│   ├── MainView.swift
│   ├── Renderer.swift
│   ├── Adjustment.swift
│   ├── Asset.swift
│   ├── EditedAsset.swift
│   └── FilmStrip.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── HDRDemo23.xcodeproj/
    └── .xcodesamplecode.plist

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 15 source declaration(s).

Overall architecture

flowchart LR
    N1["HDRDemo23App"]
    N2["MainView"]
    N3["Renderer"]
    N4["SwiftUI / CoreImage APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

HDRDemo23/HDRDemo23App.swift:10 — architecture anchor

@main
struct HDRDemo23App: App {
    // ...
        WindowGroup {
            MainView()
        }
    // ...
}

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

Ownership and state

classDiagram
    PixelBufferView o-- CVPixelBuffer : pixelBuffer
    RenderView o-- EditedAsset : asset
    AdjustView o-- EditedAsset : asset
    AdjustView *-- Int : adjustmentIdx

Ownership evidence

HDRDemo23/RenderView.swift:18 — stored dependency or nearest verified ownership anchor

#if canImport(UIKit)
struct PixelBufferView: UIViewRepresentable {
    // ...
    let pixelBuffer: CVPixelBuffer?
    // ...
}
#endif

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

HDRDemo23/AdjustView.swift:25 — representative execution boundary

@MainActor
struct AdjustView: View {
    // ...
    @Bindable var asset: EditedAsset
    // ...
}

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

HDRDemo23/HDRDemo23App.swift:11 — representative type boundary

@main
struct HDRDemo23App: App {
    // ...
            MainView()
    // ...
}

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

Access control

Reference code

HDRDemo23/HDRDemo23App.swift:11 — representative boundary

@main
struct HDRDemo23App: App {
    // ...
            MainView()
    // ...
}

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: HDRDemo23App; Renderer: Renderer; View: AdjustView, AdjustmentView, ImageView, MainView, PixelBufferView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: makeUIView, updateUIView, makeNSView, updateNSView, update, importFromPhotoLibrary, toggleEdit, saveEdit.
• Files: HDRDemo23/HDRDemo23App.swift, HDRDemo23/RenderView.swift, HDRDemo23/AdjustView.swift, HDRDemo23/ImageView.swift, HDRDemo23/MainView.swift, HDRDemo23/Renderer.swift.

Architecture takeaways

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