How imantihero/temp works
1. This is a Unity-based XR application, not a traditional web/backend repo. The runtime target is Android/Meta Quest-style headset deployment, with most behavior driven by scene assets, prefabs, and a small amount of C# glue code.
2. The main app entry point appears to be the Unity scene in Assets/Scene/Visual_wegovy.unity. A second scene in Assets/UI_Assets/Assets/Scenes/SampleScene.unity looks like a UI/package sample or a local testbed rather than the primary experience.
3. The XR platform layer is configured through Assets/XR, Assets/Oculus, and Assets/MetaXR, with OpenXR as the loader (Assets/XR/Loaders/OpenXRLoader.asset). These settings define the headset/runtime boundary: device tracking, input, and rendering are handled by Unity’s XR stack plus Meta/Oculus project configuration.
4. Interaction and hand/controller input are likely mediated by the imported Interaction SDK prefab at Assets/InteractionSDK/ComprehensiveInteraction.prefab. This is the main boundary between device input and in-scene interactive UI/content.
5. The only clearly custom runtime script in the root assets is Assets/Script/UiCameraFollower.cs, which likely keeps a UI element positioned relative to the XR camera. That suggests a diegetic or head-locked UI layer rather than a flat desktop canvas.
6. The bulk of the application-specific UI logic lives under Assets/UI_Assets/Assets/Scripts: ExperimentManager, EvaluationController, VASController, SimpleNextButton, and SliderTextUpdater. These names indicate a guided experiment or questionnaire flow, probably including a visual analog scale (VAS) rating interaction and step-by-step progression.
7. The UI subsystem is packaged separately from the main scene content. Assets/UI_Assets/Assets/Prefabs/VAS_UI/Canvas.prefab is the reusable UI container, while the scripts above orchestrate panel state, button navigation, and slider-to-text synchronization. VASPanelManager(deprecated).cs suggests this UI flow was refactored and the old panel manager is retained only for compatibility.
8. Text and labels are rendered with TextMesh Pro, which is imported twice: once at the repository level and once inside the UI_Assets package. This is an imported presentation dependency, not core app logic, but it materially affects how UI text, fonts, and styling are authored.
9. Rendering and visual presentation are configured through URP assets in Assets/UI_Assets/Assets/Settings and project-wide graphics settings in ProjectSettings. The repository also includes a LUT asset (Assets/LUT/blue_food_filter.xcf), hinting at visual filtering or color-processing assets used by the experience.
10. Android packaging is customized via Assets/Plugins/Android/AndroidManifest.xml, while the generated Burst debug folders at the root are build artifacts and not part of the shipped architecture. The presence of these artifacts confirms an Android-targeted Unity build pipeline.
11. Resource assets in Assets/Resources provide global configuration objects such as InputActions.asset, OVRBuildConfig.asset, OculusRuntimeSettings.asset, and ImmersiveDebuggerSettings.asset. These are the app’s shared configuration boundary: input mappings, Oculus/Meta build behavior, and debug/runtime settings.
12. Overall data flow is: XR hardware input and camera pose enter through OpenXR/Meta XR + Interaction SDK, scene objects and UI prefabs consume that state, the experiment controllers manage progression and VAS input, and TextMesh Pro/URP handle presentation. There is no obvious external service backend; the app appears self-contained inside the Unity runtime.
Main entry points: Visual_wegovy.unity Main scene · Canvas.prefab VAS canvas · XRGeneralSettingsPerBuildTarget.asset XR settings · VASController.cs VAS input
Components 20
Runtime
Primary Unity XR experience and headset-facing execution path.
- Main scene · Primary app entry point for the XR experience.
Assets/Scene/Visual_wegovy.unity - UI follower · Positions UI relative to the XR camera.
Assets/Script/UiCameraFollower.cs
UI Package
Reusable experiment and questionnaire UI flow.
- Sample scene · Secondary UI/sample testbed rather than the core experience.
Assets/UI_Assets/Assets/Scenes/SampleScene.unity - VAS canvas · Reusable UI container for the VAS workflow.
Assets/UI_Assets/Assets/Prefabs/VAS_UI/Canvas.prefab - Experiment · Coordinates guided progression through the study flow.
Assets/UI_Assets/Assets/Scripts/ExperimentManager.cs - Evaluation · Handles evaluation state and user response collection.
Assets/UI_Assets/Assets/Scripts/EvaluationController.cs - VAS input · Manages the visual analog scale interaction.
Assets/UI_Assets/Assets/Scripts/VASController.cs - Next button · Advances the questionnaire or experiment step flow.
Assets/UI_Assets/Assets/Scripts/SimpleNextButton.cs - Slider text · Keeps slider values synchronized with displayed text.
Assets/UI_Assets/Assets/Scripts/SliderTextUpdater.cs - Legacy panel · Old VAS panel manager retained for compatibility.
Assets/UI_Assets/Assets/Scripts/VASPanelManager(deprecated).cs
Platform
XR, Android, and Meta/Oculus project configuration boundary.
- OpenXR loader · Configures the headset runtime loader for device tracking and input.
Assets/XR/Loaders/OpenXRLoader.asset - XR settings · OpenXR editor/package settings and per-build XR setup.
Assets/XR/XRGeneralSettingsPerBuildTarget.asset - Meta XR · Meta XR project settings for Quest-style deployment.
Assets/MetaXR/MetaXRProjectSettings.asset - Oculus config · Oculus project setup and runtime configuration assets.
Assets/Oculus/OculusProjectConfig.asset - Android manifest · Custom Android packaging and application manifest.
Assets/Plugins/Android/AndroidManifest.xml - Shared resources · Global runtime assets for input, build, debugger, and overlay settings.
Assets/Resources
Presentation
Text and rendering dependencies used across the app.
- TextMesh Pro · Text, font, and shader assets used for UI presentation.
Assets/TextMesh Pro - URP settings · Universal Render Pipeline assets for mobile and sample rendering.
Assets/UI_Assets/Assets/Settings - Color LUT · Color filter or grading asset used in the experience.
Assets/LUT/blue_food_filter.xcf
Assets
Reusable scene and prefab assets that drive interaction.
- Interaction SDK · Imported interaction boundary for hands, controllers, and XR UI.
Assets/InteractionSDK/ComprehensiveInteraction.prefab
Connections 24
- Main scene → Interaction SDK: uses · Main scene consumes the imported interaction prefab for XR input and UI interaction.
- Main scene → VAS canvas: hosts · Primary scene includes the reusable experiment UI canvas.
- Main scene → UI follower: follows · Scene UI is positioned relative to the headset camera.
- Main scene → TextMesh Pro: renders text · In-scene labels and questionnaire text use TextMesh Pro assets.
- Main scene → Color LUT: applies · Visual presentation can use a LUT-based color filter.
- VAS canvas → Experiment: orchestrated by · The canvas is driven by the main experiment flow controller.
- VAS canvas → VAS input: contains · VAS UI includes the rating interaction controller.
- VAS canvas → Slider text: contains · Slider labels are updated by the text sync helper.
- VAS canvas → Next button: contains · Navigation control advances the step sequence.
- Experiment → Evaluation: coordinates · Experiment flow hands off to evaluation logic.
- Evaluation → VAS input: collects · Evaluation logic receives VAS responses.
- VAS input → Slider text: updates · VAS changes are reflected in displayed slider text.
- Next button → Experiment: advances · Next action moves the experiment to the following stage.
- Legacy panel → VAS input: replaced by · Deprecated panel manager was superseded by the current VAS controller flow.
- OpenXR loader → XR settings: configured by · OpenXR loader is part of the wider XR build configuration.
- XR settings → Meta XR: aligned with · XR runtime settings are paired with Meta XR project configuration.
- XR settings → Oculus config: aligned with · XR runtime settings are paired with Oculus project configuration.
- Shared resources → OpenXR loader: supplies · Shared input and runtime assets support the XR loader boundary.
- Shared resources → Interaction SDK: feeds input · Input action assets back the interaction SDK layer.
- Android manifest → XR settings: packages for · Android packaging is tuned for the XR deployment target.
- URP settings → Main scene: profiles · Rendering profiles shape the primary scene presentation.
- URP settings → Sample scene: profiles · Sample scene uses the package's rendering settings.
- TextMesh Pro → VAS canvas: styles · TextMesh Pro underpins the reusable UI canvas text elements.
- Sample scene → TextMesh Pro: uses · Sample UI scene demonstrates TextMesh Pro presentation assets.