Applying visual effects to foreground subjects

At a glance

Project structure

Source bundle/
├── SubjectLiftingEffects/
│   ├── SubjectLiftingEffectsApp.swift
│   ├── ContentView.swift
│   └── EffectsPipeline.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── SubjectLiftingEffects.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 10 source declaration(s).

Overall architecture

flowchart LR
    N1["SubjectLiftingEffectsApp"]
    N2["ContentView"]
    N3["EffectsPipeline"]
    N4["SwiftUI / CoreImage APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

SubjectLiftingEffects/SubjectLiftingEffectsApp.swift:11 — architecture anchor

@main
struct SubjectLiftingEffectsApp: App {
    // ...
}

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

Ownership and state

classDiagram
    SubjectLiftingEffectsApp *-- EffectsPipeline : pipeline
    EffectPicker o-- Effect : effect
    BackgroundPicker o-- Background : background
    ImagePicker o-- EffectsPipeline : pipeline

Ownership evidence

SubjectLiftingEffects/SubjectLiftingEffectsApp.swift:15 — stored dependency or nearest verified ownership anchor

@main
struct SubjectLiftingEffectsApp: App {
    // ...
    @StateObject private var pipeline = EffectsPipeline()
    // ...
}

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

SubjectLiftingEffects/SubjectLiftingEffectsApp.swift:12 — representative type boundary

struct SubjectLiftingEffectsApp: App {
    // ...
}

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

Access control

Reference code

SubjectLiftingEffects/ContentView.swift:46 — representative boundary

struct ImagePicker: View {
    // ...
    @State private var imageSelection: PhotosPickerItem? = nil
    // ...
}

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: SubjectLiftingEffectsApp; Pipeline: EffectsPipeline; View: ContentView, OutputView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: loadInputImage, regenerate, apply, subjectMask, instances, image, loadImage, render.
• Files: SubjectLiftingEffects/SubjectLiftingEffectsApp.swift, SubjectLiftingEffects/ContentView.swift, SubjectLiftingEffects/EffectsPipeline.swift.

Architecture takeaways

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