Creating 3D entities with RealityKit

At a glance

Project structure

Source bundle/
└── Creating 3D Shapes/
    ├── App/
    │   └── EntryPoint.swift  # EntryPoint
    ├── Views/
    │   └── ShapesView.swift  # ShapesView
    └── Entities/
        └── ShapesView+Entities.swift

Structure observations

• The runtime boundary is WindowGroup; the pruned tree lists only files that explain lifecycle, state, or framework integration.
• App code is compact; any explicit model, provider, or entity owner is still shown below rather than collapsed into view-local state.

Overall architecture

flowchart LR
    EntryPoint_1["EntryPoint"]
    WindowGroup_2["WindowGroup"]
    ShapesView_3["ShapesView"]
    RealityView_entity_graph_4["RealityView entity graph"]
    RealityKit_entity_graph_5["RealityKit entity graph"]
    EntryPoint_1 --> WindowGroup_2
    WindowGroup_2 --> ShapesView_3
    ShapesView_3 --> RealityView_entity_graph_4
    RealityView_entity_graph_4 --> RealityKit_entity_graph_5

Reference code

Creating 3D Shapes/App/EntryPoint.swift:11 — the app or executable entry declares the outer scene lifecycle.

struct EntryPoint: App {
    var body: some Scene {
        WindowGroup {
            ShapesView()
        }
    }
}

The diagram is a responsibility flow, not a claim that every adjacent node directly calls the next. It keeps scene ownership, shared state, RealityKit content, and framework-provider work at separate levels.

Ownership and state

classDiagram
    EntryPoint_1 --> ShapesView_2 : scene content
    ShapesView_2 --> Framework_3 : invokes framework APIs

Ownership evidence

Creating 3D Shapes/Views/ShapesView.swift:12 — representative stored state or the nearest verified lifecycle anchor.

struct ShapesView: View {
    // ...
}

Ownership here is deliberately narrow: @Environment and weak references are shared links, initialized @State or stored services are lifecycle ownership, and a RealityView content closure owns additions to its entity graph without making the SwiftUI view a reference-type owner.

Class and protocol design

The source defines no local substitution protocol in the reviewed boundary. Its protocol use is framework-facing (App, View, RealityKit/ARKit protocols, or platform adapters), so this document does not label the whole app protocol-oriented.

Access control

No reviewed declaration uses fileprivate, private(set), public, open; unmodified Swift declarations are internal.

Reference code

Creating 3D Shapes/App/EntryPoint.swift:11 — representative visibility boundary.

struct EntryPoint: App {
    // ...
}

Logic ownership and placement

Design patterns

Naming conventions

• Role suffixes are evidence, not decoration: View: ShapesView.
• Protocols: no app-defined protocol in the reviewed source.
• Commands use verb-led methods: addGeometryShapes.
• Files generally match their primary type; Views, Models, Managers, Providers, Components, Systems, and Packages folders describe architectural roles where present.

Architecture takeaways

• Treat EntryPoint as the owner of scene declarations, not as the owner of every RealityKit entity created later.
• Keep view-local interaction in SwiftUI, but move provider sessions, playback resources, shared game state, or transport state into a stable owner when their lifetime exceeds one render pass.
• The compact source does not justify adding repository, coordinator, or protocol layers beyond the model, provider, or view boundary the sample actually declares.

Source map

• Official Apple documentation