Capturing screen content on iOS

At a glance

Project structure

Source bundle/
├── iOSSCKSample/
│   ├── iOSSCKSampleApp.swift
│   ├── CaptureManager.swift
│   ├── Views/
│   │   ├── CapturePickerView.swift
│   │   └── PickerConfigurationView.swift
│   ├── ContentView.swift
│   ├── PickerDelegate.swift
│   ├── Info.plist
│   └── iOSSCKSample.entitlements
├── Configuration/
│   └── SampleCode.xcconfig
└── iOSSCKSample.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 5 project/configuration file(s) and 8 source declaration(s).

Overall architecture

flowchart LR
    N1["iOSSCKSampleApp"]
    N2["ContentView"]
    N3["CaptureManager"]
    N4["ScreenCaptureKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

iOSSCKSample/iOSSCKSampleApp.swift:10 — architecture anchor

@main
struct SCKSampleApp: 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 ScreenCaptureKit.

Ownership and state

classDiagram
    CaptureManager *-- Logger : logger
    CaptureManager o-- SCRecordingOutput : finishedRecordingOutput
    CaptureManager *-- URL : lastRecordingURL
    CaptureManager *-- URL : lastClipURL

Ownership evidence

iOSSCKSample/CaptureManager.swift:20 — stored dependency or nearest verified ownership anchor

    private let logger = Logger()

    // MARK: - Published State

    // These properties mirror the state of the active stream and its outputs. SwiftUI views
    // read them directly through the `@EnvironmentObject` to drive their controls.
    @Published var isCapturing = false

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.

Class and protocol design

iOSSCKSample/iOSSCKSampleApp.swift:11 — representative type boundary

struct SCKSampleApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

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

Access control

Reference code

iOSSCKSample/CaptureManager.swift:20 — representative boundary

@MainActor
class CaptureManager: NSObject, ObservableObject {
    // ...
    private let logger = Logger()
    // ...
}

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: SCKSampleApp; Delegate: PickerDelegate; Manager: CaptureManager; View: CapturePickerView, ContentView, PickerConfigurationView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: presentFullDisplayPicker, presentInAppPicker, setupPicker, startCapture, tearDownStream, stopCapture, startRecording, stopRecording.
• Files: iOSSCKSample/CaptureManager.swift, iOSSCKSample/Views/CapturePickerView.swift, iOSSCKSample/ContentView.swift, iOSSCKSample/PickerDelegate.swift, iOSSCKSample/Views/PickerConfigurationView.swift.

Architecture takeaways

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