How xelor-dev/moviles_proyectofinal works
Project type and purpose
• This is a Unity-based Android game (client-side application) that uses Firebase (Authentication, Realtime Database) and DOTween for animations, plus Unity’s Input System and URP for rendering.
File structure
• Top-level Unity folders:
• Assets/ — all game assets, scenes, scripts, prefabs, scriptable objects
• Packages/ — Unity package manifest
• ProjectSettings/ — Unity project settings and build configuration
• Keystore/ — Android signing key
• .utmp/ — temporary CMake build output (native plugin build)
• Within Assets/:
• ProjectAssets/ — organized art, audio, models, prefabs, scenes, UI sprites
• Plugins/ — third-party libraries (DOTween, Firebase AARs)
• Scriptable Objects/ — SO data for configs (AudioConfig, RobotNeeds, etc.)
• Scripts/ — C# code organized by feature:
· Firebase/ — AuthenticationManager.cs, DatabaseManager.cs
· Managers/ — GameSceneLoader, AudioManager, ResourceManager, UI managers
· Minigames/ — modules for ExteriorRunner, Punteria, RobotWalk
· SaveSystem/, UtilityScripts/, RepairSystem.cs, TouchInputHandler.cs
• Settings/ — render pipeline assets, volume profiles
• StreamingAssets/ — google-services-desktop.json
• Configuration files:
• Packages/manifest.json & packages-lock.json — package dependencies
• ProjectSettings/*.asset / .json — Unity build, quality, input, graphics, etc.
• Keystore/LastHopeBot.keystore — Android keystore for signing
README
• “assignment final project using Unity, this game is for android.”
• No further architectural detail, so infer architecture from file structure and Firebase usage.