Bringing your SceneKit projects to RealityKit

At a glance

Project structure

Source bundle/
├── Pyro Panda RealityKit/
│   ├── Pyro Panda RealityKit/
│   │   ├── PyroPandaRealityKitApp.swift
│   │   └── Components/
│   │       └── HeroComponent.swift
│   └── Packages/
│       ├── AgentComponent/
│       │   └── Sources/
│       │       └── AgentComponent/
│       │           └── AgentComponent.swift
│       ├── WorldCamera/
│       │   └── Sources/
│       │       └── WorldCamera/
│       │           ├── WorldCameraComponent.swift
│       │           ├── FollowComponent.swift
│       │           └── WorldCameraSystem.swift
│       ├── CharacterMovement/
│       │   └── Sources/
│       │       └── CharacterMovement/
│       │           └── CharacterMovementComponent.swift
│       └── ControllerInput/
│           └── Sources/
│               └── HapticUtility/
│                   └── HapticUtility.swift
└── Pyro Panda SceneKit/
    └── Swift/
        ├── Shared/
        │   └── GameController.swift
        ├── iOS/
        │   └── AppDelegate.swift
        ├── macOS/
        │   └── AppDelegate.swift
        └── tvOS/
            └── AppDelegate.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 22 project/configuration file(s) and 86 source declaration(s).

Overall architecture

flowchart LR
    Bundle["Sample bundle"]
    V1["Pyro Panda RealityKit"]
    V2["Pyro Panda SceneKit"]
    Boundary["RealityKit APIs"]
    Bundle --> V1
    V1 --> Boundary
    Bundle --> V2
    V2 --> Boundary

Reference code

Pyro Panda RealityKit/Pyro Panda RealityKit/PyroPandaRealityKitApp.swift:12 — architecture anchor

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

Interpretation

The branches represent separate entry-bearing project variants in the downloaded bundle, not runtime calls between those variants. Each branch is intentionally collapsed at the documented framework boundary; the detailed target-local flow remains in the cited files. Ownership is claimed only where the next section cites a stored property or assignment.

Ownership and state

classDiagram
    AgentComponent o-- AgentType : agentType
    AgentComponent o-- AgentState : state
    AgentComponent o-- PositionConstraints : positionConstraints
    AgentComponent *-- Dictionary : stateWeights

Ownership evidence

Pyro Panda RealityKit/Packages/AgentComponent/Sources/AgentComponent/AgentComponent.swift:24 — stored dependency or nearest verified ownership anchor

public struct AgentComponent: Component {
    // ...
    public let agentType: AgentType?
    // ...
}

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

Pyro Panda RealityKit/Packages/AgentComponent/Sources/AgentComponent/AgentComponent.swift:117 — representative execution boundary

        Task { await AgentSystem.registerSystem() }

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

Pyro Panda SceneKit/Swift/Shared/UI/Menu.swift:10 — representative type boundary

protocol MenuDelegate: NSObjectProtocol {

    func fStopChanged(_ value: CGFloat)
    func focusDistanceChanged(_ value: CGFloat)
    func debugMenuSelectCameraAtIndex(_ index: Int)
}

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

Access control

Reference code

Pyro Panda RealityKit/Packages/AgentComponent/Sources/AgentComponent/AgentComponent.swift:24 — representative boundary

public struct AgentComponent: Component {
    // ...
    public let agentType: AgentType?
    // ...
}

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: PyroPandaRealityKitApp; Component: AgentComponent, AttackComponent, BaseComponent, CharacterMovementComponent, CharacterStateComponent; Controller: GameController, WASDController; Delegate: AppDelegate, ButtonOverlayDelegate, MenuDelegate, PadOverlayDelegate; Handler: CameraLockActionHandler, CameraOrientActionHandler, HeroAttackActionHandler; Model: AppModel; System: AgentSystem, CharacterMovementSystem, ControllerInputSystem, FollowSystem, MoveBetweenSystem; View: CollectedItemsView, CongratulationsView, ContentView, ImmersiveView, PyroPandaView.
• Protocols: MenuDelegate, ButtonOverlayDelegate, PadOverlayDelegate.
• Methods: clamp, cameraAxisOrientation, updateWith, setupGameController, setupCharacter, setupPhysics, setupCollisions, setupFollowCamera.
• Files: Pyro Panda RealityKit/Pyro Panda RealityKit/PyroPandaRealityKitApp.swift, Pyro Panda RealityKit/Packages/AgentComponent/Sources/AgentComponent/AgentComponent.swift, Pyro Panda RealityKit/Packages/WorldCamera/Sources/WorldCamera/WorldCameraComponent.swift, Pyro Panda SceneKit/Swift/Shared/GameController.swift, Pyro Panda RealityKit/Packages/CharacterMovement/Sources/CharacterMovement/CharacterMovementComponent.swift, Pyro Panda RealityKit/Packages/ControllerInput/Sources/HapticUtility/HapticUtility.swift.

Architecture takeaways

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