Tracking Multiple Objects or Rectangles in Video

At a glance

Project structure

Source bundle/
├── VisionObjectTrack/
│   ├── AssetsViewController.swift
│   ├── AppDelegate.swift
│   ├── VisionTrackerProcessor.swift
│   ├── TrackingViewController.swift
│   ├── CommonTypes.swift
│   ├── TrackingImageView.swift
│   ├── VideoReader.swift
│   └── Base.lproj/
│       ├── LaunchScreen.storyboard
│       └── Main.storyboard
├── Configuration/
│   └── SampleCode.xcconfig
└── VisionObjectTrack.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 6 project/configuration file(s) and 16 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["AssetsViewController"]
    N3["VisionTrackerProcessor"]
    N4["Vision APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

VisionObjectTrack/AppDelegate.swift:10 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    var window: UIWindow?
}

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
    var *-- String : representedAssetIdentifier
    var o-- UIImageView : imageView
    var o-- PHFetchResult : assets
    AppDelegate o-- UIWindow : window

Ownership evidence

VisionObjectTrack/AssetsViewController.swift:15 — stored dependency or nearest verified ownership anchor

class AssetsViewControllerCell: UICollectionViewCell {
    // ...
    var representedAssetIdentifier: String = ""

    // ...
}

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

VisionObjectTrack/AssetsViewController.swift:32 — representative execution boundary

                DispatchQueue.main.async {
                    self.loadAssetsFromLibrary()
                }

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

VisionObjectTrack/VisionTrackerProcessor.swift:19 — representative type boundary

protocol VisionTrackerProcessorDelegate: AnyObject {
    func displayFrame(_ frame: CVPixelBuffer?, withAffineTransform transform: CGAffineTransform, rects: [TrackedPolyRect]?)
    func displayFrameCounter(_ frame: Int)
    func didFinifshTracking()
}

The source explicitly defines local protocol relationships: TrackingViewController → VisionTrackerProcessorDelegate.

Access control

Reference code

VisionObjectTrack/AssetsViewController.swift:48 — representative boundary

    private func loadAssetsFromLibrary() {
        let assetsOptions = PHFetchOptions()
        // ...
    }

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: Controller: AssetsViewController, TrackingViewController; Delegate: AppDelegate, VisionTrackerProcessorDelegate; Processor: VisionTrackerProcessor; View: TrackingImageView.
• Protocols: VisionTrackerProcessorDelegate.
• Methods: viewDidLoad, viewDidLayoutSubviews, loadAssetsFromLibrary, recalculateItemSize, asset, prepare, numberOfSections, collectionView.
• Files: VisionObjectTrack/AssetsViewController.swift, VisionObjectTrack/AppDelegate.swift, VisionObjectTrack/VisionTrackerProcessor.swift, VisionObjectTrack/TrackingViewController.swift, VisionObjectTrack/TrackingImageView.swift, VisionObjectTrack/VideoReader.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches UIKit, AVFoundation, Vision, Darwin 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.
• Local protocol relationships provide an explicit substitution boundary.

Source map

• Official Apple documentation