Apple & iOS
AuraScore 77/100

visionOS Immersive STEM Simulation Technical Assessment Report

Assess the performance, RealityKit rendering, and spatial ergonomics of visionOS STEM lab simulations for higher education.

Use this template to evaluate a visionOS spatial computing application built for university physics, biology, or engineering lab simulations. It ensures performance budgets, gesture interactions, and multi-user spatial audio meet academic goals.

Template

Role: Senior Spatial Computing Engineer & Apple Developer Relations Specialist for Higher Education.

Context

  • Academic Lab / Faculty: {{university_lab}}
  • Simulation Topic: {{simulation_topic}}
  • Target visionOS Version: {{target_visionos_version}}
  • Spatial Input Modalities: {{spatial_input_types}}
  • Performance Target: {{frame_rate_target}}
  • Rendering Engine & Tooling: {{rendering_pipeline}}

Task

Author a technical assessment report detailing the runtime feasibility, RealityKit entity architecture, and spatial interaction safety of a visionOS simulation for {{simulation_topic}} at {{university_lab}}.

Method

  1. Review the proposed 3D assets and particle systems against {{rendering_pipeline}} shader limits and vertex count budgets.
  2. Evaluate spatial anchoring techniques (World Tracking vs. Image Anchoring vs. Tabletop) for academic laboratory environments.
  3. Analyze {{spatial_input_types}} (e.g., eye gaze + pinch, custom gestures, game controllers) to prevent user fatigue during 45-minute lab sessions.
  4. Measure memory footprint and dynamic thermal management needed to maintain {{frame_rate_target}} without dropped frames.
  5. Assess multi-user SharePlay synchronization for collaborative student experiments using Spatial Personas.
  6. Audit Spatial Audio configuration to ensure accurate directional acoustic feedback for interactive 3D science apparatus.
  7. Produce a definitive list of technical roadblocks with specific RealityKit and SwiftUI code-level remedies.

Constraints

  • MUST evaluate framerate and thermal throttling risks against the target {{frame_rate_target}}.
  • MUST NOT recommend custom gestural paradigms that override standard visionOS system gestures.
  • Must provide concrete USDZ asset optimization guidelines.
  • Must restrict report length to under 1500 words.

Output format

Generate a structured engineering report containing:

  1. Executive Simulation Assessment (key risks and viability score)
  2. RealityKit Scene Hierarchy & Entity-Component-System (ECS) Recommendation
  3. Ergonomic and Input Latency Analysis (evaluating {{spatial_input_types}})
  4. Framerate & Thermal Optimization Protocol (step-by-step performance plan)

Self-review

  • Ensure the target {{frame_rate_target}} is explicitly validated against visionOS display refresh rates.
  • Confirm that {{rendering_pipeline}} specifics (e.g., RealityKit vs. Unity PolySpatial) are accurately handled.
  • Check that SharePlay or collaborative student lab interactions are addressed.
AuraScore breakdown
77/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering8/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-apple
education-research
visionos
realitykit
spatial-computing