Presenting images in RealityKit

At a glance

Project structure

Source bundle/
├── SpatialPhotosSample/
│   ├── SpatialPhotosSample/
│   │   ├── SpatialPhotosSampleApp.swift
│   │   ├── Delegates/
│   │   │   ├── AppDelegate.swift
│   │   │   └── SceneDelegate.swift
│   │   ├── Model/
│   │   │   └── AppModel.swift
│   │   ├── Views/
│   │   │   ├── ContentView.swift
│   │   │   ├── ImagePresentationView.swift
│   │   │   └── OrnamentsView.swift
│   │   └── Info.plist
│   └── SpatialPhotosSample.xcodeproj/
│       ├── .xcodesamplecode.plist
│       └── project.pbxproj
└── Configuration/
    └── SampleCode.xcconfig

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

Overall architecture

flowchart LR
    N1["SpatialPhotosSampleApp"]
    N2["ContentView"]
    N3["AppModel"]
    N4["RealityKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

SpatialPhotosSample/SpatialPhotosSample/SpatialPhotosSampleApp.swift:10 — architecture anchor

@main
struct SpatialPhotosSampleApp: App {
    @State private var appModel = AppModel()
    @UIApplicationDelegateAdaptor private var appDelegate: AppDelegate

    var body: some Scene {
        WindowGroup {
            ContentView()
                .environment(appModel)
                .frame(minWidth: 600, maxWidth: 2000, minHeight: 600, maxHeight: 2000)
        }
        .windowResizability(.contentSize)
        .windowStyle(.plain)
    }
}

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
    SpatialPhotosSampleApp *-- AppModel : appModel
    SpatialPhotosSampleApp o-- AppDelegate : appDelegate
    AppModel *-- Array : imageNames
    AppModel *-- Int : imageIndex

Ownership evidence

SpatialPhotosSample/SpatialPhotosSample/SpatialPhotosSampleApp.swift:12 — stored dependency or nearest verified ownership anchor

@main
struct SpatialPhotosSampleApp: App {
    @State private var appModel = AppModel()
    // ...
}

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

SpatialPhotosSample/SpatialPhotosSample/Model/AppModel.swift:17 — representative execution boundary

@MainActor
@Observable
class AppModel {
    // ...
        var imageURLs: [URL] = []
    // ...
}

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

SpatialPhotosSample/SpatialPhotosSample/SpatialPhotosSampleApp.swift:11 — representative type boundary

@main
struct SpatialPhotosSampleApp: App {
    @State private var appModel = AppModel()
    // ...
}

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

Access control

Reference code

SpatialPhotosSample/SpatialPhotosSample/SpatialPhotosSampleApp.swift:12 — representative boundary

@main
struct SpatialPhotosSampleApp: App {
    @State private var appModel = AppModel()
    // ...
}

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: SpatialPhotosSampleApp; Delegate: AppDelegate, SceneDelegate; Model: AppModel; View: ContentView, ImagePresentationView, OrnamentsView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: application, createImagePresentationComponent, generateSpatial3DImage, scene, scaleImagePresentationToFit.
• Files: SpatialPhotosSample/SpatialPhotosSample/SpatialPhotosSampleApp.swift, SpatialPhotosSample/SpatialPhotosSample/Delegates/AppDelegate.swift, SpatialPhotosSample/SpatialPhotosSample/Model/AppModel.swift, SpatialPhotosSample/SpatialPhotosSample/Delegates/SceneDelegate.swift, SpatialPhotosSample/SpatialPhotosSample/Views/ContentView.swift, SpatialPhotosSample/SpatialPhotosSample/Views/ImagePresentationView.swift.

Architecture takeaways

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