How kuneosu/mintoners works
Main Components
a) Application Layer:
• MainActivity as the entry point
• SplashActivity for initial loading
• InstructionActivity for user guidance
• MatchActivity for match management
b) UI Layer (Fragment Structure):
• Home Module (HomeFragment)
• Match Module (MatchInfoFragment, MatchPlayerFragment, MatchGameFragment, MatchMainFragment)
• Settings Module (SettingsFragment)
• Notice Module (NoticeFragment)
c) Data Layer:
• Local Storage (Room Database)
• AppDatabase
• MainDao
• Remote Storage
• GitHub API Service (for notices)
• RetrofitClient
d) Repository Layer:
• HomeRepository
• MatchRepository
e) ViewModel Layer:
• HomeViewModel
• MatchViewModel
Relationships and Data Flow
• User interaction flow through Activities and Fragments
• Data flow between ViewModels and Repositories
• Database interactions
• API calls to GitHub for notices
Specific Implementation Details
• DI implementation using Hilt
• Navigation components
• Custom Views and Dialogs
• Data Models (Match, Player, Game, Notice)
Architecture Pattern
MVVM architecture:
• View Layer (Activities/Fragments)
• ViewModel Layer
• Model Layer (Repositories/Data Sources)
External Dependencies
Integration with:
• Firebase Remote Config
• GitHub API
• Material Design Components
[UI Layer (Activities/Fragments)]
• ↕
[ViewModel Layer]
• ↕
[Repository Layer]
• ↕
[Data Layer (Local/Remote)]
Key Considerations: