How shitijg118/solarsystem-ar works
Project Type and Purpose
• This is a full-stack AR mobile application built in Unity, using the Vuforia engine for marker-based AR. Its goal is to spawn a 3D solar system on a mobile device, allow users to tap planets to retrieve information, and present MCQs in the AR scene.
File Structure Analysis
• Top-level directories:
• AssetBundles – prebuilt demo bundles for testing delivery.
• Assets/AddressableAssetsData – Unity Addressables configuration.
• Assets/Editor – migration scripts, custom editor tooling.
• Assets/ExternalDependencyManager & GooglePlayPlugins – build-time plugins for Android, Google Play asset delivery, bundletool integration.
• Assets/Plugins – Android Gradle templates.
• Assets/Solar System Level – core game code: scenes, 3D models, materials, scripts, quiz logic.
• Packages & ProjectSettings – Unity package manifest (Vuforia, external libs) and project config.
• Patterns:
• Component-based Unity architecture.
• Use of Addressables/AssetBundles and Google Play Asset Delivery for runtime asset loading.
• Plugin isolation: Vuforia, LeanTouch, DOTween, TextMeshPro, Google Play core/common/assetdelivery.
README Insights
• Confirms use of Unity + Vuforia.
• Describes two runtime services: AR marker detection (Vuforia) and dynamic content (MCQ, planet info).
• No server-side components—entirely on-device, except for potential asset downloads from Google Play.
a. Main Components
• Mobile Device (Camera + Touch Input)
• Vuforia Engine (AR Marker Detection)
• Unity Runtime
– Scene Manager
– SolarSystemController (instantiates planet prefabs)
– QuizManager & UI Controllers (MCQ logic)
– Addressables/AssetBundles Loader
– Plugins (LeanTouch input, DOTween animation, TextMeshPro text rendering)
• Google Play Asset Delivery (runtime asset packs via Play Services)
• Local Resources & Prebundled Assets (Models, Materials, Scenes)
b. Relationships & Interactions
• Camera feed → Vuforia → ARCamera prefab → Unity Scene
• On marker recognized → SolarSystemController spawns planet prefabs
• User tap → LeanTouch → QuizManager opens UI (TextMeshPro)
• Quiz data & 3D models loaded via Addressables; fallback to local if offline
• At first run, Google Play Asset Delivery may fetch large asset packs
c. Architectural Patterns & Principles
• Component-based modularity (each subsystem as a Unity component)
• Separation of concerns: AR detection, content loading, UI/quiz logic
• Lazy loading of assets via Addressables/Asset Bundles for performance
• Plugin isolation: third-party code confined to Plugins/GooglePlayPlugins folders
d. Key Technologies
• Unity Engine
• Vuforia AR SDK
• Unity Addressables & AssetBundles
• Google Play Asset Delivery / Bundletool
• LeanTouch (touch input abstraction)
• DOTween (tweening/animations)
• TextMeshPro (rich text UI)