How kimweking-bit/scholar-dash works
The tree suggests a small Android app with an entry activity, separate login and registration screens, and a dashboard. No README or runtime source excerpts were provided, so their routing, authentication behavior, data sources, and external integrations cannot be established; the graph avoids implying connections between those screens. The theme files are shown as a UI layer, not as a separate product capability.
Main entry points: MainActivity.kt Main activity
Components 6
App entry
- Main activity
app/src/main/java/com/example/app/MainActivity.kt
Account screens
- Login screen
app/src/main/java/com/example/app/login.kt - Registration screen
app/src/main/java/com/example/app/Register.kt
Dashboard UI
- Dashboard
app/src/main/java/com/example/app/dashboard.kt
Presentation
- UI theme
app/src/main/java/com/example/app/ui/theme/Theme.kt
Other components
- App user
Connections 1
- App user → Main activity: opens app