Capturing consistent color images

At a glance

Project structure

Source bundle/
├── ConstantColorCam/
│   ├── ConstantColorCamApp.swift
│   ├── CameraView.swift
│   ├── PhotosTabView.swift
│   ├── ContentView.swift
│   ├── DataModel.swift
│   ├── ViewFinderView.swift
│   ├── Camera.swift
│   └── PhotoLibrary.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── ConstantColorCam.xcodeproj/
    ├── .xcodesamplecode.plist
    └── project.pbxproj

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 3 project/configuration file(s) and 11 source declaration(s).

Overall architecture

flowchart LR
    N1["ConstantColorCamApp"]
    N2["ContentView"]
    N3["DataModel"]
    N4["SwiftUI / Photos APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

ConstantColorCam/ConstantColorCamApp.swift:10 — architecture anchor

@main
struct ConstantColorCamApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView().preferredColorScheme(.dark)
        }
    }
}

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

Ownership and state

classDiagram
    CameraView *-- DataModel : model
    CameraView o-- Showflasherror : showFlashError
    CameraView o-- Showfallbackphotodeliveryerror : showFallbackPhotoDeliveryError
    ShutterButton o-- Callback : action

Ownership evidence

ConstantColorCam/CameraView.swift:13 — stored dependency or nearest verified ownership anchor

struct CameraView: View {
    // ...
    @State private var model = DataModel()
    // ...
}

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

ConstantColorCam/Camera.swift:158 — representative execution boundary

class Camera: NSObject {
    // ...
        sessionQueue = DispatchQueue(label: "session queue")
    // ...
}

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

ConstantColorCam/ConstantColorCamApp.swift:11 — representative type boundary

@main
struct ConstantColorCamApp: App {
    // ...
            ContentView().preferredColorScheme(.dark)
    // ...
}

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

Access control

Reference code

ConstantColorCam/Camera.swift:18 — representative boundary

class Camera: NSObject {
    // ...
    private let captureSession = AVCaptureSession()
    // ...
}

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

Main application flow

sequenceDiagram
    actor User
    participant View as CameraView
    participant Camera
    participant Output as AVCapturePhotoOutput
    participant Results as PhotosTabView
    User->>View: Tap shutter
    View->>View: Validate option combination
    View->>Camera: set options and takePhoto()
    Camera->>Output: capturePhoto(settings, delegate)
    Output-->>Camera: didFinishProcessingPhoto
    Camera->>Camera: classify constant/fallback/normal result
    Camera-->>Results: photosViewVisible and image state

Reference code

ConstantColorCam/Camera.swift:389 — takePhoto

    func takePhoto() {
        guard let photoOutput else { return }
        constantColorPhoto = nil
        fallbackFrame = nil
        confidenceMap = nil
        normalPhoto = nil
        let photoSettings = AVCapturePhotoSettings()
        photoOutputReadinessCoordinator.startTrackingCaptureRequest(using: photoSettings)
        sessionQueue.async {
            photoSettings.flashMode = self.flashEnabled ? .on : .off
           if self.constantColorSupported {
                photoSettings.isConstantColorEnabled = self.constantColorEnabled
                photoSettings.isConstantColorFallbackPhotoDeliveryEnabled = self.fallBackPhotoDeliveryEnabled
           }
            photoSettings.maxPhotoDimensions = photoOutput.maxPhotoDimensions
            if let previewPhotoPixelFormatType = photoSettings.availablePreviewPhotoPixelFormatTypes.first {
                photoSettings.previewPhotoFormat = [kCVPixelBufferPixelFormatTypeKey as String: previewPhotoPixelFormatType]
            }
            photoSettings.photoQualityPrioritization = .balanced
            photoOutput.connection(with: .video)?.videoRotationAngle = 90
            self.videoOutput?.connection(with: .video)?.videoRotationAngle = 90
            photoOutput.capturePhoto(with: photoSettings, delegate: self)
            self.photoOutputReadinessCoordinator.stopTrackingCaptureRequest(using: photoSettings.uniqueID)
        }
    }

Naming conventions

• Types: App: ConstantColorCamApp; Model: DataModel; View: CameraView, ContentView, ImageView, PhotosTabView, ViewFinderView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: takePhoto, handleCameraPreviews, initialize, configureCaptureSession, checkCameraAuthorization, checkPhotoAuthorization, deviceInputFor, createImageFromPixelBuffer.
• Files: ConstantColorCam/ConstantColorCamApp.swift, ConstantColorCam/CameraView.swift, ConstantColorCam/PhotosTabView.swift, ConstantColorCam/ContentView.swift, ConstantColorCam/DataModel.swift, ConstantColorCam/ViewFinderView.swift.

Architecture takeaways

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