Diorama

At a glance

Project structure

Source bundle/
├── Diorama/
│   ├── DioramaApp.swift
│   ├── ViewModel.swift
│   ├── LearnMoreView.swift
│   ├── AttachmentsProvider.swift
│   └── ContentView.swift
└── Packages/
    └── RealityKitContent/
        └── Sources/
            └── RealityKitContent/
                ├── PointOfInterestComponent.swift
                ├── BillboardComponent.swift
                ├── BillboardSystem.swift
                ├── RegionSpecificComponent.swift
                ├── TrailAnimationSystem.swift
                ├── TrailComponent.swift
                └── Style.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 22 source declaration(s).

Overall architecture

flowchart LR
    N1["DioramaApp"]
    N2["ContentView"]
    N3["ViewModel"]
    N4["AttachmentsProvider"]
    N5["RealityKit / SwiftUI APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

Diorama/DioramaApp.swift:13 — architecture anchor

@main
struct DioramaApp: App {
    @UIApplicationDelegateAdaptor(AppDelegate.self) var appDelegate
    // ...
}

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

Ownership and state

classDiagram
    DioramaApp *-- ViewModel : viewModel
    ViewModel o-- Entity : rootEntity
    ViewModel *-- Bool : showImmersiveContent
    ViewModel *-- Float : sliderValue

Ownership evidence

Diorama/DioramaApp.swift:18 — stored dependency or nearest verified ownership anchor

@main
struct DioramaApp: App {
    // ...
    @State private var viewModel = ViewModel()
    // ...
}

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

Diorama/ContentView.swift:32 — representative execution boundary

                    Task {
                        // ...
                            viewModel.resetAudio()
                        // ...
                    }

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

Diorama/DioramaApp.swift:14 — representative type boundary

@main
struct DioramaApp: App {
    @UIApplicationDelegateAdaptor(AppDelegate.self) var appDelegate
    // ...
}

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

Access control

Reference code

Diorama/ContentView.swift:78 — representative boundary

    private func update() {
        viewModel.updateTerrainMaterial()
        viewModel.updateRegionSpecificOpacity()
    }

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: DioramaApp; Component: BillboardComponent, ControlledOpacityComponent, FlockingComponent, PointOfInterestComponent, PointOfInterestRuntimeComponent; Delegate: AppDelegate; Provider: AttachmentsProvider; System: BillboardSystem, FlockingSystem, TrailAnimationSystem; View: ContentView, DioramaView, ImagesView, LearnMoreView; ViewModel: ViewModel.
• Protocols: no local protocol declaration in the scanned source.
• Methods: applicationShouldTerminateAfterLastWindowClosed, updateScale, updateRegionSpecificOpacity, setupAudio, resetAudio, updateTerrainMaterial, opacity, gain.
• Files: Diorama/DioramaApp.swift, Diorama/ViewModel.swift, Packages/RealityKitContent/Sources/RealityKitContent/PointOfInterestComponent.swift, Packages/RealityKitContent/Sources/RealityKitContent/BillboardComponent.swift, Packages/RealityKitContent/Sources/RealityKitContent/BillboardSystem.swift, Packages/RealityKitContent/Sources/RealityKitContent/RegionSpecificComponent.swift.

Architecture takeaways

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