How mauznemo/smartifyos works
Project type and purpose
• Unity-based monolithic application for a DIY car infotainment GUI.
• “Assets/SmartifyOS”: reusable core framework.
• “Assets/Scripts”, “Assets/ScriptableObjects”: Miata-specific controllers and UI extensions.
File structure
• Top-level Unity directories:
– Assets/SmartifyOS (Core framework)
– Assets/Scripts (Project-specific controllers)
– Assets/ScriptableObjects (Configuration data)
– Assets/Scenes, Assets/Materials, Assets/Prefabs (Unity runtime content)
• Packages: LeanTween, Universal Blur, TextMeshPro (third-party libs).
• ProjectSettings, Packages/manifest.json: build & deployment config.
README for insights
• “Assets/SmartifyOS” is the base; “Assets/Scripts” extends it for a specific car setup.
• Supported on Linux (editor & build), partial Windows editor.
Main components & interactions
A. Unity Engine Core (Runtime)
– Scene Management (MainScene.unity)
– Render Pipeline (URP, Blur pass)
– Main Thread Dispatcher
B. Core Framework (“Assets/SmartifyOS”)
1. SystemManager & SystemEventManager
• Boots subsystems, routes events.
2. SerialCommunication Layer
• BaseSerialCommunication, BaseLiveSerialCommunication → ARDUINO boards.
3. Bluetooth Layer
• BluetoothManager, BluetoothParser → external BLE devices.
4. Audio System
• AudioManager, FilePlayer (media playback) → filesystem.
5. UI Framework
• BaseUIManager, BaseUIWindow
• Core Windows: AppList, SettingsUIWindow, PowerOffUIWindow, etc.
• UI Components: Buttons, ToggleButtons, QuickSettings entries, VolumeOverlay, StatusBar, GraphLineRenderer, ReverseCameraOverlay.
6. SaveSystem
• SaveManager, SaveData, JSON converters
7. EditorTools (design-time helpers, only relevant in Editor)
C. Project-Specific Extensions (“Assets/Scripts”)
1. Arduino Controllers
• LightController, LockController, MainController, LiveDataController
2. AnimatedObjects
• LeftDoor, RightDoor, Trunk, PopupLights, WheelAnimator
3. UI Extensions
• ActionButtonManager, ControlwheelManager, LedManager, WarningManager
• Windows: RealtimeInfoUIWindow, ReverseCameraUIWindow, StatisticsUIWindow, ZeroTo100UIWindow
• QuickSettings entries: LockToggle, ToggleInteriorLight, ToggleWave, etc.
• Settings pages: ArduinoPorts, CameraSettings, DisplaySettings, InteriorLightingSettings, NotificationsSettings, PopupsSettings.
4. ScriptableObjects for car-specific config (AudioConfigSO, ThemeData)
D. Third-Party Libraries
• LeanTween (tween animations)
• Unified-Universal-Blur (post-processing)
• TextMeshPro (text rendering)
E. External Actors
• Arduino boards (via serial)
• Bluetooth devices (phones, sensors)
• Filesystem (media files under Assets/SmartifyOS/Audio)
• Car sensors (speed, acceleration) → via LiveDataController
Relationships & Data Flows
• SystemManager initializes Core Framework at startup.
• SystemEventManager broadcasts events between subsystems.
• UI Framework listens for SystemEvents; user input → UIManager → SystemEventManager → subsystems.
• SerialCommunication ↔ Arduino Controllers (commands & telemetry).
• BluetoothManager ↔ external devices.
• AudioManager ← FilePlayer reads from filesystem.
• SaveManager persists settings changes from UI.
Architectural patterns & principles
• Event-driven architecture (SystemEventManager).
• Layered approach: Core Framework vs. Project Extensions.
• Modular subsystems (Audio, UI, Serial, Bluetooth, Save).
• Extensibility via ScriptableObjects and base classes.
Essential elements
• Component labels (e.g., “BluetoothManager”).