Creating 3D models as movable windows

At a glance

Project structure

Source bundle/
├── Creating a Volumetric Window/
│   ├── App/
│   │   ├── EntryPoint.swift
│   │   └── Info.plist
│   └── Views/
│       └── VolumetricWindow.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── Creating a Volumetric Window.xcodeproj/
    ├── .xcodesamplecode.plist
    └── project.pbxproj

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

Overall architecture

flowchart LR
    N1["EntryPoint"]
    N2["VolumetricWindow"]
    N3["SwiftUI / RealityKit APIs"]
    N1 --> N2
    N2 --> N3

Reference code

Creating a Volumetric Window/App/EntryPoint.swift:10 — architecture anchor

@main
struct EntryPoint: App {
    /// The multiplier for the height of the volumetric window.
    let heightModifier: CGFloat = 0.25

    var body: some Scene {
        // Configure a window group with a volumetric window.
        WindowGroup() {
            VolumetricWindow()
        }
        .windowStyle(.volumetric)
        // Scale the size of the window group relative to the volumetric window's size.
        .defaultSize(
            width: VolumetricWindow.defaultSize,
            height: heightModifier * VolumetricWindow.defaultSize,
            depth: VolumetricWindow.defaultSize,
            in: .meters
        )
    }
}

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
    EntryPoint *-- CGFloat : heightModifier
    VolumetricWindow *-- CGFloat : defaultSize
    VolumetricWindow *-- String : modelName

Ownership evidence

Creating a Volumetric Window/App/EntryPoint.swift:13 — stored dependency or nearest verified ownership anchor

@main
struct EntryPoint: App {
    // ...
    let heightModifier: CGFloat = 0.25
    // ...
}

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

Creating a Volumetric Window/Views/VolumetricWindow.swift:25 — representative execution boundary

                guard let model = try? await ModelEntity(named: modelName) else {
                    return
                }

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

Creating a Volumetric Window/App/EntryPoint.swift:11 — representative type boundary

@main
struct EntryPoint: App {
    // ...
    let heightModifier: CGFloat = 0.25
    // ...
}

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

Access control

Reference code

Creating a Volumetric Window/App/EntryPoint.swift:11 — representative boundary

@main
struct EntryPoint: App {
    // ...
    let heightModifier: CGFloat = 0.25
    // ...
}

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: feature-specific names rather than reusable layer suffixes.
• Protocols: no local protocol declaration in the scanned source.
• Methods: no representative method name extracted from the architectural files.
• Files: Creating a Volumetric Window/App/EntryPoint.swift, Creating a Volumetric Window/Views/VolumetricWindow.swift.

Architecture takeaways

• EntryPoint 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