Construct an immersive environment for visionOS

At a glance

Project structure

Source bundle/
├── Meadow/
│   ├── MeadowApp.swift
│   ├── ContentView.swift
│   ├── EnvironmentLoader.swift
│   ├── ImmersiveView.swift
│   └── Info.plist
├── Packages/
│   └── RealityKitContent/
│       ├── Sources/
│       │   └── RealityKitContent/
│       │       └── RealityKitContent.swift
│       └── Package.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── Custom Meadow Immersive Environment.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 4 source declaration(s).

Overall architecture

flowchart LR
    N1["MeadowApp"]
    N2["ContentView"]
    N3["EnvironmentLoader"]
    N4["RealityKit / RealityKitContent APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

Meadow/MeadowApp.swift:10 — architecture anchor

@main
struct MeadowApp: App {

    @State var loader = EnvironmentLoader()

    var body: some Scene {
        // Window with a portal to the environment
        WindowGroup(id: "Window") {
            ContentView(loader: loader)
        }.windowStyle(.plain)

        // ImmersiveSpace showing the environment
        ImmersiveSpace(id: "ImmersiveSpace") {
            ImmersiveView(loader: loader)
        }.immersionStyle(selection: .constant(.progressive), in: .progressive)
    }
}

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
    MeadowApp *-- EnvironmentLoader : loader
    ContentView o-- EnvironmentLoader : loader
    ContentView *-- Entity : root
    ContentView *-- ModelEntity : portalPlane

Ownership evidence

Meadow/MeadowApp.swift:13 — stored dependency or nearest verified ownership anchor

@main
struct MeadowApp: App {
    // ...
    @State var loader = EnvironmentLoader()
    // ...
}

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

Meadow/ContentView.swift:33 — representative execution boundary

struct ContentView: View {
    // ...
                    world.addChild(try! await loader.getEntity())
    // ...
}

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

Meadow/MeadowApp.swift:11 — representative type boundary

@main
struct MeadowApp: App {
    // ...
    @State var loader = EnvironmentLoader()
    // ...
}

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

Access control

Reference code

Meadow/EnvironmentLoader.swift:16 — representative boundary

actor EnvironmentLoader {
    // ...
    private weak var entity: Entity?
    // ...
}

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: MeadowApp; Loader: EnvironmentLoader; View: ContentView, ImmersiveView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: getEntity.
• Files: Meadow/MeadowApp.swift, Meadow/ContentView.swift, Meadow/EnvironmentLoader.swift, Meadow/ImmersiveView.swift.

Architecture takeaways

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