Building an object reconstruction app

At a glance

Project structure

Source bundle/
└── ObjectCaptureReconstruction/
    ├── ObjectCaptureReconstructionApp.swift
    ├── AppDataModel.swift
    ├── Settings/
    │   ├── ReconstructionOptions/
    │   │   └── MaskingView.swift
    │   └── AdvancedReconstructionOptions/
    │       ├── PolygonCountView.swift
    │       └── TextureFormatView.swift
    ├── ContentView.swift
    └── Processing/
        ├── BottomBarView.swift
        ├── ModelView.swift
        ├── ProcessingView.swift
        ├── ReconstructionProgressView.swift
        ├── ReprocessView.swift
        └── TopBarView.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 4 project/configuration file(s) and 34 source declaration(s).

Overall architecture

flowchart LR
    N1["ObjectCaptureReconstructionApp"]
    N2["ContentView"]
    N3["AppDataModel"]
    N4["RealityKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

ObjectCaptureReconstruction/ObjectCaptureReconstructionApp.swift:10 — architecture anchor

@main
struct ObjectCaptureReconstructionApp: App {
    static let subsystem: String = "com.example.apple-samplecode.ObjectCaptureReconstruction"

    var body: some Scene {
        Window("ObjectCaptureReconstruction", id: "main") {
            ContentView()
                .frame(width: 400, height: 360)
        }
        .windowResizability(.contentSize)
    }
}

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
    ObjectCaptureReconstructionApp *-- String : subsystem
    AppDataModel *-- Logger : logger
    AppDataModel o-- PhotogrammetrySession : session
    AppDataModel o-- State : state

Ownership evidence

ObjectCaptureReconstruction/ObjectCaptureReconstructionApp.swift:12 — stored dependency or nearest verified ownership anchor

@main
struct ObjectCaptureReconstructionApp: App {
    static let subsystem: String = "com.example.apple-samplecode.ObjectCaptureReconstruction"

    // ...
}

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

ObjectCaptureReconstruction/AppDataModel.swift:15 — representative execution boundary

@MainActor @Observable class AppDataModel {
    // ...
        case ready
    // ...
}

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

ObjectCaptureReconstruction/ObjectCaptureReconstructionApp.swift:11 — representative type boundary

@main
struct ObjectCaptureReconstructionApp: App {
    static let subsystem: String = "com.example.apple-samplecode.ObjectCaptureReconstruction"

    // ...
}

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

Access control

Reference code

ObjectCaptureReconstruction/AppDataModel.swift:12 — representative boundary

private let logger = Logger(subsystem: ObjectCaptureReconstructionApp.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: ObjectCaptureReconstructionApp; Model: AppDataModel; View: BottomBarView, ContentView, FolderOptionsView, IgnoreBoundingBoxView, ImageFolderSelectionView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: startReconstruction, createSession, createReconstructionRequests, hash, getImageName, getFirstImage, isLoadableImageFile, getSessionOutput.
• Files: ObjectCaptureReconstruction/ObjectCaptureReconstructionApp.swift, ObjectCaptureReconstruction/AppDataModel.swift, ObjectCaptureReconstruction/Settings/ReconstructionOptions/MaskingView.swift, ObjectCaptureReconstruction/ContentView.swift, ObjectCaptureReconstruction/Processing/BottomBarView.swift, ObjectCaptureReconstruction/Processing/ModelView.swift.

Architecture takeaways

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