How splendo/kaluga works
Main Components
a. Core Architecture Layer:
• Base Module (foundation layer)
• Architecture Module (MVVM implementation)
• Resources Module
• Logging Module
b. Feature Modules Layer:
• UI Components (Alerts, HUD, Keyboard)
• Device Features (Bluetooth, Location, Media)
• System Services (Network, Battery)
• Permissions Management
c. Testing Infrastructure Layer:
• Test Utils Modules
• Mock Implementations
Relationships and Flow
• Platform-specific implementations (Android/iOS) branching from common modules
• Integration points with external systems (Firebase, SQLDelight)
• Permission management flow
• MVVM architecture pattern implementation
Detailed Components
a. Base Layer:
[Base Module]
• Threading
• Flow Management
• Localization
• Core Utilities
b. Architecture Layer:
[Architecture Module]
• MVVM Implementation
• Lifecycle Management
• Navigation
• State Management
c. Feature Modules:
[Feature Modules]
• UI Components
• Alerts
• HUD
• Keyboard
• Device Features
• Bluetooth
• Location
• Media
• System Services
• Network
• Battery
Implementation Details
• Coroutines and Flow usage throughout the system
• Platform-specific implementations using Kotlin Multiplatform
• Integration with Compose and SwiftUI
• Test utilities and mock implementations
• Permission management system
Notes
Annotations for:
• Kotlin Multiplatform specific features
• Platform-specific considerations
• Integration points with native UI frameworks
• Testing approach
• Permission handling
Remember to emphasize:
• The cold streams approach using Flow
• Cross-platform nature of the implementation
• Modular architecture allowing selective module usage
• Integration with native UI frameworks
• Comprehensive testing infrastructure
This system design will help developers understand both the high-level architecture and the detailed implementation patterns used throughout Kaluga.