StudyTrack
Android app helping students track study sessions and manage tasks.
- My role
- Academic Team
- Timeframe
- 2025
- Project status
- Academic deliverable
The context.
A native Android application designed to help students track study sessions, manage academic tasks, and build consistent study habits. Built with modern Android architecture components — MVVM pattern, Material3 design system, Jetpack Compose for declarative UI, Navigation Compose for multi-screen flows, and Room for offline data persistence.
Collaborative mobile development module project where the team followed Agile sprints, peer code reviews, and test-driven development practices.
My contribution.
A native Android study companion for recording study sessions, managing academic tasks and building consistent study habits.
- Study-session tracking and task-management flows for students
- Multi-screen navigation for the core mobile experience
- Offline-friendly local persistence for study and task records
The implementation.
A Kotlin team project using Jetpack Compose, Material3, Navigation Compose, Room and an MVVM structure.
- Contributed to declarative Compose UI and Material3 components within the shared Android implementation
- Worked with the team’s Room entities and DAO layers for local persistence
- Delivered within sprint-style collaboration, peer review and test-driven development practices
Kotlin · Jetpack Compose · Material3 · Navigation Compose · Room
Project identity.
The project mark identifies the work. The implementation evidence is described above and linked where available.
What was delivered.
- Contributed to native Android logic using Kotlin with modern Jetpack Compose and Material3 UI toolkits
- Worked within a team implementation targeting Android SDK API 34 and an MVVM structure
- Contributed to modular navigation flows using Navigation Compose for the multi-screen architecture
- Worked with Room-based local persistence through the team’s entity models and DAO layers
What I took forward.
- Jetpack Compose's state management requires a different mental model than XML layouts
- Collaborative Git workflows with feature branches prevent merge conflicts in team projects
Want to talk about this work?
A question about the approach, a role or a project of your own.
Discuss this project