Supporting Continuity Camera in your macOS app

At a glance

Project structure

Source bundle/
├── ContinuityCam/
│   ├── ContinuityCamApp.swift
│   ├── Views/
│   │   ├── ConfigurationView.swift
│   │   ├── MaterialView.swift
│   │   └── CameraPreview.swift
│   ├── Camera.swift
│   ├── ContentView.swift
│   ├── DeviceObservers.swift
│   └── ContinuityCam.entitlements
├── Configuration/
│   └── SampleCode.xcconfig
└── ContinuityCam.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 4 project/configuration file(s) and 17 source declaration(s).

Overall architecture

flowchart LR
    N1["ContinuityCamApp"]
    N2["ContentView"]
    N3["PreferredCameraObserver"]
    N4["AVFoundation APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

ContinuityCam/ContinuityCamApp.swift:10 — architecture anchor

@main
struct ContinuityCamApp: App {

    var body: some Scene {
        WindowGroup {
            ContentView()
                .navigationTitle("Continuity Camera Sample")
                .frame(minWidth: 800, minHeight: 600)
        }
    }
}

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
    ConfigurationView *-- CGFloat : sectionSpacing
    ConfigurationView o-- Camera : camera
    SectionHeader *-- String : title
    DevicePickerView *-- String : label

Ownership evidence

ContinuityCam/Views/ConfigurationView.swift:14 — stored dependency or nearest verified ownership anchor

struct ConfigurationView: View {
    // ...
    let sectionSpacing: CGFloat = 20
    // ...
}

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

ContinuityCam/Camera.swift:12 — representative execution boundary

@MainActor
class Camera: ObservableObject {
    // ...
        case noVideoDeviceAvailable
    // ...
}

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

ContinuityCam/ContinuityCamApp.swift:11 — representative type boundary

@main
struct ContinuityCamApp: App {
    // ...
            ContentView()
    // ...
}

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

Access control

Reference code

ContinuityCam/Camera.swift:29 — representative boundary

@MainActor
class Camera: ObservableObject {
    // ...
    private(set) var isSetup = false
    // ...
}

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: ContinuityCamApp; Observer: PreferredCameraObserver, VideoEffectsObserver; View: ConfigurationView, ContentView, DevicePickerView, EffectStatusView, MaterialView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: start, authorize, setup, setupDeviceDiscovery, setupInputs, addInput, resetToDefaultDevices, startSession.
• Files: ContinuityCam/ContinuityCamApp.swift, ContinuityCam/Views/ConfigurationView.swift, ContinuityCam/Camera.swift, ContinuityCam/ContentView.swift, ContinuityCam/Views/MaterialView.swift, ContinuityCam/Views/CameraPreview.swift.

Architecture takeaways

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