Generating an animation with a Core Image Render Destination

At a glance

Project structure

Source bundle/
├── Shared/
│   ├── RenderDestinationMetalViewApp.swift
│   ├── ContentView.swift
│   ├── MetalView.swift
│   ├── Renderer.swift
│   └── ViewRepresentable.swift
├── Configuration/
│   └── SampleCode.xcconfig
├── RenderDestinationMetalView.xcodeproj/
│   ├── .xcodesamplecode.plist
│   └── project.pbxproj
└── macOS/
    └── macOS.entitlements

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

Overall architecture

flowchart LR
    N1["RenderDestinationMetalViewApp"]
    N2["ContentView"]
    N3["Renderer"]
    N4["CoreImage APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

Shared/RenderDestinationMetalViewApp.swift:10 — architecture anchor

@main
struct RenderDestinationMetalViewApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

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 Core Image.

Ownership and state

classDiagram
    MetalView *-- Renderer : renderer
    Renderer o-- MTLDevice : device
    Renderer o-- MTLCommandQueue : commandQueue
    Renderer o-- CIContext : cicontext

Ownership evidence

Shared/MetalView.swift:13 — stored dependency or nearest verified ownership anchor

struct MetalView: ViewRepresentable {
    // ...
    @StateObject var renderer: Renderer
    // ...
}

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

Shared/Renderer.swift:23 — representative execution boundary

final class Renderer: NSObject, MTKViewDelegate, ObservableObject {
    // ...
    let inFlightSemaphore = DispatchSemaphore(value: maxBuffersInFlight)
    // ...
}

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

Shared/ViewRepresentable.swift:11 — representative type boundary

#if os(iOS) || os(tvOS)
protocol ViewRepresentable: UIViewRepresentable {
    associatedtype ViewType = UIViewType
    func makeView(context: Context) -> ViewType
    func updateView(_ view: ViewType, context: Context)
}
#endif

The source explicitly defines local protocol relationships: MetalView → ViewRepresentable.

Access control

Reference code

Shared/MetalView.swift:41 — representative boundary

    private func configure(view: MTKView, using renderer: Renderer) {
        view.delegate = renderer
    }

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: RenderDestinationMetalViewApp; Renderer: Renderer; View: ContentView, MetalView.
• Protocols: ViewRepresentable, ViewRepresentable.
• Methods: makeView, updateView, configure, draw, mtkView, makeUIView, updateUIView, makeNSView.
• Files: Shared/RenderDestinationMetalViewApp.swift, Shared/ContentView.swift, Shared/MetalView.swift, Shared/Renderer.swift, Shared/ViewRepresentable.swift.

Architecture takeaways

• RenderDestinationMetalViewApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches SwiftUI, CoreImage, MetalKit, Metal 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.
• Local protocol relationships provide an explicit substitution boundary.

Source map

• Official Apple documentation