Building an object reconstruction app

At a glance

Project structure

Source bundle/
└── ObjectCaptureReconstruction/
    ├── AppDataModel.swift  # AppDataModel, State, DetailLevelOptionsUnderAdvancedMenu
    ├── ObjectCaptureReconstructionApp.swift  # ObjectCaptureReconstructionApp
    ├── Settings/
    │   ├── ReconstructionOptions/
    │   │   ├── MaskingView.swift  # MaskingView, MaskingOption
    │   │   └── IgnoreBoundingBoxView.swift  # IgnoreBoundingBoxView
    │   └── FolderOptions/
    │       └── FolderOptionsView.swift  # FolderOptionsView
    ├── ContentView.swift  # ContentView
    └── Processing/
        └── BottomBarView.swift  # BottomBarView

Structure observations

• The runtime boundary is Window; the tree is pruned to lifecycle, state, framework, rendering, and ECS files.
• The source is Swift; role-named types and feature folders separate the major responsibilities.

Overall architecture

flowchart LR
    ObjectCaptureReconstructionApp_1["ObjectCaptureReconstructionApp"]
    Window_2["Window"]
    ContentView_3["ContentView"]
    AppDataModel_4["AppDataModel"]
    RealityKit_entity_graph_5["RealityKit entity graph"]
    Object_Capture_session_pipeline_6["Object Capture session pipeline"]
    ObjectCaptureReconstructionApp_1 --> Window_2
    Window_2 --> ContentView_3
    ContentView_3 --> AppDataModel_4
    AppDataModel_4 --> RealityKit_entity_graph_5
    RealityKit_entity_graph_5 --> Object_Capture_session_pipeline_6

Reference code

ObjectCaptureReconstruction/ObjectCaptureReconstructionApp.swift:11 — executable or app-lifecycle anchor.

struct ObjectCaptureReconstructionApp: App {
    // ...
}

The diagram is a responsibility flow, not a claim that every adjacent node directly calls the next. It separates lifecycle, presentation, stable state, framework/session work, and the RealityKit entity graph.

Ownership and state

classDiagram
    AppDataModel --> PhotogrammetrySession : session
    ContentView *-- AppDataModel : appDataModel
    AppDataModel --> PhotogrammetrySession : detailLevelOptionUnderQualityMenu
    AppDataModel --> Configuration : sessionConfiguration

Ownership evidence

ObjectCaptureReconstruction/AppDataModel.swift:24 — representative stored state or nearest verified lifecycle anchor.

    private(set) var session: PhotogrammetrySession?

    // App's current state.
    var state: State = .ready {
        // ...
    }

Ownership is intentionally narrow: environment, bindings, observed objects, weak links, and delegate callbacks do not prove lifetime ownership. Initialized stored services and wrapper-managed state do; entities added inside a RealityKit content closure belong to that entity graph.

Class and protocol design

The reviewed source defines no local substitution protocol. Its App, View, delegate, renderer, ARKit, and RealityKit conformances are framework-facing contracts, so this document does not label the whole app protocol-oriented.

Access control

No reviewed Swift access example uses fileprivate, open; declarations without a modifier are internal.

Reference code

ObjectCaptureReconstruction/AppDataModel.swift:24 — representative visibility boundary.

    private(set) var session: PhotogrammetrySession?

    // App's current state.
    var state: State = .ready {
        // ...
    }

Logic ownership and placement

Design patterns

Naming conventions

• Role suffixes are evidence, not decoration: App: ObjectCaptureReconstructionApp; Model: AppDataModel; View: BottomBarView, ContentView, FolderOptionsView, IgnoreBoundingBoxView, ImageFolderSelectionView.
• Protocols: no app-defined protocol in the reviewed source.
• Commands use verb-led methods: startReconstruction, createSession, createReconstructionRequests, hash, getImageName, getFirstImage, isLoadableImageFile.
• Files and folders use primary-type or responsibility names such as Views, Models, Rendering, Components, Systems, Packages, or feature names where those boundaries exist.

Architecture takeaways

• Treat ObjectCaptureReconstructionApp as the owner of executable or scene lifecycle, not automatically as the owner of every entity created later.
• Keep view/controller input near presentation, but move sessions, reconstruction, capture, rendering, shared game state, or documents into stable owners when their lifetime exceeds one callback or render pass.
• Tie asynchronous session/output consumers to an explicit owner so cancellation and teardown follow the same lifecycle.

Source map

• Official Apple documentation