Sample CodevisionOSReviewed 2026-07-21View on Apple Developer

Displaying a 3D environment through a portal

At a glance

Item Summary
Purpose Implement a portal window that displays a 3D environment and simulates entering a portal by using RealityKit.
App architecture EntryPoint composes WindowGroup + ImmersiveSpace around UIPortalView; AppModel owns interaction while RealityView manages the entity graph.
Main patterns SwiftUI scene composition, SwiftUI–RealityKit bridge, Explicit immersive-space lifecycle, Observable state owner
Project style Code-light sample with 6 scanned Swift file(s) and 283 Swift line(s); resources and generated assets are excluded from those counts.

Project structure

Source bundle/
└── RealityKit-UIPortal/
    └── RealityKit-UIPortal/
        ├── App/
        │   ├── EntryPoint.swift  # EntryPoint
        │   └── AppModel.swift  # AppModel, ImmersiveSpaceState
        ├── Views/
        │   ├── UIPortalView.swift  # UIPortalView
        │   ├── ImmersiveView.swift  # ImmersiveView
        │   └── ToggleImmersiveSpace.swift  # ToggleImmersiveSpaceButton
        └── Extensions/
            └── EnvironmentResource.swift

Structure observations

  • The runtime boundary is WindowGroup + ImmersiveSpace; 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

Reference code

RealityKit-UIPortal/RealityKit-UIPortal/App/EntryPoint.swift:11 — the app or executable entry declares the outer scene lifecycle.

struct EntryPoint: App {
    // ...
}

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

Ownership evidence

RealityKit-UIPortal/RealityKit-UIPortal/App/EntryPoint.swift:12 — representative stored state or the nearest verified lifecycle anchor.

    @State private var appModel = AppModel()
Owner Object or state Relationship Mutation authority
EntryPoint AppModel as appModel creates and retains Only the declaring scope writes
UIPortalView AppModel as appModel receives a shared/non-owning reference The upstream owner controls lifetime; this scope may invoke its mutable API
UIPortalView Entity as root creates and retains Only the declaring scope writes
UIPortalView ModelEntity as portalPlane creates and retains Only the declaring scope writes

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

Type Responsibility Depends on or conforms to
EntryPoint (RealityKit-UIPortal/RealityKit-UIPortal/App/EntryPoint.swift:11) Declares app scenes and top-level dependency lifetime. App
UIPortalView (RealityKit-UIPortal/RealityKit-UIPortal/Views/UIPortalView.swift:11) Presents UI and forwards gestures or lifecycle events. View
AppModel (RealityKit-UIPortal/RealityKit-UIPortal/App/AppModel.swift:13) Owns observable feature state and domain transitions. Concrete framework collaborators
ImmersiveView (RealityKit-UIPortal/RealityKit-UIPortal/Views/ImmersiveView.swift:12) Presents UI and forwards gestures or lifecycle events. View

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

Symbol Access Verified effect Likely rationale
@State private var appModel = AppModel() (RealityKit-UIPortal/RealityKit-UIPortal/App/EntryPoint.swift:12) private Use is restricted to the declaration and same-file extensions permitted by Swift. Inference: Hide implementation details and lifecycle-sensitive state.

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

Reference code

RealityKit-UIPortal/RealityKit-UIPortal/App/EntryPoint.swift:12 — representative visibility boundary.

    @State private var appModel = AppModel()

Logic ownership and placement

Logic Owning type or file Placement rationale
Scene declaration and dependency lifetime EntryPoint The App/entry boundary determines window, volume, and immersive-space lifetime.
Presentation, attachments, and gestures UIPortalView SwiftUI view code forwards user intent and RealityView lifecycle events.
Shared feature state and commands AppModel A role-named owner prevents sibling views from duplicating transitions.

Design patterns

Pattern Source evidence Purpose or tradeoff
SwiftUI scene composition RealityKit-UIPortal/RealityKit-UIPortal/App/EntryPoint.swift:11 Keeps windows, volumes, and immersive-space lifecycle visible at the app boundary.
SwiftUI–RealityKit bridge RealityKit-UIPortal/RealityKit-UIPortal/Views/UIPortalView.swift:38 Builds and updates a RealityKit entity graph from SwiftUI lifecycle closures.
Explicit immersive-space lifecycle RealityKit-UIPortal/RealityKit-UIPortal/App/EntryPoint.swift:22 Makes immersive presentation a scene transition rather than hidden global state.
Observable state owner RealityKit-UIPortal/RealityKit-UIPortal/App/AppModel.swift:13 Shares feature state across multiple views without moving framework resources into view values.

Naming conventions

  • Role suffixes are evidence, not decoration: Model: AppModel; View: ImmersiveView, UIPortalView.
  • Protocols: no app-defined protocol in the reviewed source.
  • Commands use verb-led methods: createPortal, updatePortalSize, createEnvironment.
  • 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.
  • Model immersive-space open, transition, and close states explicitly so windows and immersive content cannot drift apart.
  • 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

Source file Relevant symbols
RealityKit-UIPortal/RealityKit-UIPortal/App/EntryPoint.swift:11 EntryPoint
RealityKit-UIPortal/RealityKit-UIPortal/Views/UIPortalView.swift:11 UIPortalView
RealityKit-UIPortal/RealityKit-UIPortal/App/AppModel.swift:13 AppModel, ImmersiveSpaceState
RealityKit-UIPortal/RealityKit-UIPortal/Views/ImmersiveView.swift:12 ImmersiveView
RealityKit-UIPortal/RealityKit-UIPortal/Views/ToggleImmersiveSpace.swift:10 ToggleImmersiveSpaceButton
RealityKit-UIPortal/RealityKit-UIPortal/Extensions/EnvironmentResource.swift:1 Feature implementation