Segmenting objects using taps, scribbles or rectangles

At a glance

Project structure

Source bundle/
├── TapToSegment/
│   ├── TapToSegmentApp.swift
│   ├── SegmentationHandler.swift
│   └── ContentView.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── TapToSegment.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 4 source declaration(s).

Overall architecture

flowchart LR
    N1["TapToSegmentApp"]
    N2["ContentView"]
    N3["SegmentationHandler"]
    N4["Vision APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

TapToSegment/TapToSegmentApp.swift:10 — architecture anchor

@main
struct TapToSegmentApp: 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 Vision.

Ownership and state

classDiagram
    SegmentationHandler o-- ProgressReporter : assetDownloadingProgressReport
    SegmentationHandler o-- GenerateIterativeSegmentationRequest : segmentationRequest
    SegmentationHandler o-- ImageRequestHandler : imageHandler
    ContentView *-- SegmentationHandler : segmentationHandler

Ownership evidence

TapToSegment/SegmentationHandler.swift:14 — stored dependency or nearest verified ownership anchor

@Observable
class SegmentationHandler {
    // ...
    var assetDownloadingProgressReport: ProgressReporter? = nil
    // ...
}

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

TapToSegment/TapToSegmentApp.swift:11 — representative type boundary

struct TapToSegmentApp: 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

TapToSegment/ContentView.swift:13 — representative boundary

    @State private var segmentationHandler = SegmentationHandler()
    @State private var selectedPhoto: PhotosPickerItem?
    @State private var selectedImage: Image?
    @State private var originalUIImage: UIImage?
    @State private var displayedImageRect = CGRect()
    @State private var segmentationMaskImage: UIImage?

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: TapToSegmentApp; Handler: SegmentationHandler; View: ContentView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: prepareAsset, setImage, perform, performSegmentation, convertPoint, resetRequest, calculateImagePosition, scribbleCanvas.
• Files: TapToSegment/TapToSegmentApp.swift, TapToSegment/SegmentationHandler.swift, TapToSegment/ContentView.swift.

Architecture takeaways

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