\section{Conclusion}

The goal of \textit{Study Sprint} was to create a focused mobile application that helps students organise academic work and move more easily into structured study sessions. The final product addresses this goal by combining subjects, assignments, tasks, timed focus sessions, breaks, progress tracking, reminders, and persistence into one connected workflow.

\vspace{2mm}

The project shows that the value of the application lies mainly in how these parts work together. A planner alone would not solve the problem of starting focused work, and a timer alone would not help the user decide what to study. By linking study sessions directly to tasks, the app makes the transition from planning to action more concrete. This supports the original product vision, where simplicity, low friction, reliability, and realistic scope were more important than building a broad productivity platform.

\vspace{2mm}

During development, the application also became more coherent through several important refinements. The screen structure was aligned more closely with the hierarchy of \textit{Subject $\rightarrow$ Assignment $\rightarrow$ Task}, the timer flow was implemented around the task workflow as originally intended, and session reliability was improved through more consistent lifecycle handling. The final design also supports several usability principles, including visible system status, familiar student-oriented concepts, consistent interaction patterns, and a low-friction default path into study sessions.

\vspace{2mm}

There are still limitations. The project remained intentionally narrow in scope, and some behaviour, especially around timer interaction, onboarding, notifications, and break handling, depended heavily on manual verification. The product is also still best understood as a proof-of-concept rather than a production service, especially because it depends on Supabase free-tier limits and does not yet include a larger automated testing strategy, advanced analytics, calendar integration, or richer cross-device behaviour. In addition, the lack of formal time sheets and a formal ticket-tracking system weakened the precision of the process documentation, even though the group could still document work through the report, source control, communication, meetings, and development history.

\vspace{2mm}

Overall, \textit{Study Sprint} can be considered a successful result within the constraints of the project. It delivers a working and coherent study-support application that reflects the original vision more clearly than the early prototype. The final result is not the largest possible productivity app, but it is a focused solution that connects planning, studying, breaks, and progress in a way that is useful for the intended student user.
