How yeahhe365/rubik-cube-simulator works
This is a native Android Rubik’s Cube simulator. The documented user-facing capability is interacting with a simulated cube; the tree also shows a local solve-record persistence layer. Source excerpts are limited to build configuration, so runtime connections—especially between UI, cube state, and persistence—are not verified and are shown only as dashed links.
Main entry points: SolveDao.kt Solve DAO · MainActivity.kt Main activity · RubikCubeSimulator.kt Cube simulator UI · RubikViewModel.kt Cube view model
Components 11
Android interface
- Main activity
app/src/main/java/com/example/MainActivity.kt - Cube simulator UI
app/src/main/java/com/example/ui/RubikCubeSimulator.kt - Cube view model
app/src/main/java/com/example/ui/RubikViewModel.kt
Cube simulation
- Cube state
app/src/main/java/com/example/model/RubikCube.kt - Cube faces
app/src/main/java/com/example/model/Face.kt - Cube colors
app/src/main/java/com/example/model/CubeColor.kt
Solve storage
- Solve repository
app/src/main/java/com/example/database/SolveRepository.kt - Solve DAO
app/src/main/java/com/example/database/SolveDao.kt - Solve record
app/src/main/java/com/example/database/SolveRecord.kt - App database
app/src/main/java/com/example/database/AppDatabase.kt
Other components
- User
Connections 7
- User → Main activity: opens app
- Main activity → Cube simulator UI: shows UI
- Cube simulator UI → Cube view model: handles interaction
- Cube view model → Cube state: updates state
- Solve repository → Solve DAO: uses
- Solve DAO → App database: accesses
- Solve DAO → Solve record: maps records