Scanning objects using Object Capture

At a glance

Project structure

Source bundle/
└── GuidedCaptureSample/
    └── GuidedCaptureSample/
        ├── GuidedCaptureSampleApp.swift
        ├── Views/
        │   ├── HelpPageView.swift
        │   ├── CaptureOverlayView.swift
        │   ├── ReconstructionPrimaryView.swift
        │   ├── ModelView.swift
        │   ├── OnboardingButtonView.swift
        │   ├── BottomOverlayButtons.swift
        │   ├── PlayerView.swift
        │   ├── TopOverlayButtons.swift
        │   └── TutorialPageView.swift
        ├── AppDataModel.swift
        └── CaptureFolderManager.swift

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 87 source declaration(s).

Overall architecture

flowchart LR
    N1["GuidedCaptureSampleApp"]
    N2["ContentView"]
    N3["Coordinator"]
    N4["RealityKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

GuidedCaptureSample/GuidedCaptureSample/GuidedCaptureSampleApp.swift:10 — architecture anchor

@main
struct GuidedCaptureSampleApp: App {
    static let subsystem: String = "com.example.apple-samplecode.guided-capture-sample"

    var body: some Scene {
        WindowGroup {
            ContentView()
                .environment(AppDataModel.instance)
        }
    }
}

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

Ownership and state

classDiagram
    GuidedCaptureSampleApp *-- String : subsystem
    AppDataModel *-- Logger : logger
    AppDataModel *-- AppDataModel : instance
    AppDataModel o-- PhotogrammetrySession : photogrammetrySession

Ownership evidence

GuidedCaptureSample/GuidedCaptureSample/GuidedCaptureSampleApp.swift:12 — stored dependency or nearest verified ownership anchor

@main
struct GuidedCaptureSampleApp: App {
    static let subsystem: String = "com.example.apple-samplecode.guided-capture-sample"

    // ...
}

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

GuidedCaptureSample/GuidedCaptureSample/AppDataModel.swift:16 — representative execution boundary

@MainActor
@Observable
class AppDataModel: Identifiable {
    static let instance = AppDataModel()
    // ...
}

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

GuidedCaptureSample/GuidedCaptureSample/Views/CaptureOverlayView.swift:237 — representative type boundary

protocol OverlayButtons {
    func isCapturingStarted(state: ObjectCaptureSession.CaptureState) -> Bool
}

The source explicitly defines local protocol relationships: BottomOverlayButtons → OverlayButtons, TopOverlayButtons → OverlayButtons.

Access control

Reference code

GuidedCaptureSample/GuidedCaptureSample/AppDataModel.swift:13 — representative boundary

private let logger = Logger(subsystem: GuidedCaptureSampleApp.subsystem,
                            category: "AppDataModel")

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: GuidedCaptureSampleApp; Controller: ARQuickLookController; Coordinator: Coordinator; Manager: CaptureFolderManager; Model: AppDataModel; View: AVPlayerView, AutoDetectionStateView, BoundingBoxGuidanceView, CaptureModeGuidanceView, CaptureOverlayView.
• Protocols: OverlayButtons.
• Methods: endCapture, removeCaptureFolder, setShowOverlaySheets, saveDraft, attachListeners, detachListeners, handleAppTermination, startNewCapture.
• Files: GuidedCaptureSample/GuidedCaptureSample/GuidedCaptureSampleApp.swift, GuidedCaptureSample/GuidedCaptureSample/Views/HelpPageView.swift, GuidedCaptureSample/GuidedCaptureSample/AppDataModel.swift, GuidedCaptureSample/GuidedCaptureSample/Views/CaptureOverlayView.swift, GuidedCaptureSample/GuidedCaptureSample/Views/ReconstructionPrimaryView.swift, GuidedCaptureSample/GuidedCaptureSample/Views/ModelView.swift.

Architecture takeaways

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