How unity-technologies/arfoundation-samples works
Project type and purpose
• This is an open-source Unity sample application (“AR Foundation Samples”) that demonstrates AR Foundation 6.0 features across multiple AR scenarios (plane detection, image/object/face/body tracking, meshing, occlusion, environment probes, multi-device collaboration, etc.).
• It is not a classic client–server or full-stack web app; it is a single-player AR demo built on top of Unity’s engine, AR Foundation package, and platform-specific XR plug-ins.
File structure
• Top level:
• Assets/ – All Unity assets (Scenes, Scripts, Prefabs, Materials, Shaders, Fonts, etc.)
• Packages/ – package manifest declaring dependencies: AR Foundation, ARCore, ARKit, OpenXR, URP, TextMeshPro
• ProjectSettings/ – Unity project configuration (graphics, input, XR settings, URP settings)
• .github/, LICENSE.md, CONTRIBUTING.md – repo meta, CI/issue templates
• Under Assets/:
• Scenes/ – dozens of minimal sample scenes for each AR feature
• Scripts/Runtime/ – C# MonoBehaviours using AR Foundation APIs (ARPlaneManager, ARRaycastManager, ARImageTrackingManager, ARFaceManager, ARMeshManager, AROcclusionManager, AREnvironmentProbeManager, Multipeer connectivity code, etc.)
• Scripts/Editor/ – custom inspectors and asset editors for event assets, UI
• Prefabs/, Materials/, Shaders/, Fonts/, InputActions/, etc. – reusable assets referenced by scenes and scripts
• Settings/ – build profiles (Meta Quest, Visual Scripting)
• Samples/ – sample content for XR Interaction Toolkit
• Key config files:
• Packages/manifest.json – declares AR Foundation & XR plug-in dependencies
• ProjectSettings/XRSettings.asset – XR Loader configuration (ARKitLoader, ARCoreLoader, OpenXRLoader, SimulationLoader)
• URP assets – Universal Render Pipeline settings and renderers
README for additional insights
• Confirms AR Foundation 6.0 usage, Unity 2023.2+ compatibility
• Lists supported packages (AR Foundation, ARCore XR, ARKit XR, OpenXR)
• Describes each sample scene’s purpose and the associated key scripts
Be very detailed
• Essential Managers in ARFoundation, key XR Subsystem names, and the Loader/Plug-in mapping
• Separate runtime vs. editor components for clarity
• Don’t overthink: break the project into its main functional slices (Scenes/UI → ARFoundation → XR Subsystem → Plug-in → Native SDK → Hardware)