Detecting Hand Poses with Vision

At a glance

Project structure

Source bundle/
├── HandPose/
│   ├── AppDelegate.swift
│   ├── HandGestureProcessor.swift
│   ├── CameraView.swift
│   ├── CameraViewController.swift
│   ├── SceneDelegate.swift
│   ├── Base.lproj/
│   │   ├── LaunchScreen.storyboard
│   │   └── Main.storyboard
│   ├── HandPose.entitlements
│   └── Info.plist
├── Configuration/
│   └── SampleCode.xcconfig
└── HandPose.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 7 project/configuration file(s) and 7 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["CameraViewController"]
    N3["HandGestureProcessor"]
    N4["Vision APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

HandPose/AppDelegate.swift:11 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
}

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
    HandGestureProcessor *-- CGFloat : pinchMaxDistance
    HandGestureProcessor *-- Int : evidenceCounterStateTrigger
    HandGestureProcessor o-- Callback : didChangeStateClosure
    HandGestureProcessor *-- PointsPair : lastProcessedPointsPair

Ownership evidence

HandPose/HandGestureProcessor.swift:32 — stored dependency or nearest verified ownership anchor

class HandGestureProcessor {
    // ...
    private let pinchMaxDistance: CGFloat
    // ...
}

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

HandPose/AppDelegate.swift:12 — representative type boundary

class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
}

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

Access control

Reference code

HandPose/CameraView.swift:14 — representative boundary

    private var overlayLayer = CAShapeLayer()
    private var pointsPath = UIBezierPath()

    var previewLayer: AVCaptureVideoPreviewLayer {
        return layer as! AVCaptureVideoPreviewLayer
    }

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: CameraViewController; Delegate: AppDelegate, SceneDelegate; Processor: HandGestureProcessor; View: CameraView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: application, display, displayInViewController, reset, processPointsPair, midPoint, distance, layoutSublayers.
• Files: HandPose/AppDelegate.swift, HandPose/HandGestureProcessor.swift, HandPose/CameraView.swift, HandPose/CameraViewController.swift, HandPose/SceneDelegate.swift.

Architecture takeaways

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