Combining 2D and 3D views in an immersive app

At a glance

Project structure

Source bundle/
├── MultiDimensionalImmersiveContent/
│   ├── MultiDimensionalImmersiveContentApp.swift
│   ├── RainbowModel.swift
│   ├── SwiftUIArch/
│   │   └── SwiftUIArcView.swift
│   ├── CALayerArch/
│   │   ├── CALayerArcView.swift
│   │   └── CALayerArcRepresentable.swift
│   ├── RainbowView.swift
│   ├── UIViewArch/
│   │   ├── UIViewArcView.swift
│   │   └── UIViewArcRepresentable.swift
│   └── Extensions.swift
├── Packages/
│   └── RealityKitContent/
│       ├── Sources/
│       │   └── RealityKitContent/
│       │       └── RealityKitContent.swift
│       └── Package.swift
└── 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 13 source declaration(s).

Overall architecture

flowchart LR
    N1["MultiDimensionalImmersiveContentApp"]
    N2["RainbowView"]
    N3["RainbowModel"]
    N4["RealityKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

MultiDimensionalImmersiveContent/MultiDimensionalImmersiveContentApp.swift:10 — architecture anchor

@main
struct MultiDimensionalImmersiveContentApp: App {
    var body: some Scene {
        ImmersiveSpace(id: "ImmersiveSpace") {
            RainbowView()
        }
    }
}

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
    RainbowModel *-- Array : archAttachments
    RainbowModel *-- Array : tapAttachments
    RainbowModel *-- EntityData : plane
    RainbowModel *-- Array : realityKitAssets

Ownership evidence

MultiDimensionalImmersiveContent/RainbowModel.swift:17 — stored dependency or nearest verified ownership anchor

@Observable
class RainbowModel {
    // ...
}

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

MultiDimensionalImmersiveContent/RainbowView.swift:12 — representative execution boundary

@MainActor struct RainbowView: View {
    // ...
    @State private var rainbowModel = RainbowModel()
    // ...
}

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

MultiDimensionalImmersiveContent/MultiDimensionalImmersiveContentApp.swift:11 — representative type boundary

@main
struct MultiDimensionalImmersiveContentApp: App {
    // ...
            RainbowView()
    // ...
}

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

Access control

Reference code

MultiDimensionalImmersiveContent/CALayerArch/CALayerArcView.swift:31 — representative boundary

    open override func layoutSubviews() {
        super.layoutSubviews()
        // ...
    }

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: MultiDimensionalImmersiveContentApp; Model: RainbowModel; View: CALayerArcView, RainbowView, SwiftUIArcView, UIViewArcView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: path, didMoveToSuperview, layoutSubviews, addAttachments, createArchAttachment, createAndPositionTapEntity, scaleAndPositionArches, createEntity.
• Files: MultiDimensionalImmersiveContent/MultiDimensionalImmersiveContentApp.swift, MultiDimensionalImmersiveContent/RainbowModel.swift, MultiDimensionalImmersiveContent/SwiftUIArch/SwiftUIArcView.swift, MultiDimensionalImmersiveContent/CALayerArch/CALayerArcView.swift, MultiDimensionalImmersiveContent/RainbowView.swift, MultiDimensionalImmersiveContent/UIViewArch/UIViewArcView.swift.

Architecture takeaways

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