How hadao12/count-doku works
Main Architecture Components
a) Presentation Layer (Top)
• Screens (Splash, Level, Puzzle, Pass)
• Jetpack Compose UI components
• ViewModels for each screen
• UI State, Events, and Actions flow
b) Domain Layer (Middle)
• UseCase components (e.g., GenerateQuestionsUseCase)
• Domain models (Puzzle, GameLevel)
c) Data Layer (Bottom)
• Local Database (SQLite)
• DAOs (GameMetaDataDao, LevelDao)
• PlayerProgressManager for preferences
Component Relationships
• ViewModels → UseCases (downward)
• UseCases → Repositories (downward)
• DAOs → Database (bidirectional)
• Database → Domain Models (upward)
b) Dependency Injection:
• AppModule as a central component
Specific Components
Frontend:
[Presentation Layer]
• Screens (Compose UI)
• SplashScreen
• LevelScreen
• PuzzleScreen
• PassScreen
• ViewModels
• LevelViewModel
• PuzzleViewModel
• PassViewModel
• UI Components
• Custom Components
• CustomProgressBar
• PuzzleButton
• PuzzleTopAppBar
Backend:
[Domain Layer]
• UseCases
• GenerateQuestionsUseCase
• Models
• GameLevel
• Puzzle
[Data Layer]
• Local Database
• DatabaseHelper
• DAOs
• GameMetaDataDao
• LevelDao
• Preferences
• PlayerProgressManager
Additional Elements
Include:
• Version information
• Technology stack badges (Kotlin, Jetpack Compose, SQLite)
• Clear data flow indicators
• State management flow