\section{Individual Reports}
\subsection{Christopher Sanden}

My individual contribution to \textit{Study Sprint} covered several central parts of the project, but the largest part of my work was connected to the timer, session flow, onboarding, and final delivery preparation. The commit history attributes 44 commits to me, including the first timer implementation, later task-flow integration, dashboard and session improvements, break-cycle logic, onboarding refinements, signup-confirmation deployment, test updates, and Android delivery preparation. The most relevant work is supported by the timer work notes from 21 April to 5 May and commits such as \texttt{d50301c}, \texttt{666bdc1}, \texttt{c74062c}, \texttt{b437643}, \texttt{907fa18}, \texttt{245b6db}, \texttt{2bb2ac6}, \texttt{9bb3bb1}, and \texttt{419463e}.

\vspace{2mm}

My first major contribution was creating the original timer feature. In commit \texttt{d50301c}, I added the first functional timer screen with duration selection, start behaviour, running timer state, and animated visual feedback. In the following iterations, I developed the timer into a more complete study-session interaction. This included countdown behaviour, measured layout handling, duration locking while a session was running, a deliberate hold-to-cancel flow, and cleanup of the internal timer structure. The timer eventually relied on several separate kinds of state, including selected duration, running state, countdown text, layout height, progress animation, and cancellation state. Separating these concerns was important because the timer later had to survive routing changes, cancellation, recovery, and integration with persistent session data.

\vspace{2mm}

A key part of this work was making the timer maintainable enough to become a core product feature rather than a fragile prototype. In commit \texttt{666bdc1}, I refactored the timer code by extracting repeated cleanup logic, grouping refs by responsibility, and making the render structure match the visible screen layers more closely. This was especially important because the timer used intervals, timeouts, animation refs, and cancellation flags. Keeping those responsibilities clear made the later integration work safer and easier to reason about.

\vspace{2mm}

The most important product-level change I made was moving the timer into the actual task workflow. In commit \texttt{c74062c}, I moved the timer from the tab navigator into the task stack and made it open from a selected task. The timer could then receive a task id, load the matching task from Supabase, display task information during the sprint, and preserve an active sprint locally through an end time. This changed the timer from a generic utility into a study-session feature tied directly to the user's planned work, which better matched the product vision.

\vspace{2mm}

I also extended the timer into a more durable session model. In commit \texttt{b437643}, I connected active local sprint state to database-backed sprint sessions and added task-level study-time tracking. This meant that completed, expired, or cancelled sessions could contribute elapsed time back to the relevant task instead of only changing temporary UI state. I also handled failure cases around session creation, finalisation, cancellation, and restore behaviour so the local timer state and stored session history would not drift apart.

\vspace{2mm}

My work also affected the dashboard and progress experience. I added support for reopening active sprints from the dashboard, showing remaining session time, displaying upcoming deadline tasks with subject and assignment context, and marking tasks as completed from dashboard cards. I also fixed a dashboard issue where upcoming tasks disappeared whenever an active sprint existed. These changes made the dashboard more useful as a daily study overview instead of only being a static landing page.

\vspace{2mm}

Later in the project, I worked on the focus-and-break cycle. I introduced shared session defaults in \texttt{lib/sessionDefaults.ts} so focus duration, short breaks, long breaks, and long-break frequency could be reused consistently across the timer, task details, and dashboard. I also implemented a local study-cycle model so the app could decide whether the next break should be short or long based on the current continuous study run rather than unrelated historical sessions. This made the session flow closer to a real study rhythm: focus, break, continue the same task, or return to the dashboard.

\vspace{2mm}

As the session flow became more connected to the rest of the app, I added a shared lifecycle helper in \texttt{lib/sessionLifecycle.ts}. This centralised how active sessions are finalised when they expire, are replaced, or are cleared from other screens. This was one of my more important reliability contributions because it reduced duplicated logic across the timer, dashboard, task details, and setup flow, and lowered the risk of the UI and database recording different versions of the same session.

\vspace{2mm}

I also contributed to the first-time-user and account-confirmation flow. In commit \texttt{907fa18}, I added a guided setup route that helps new users create their first subject, assignment, and task before starting a sprint. Later, in commit \texttt{9bb3bb1}, I added shared setup-completion logic in \texttt{lib/setupStatus.ts} so incomplete users are routed into setup more consistently. I also changed the first setup sprint into a short demo timer, making the first interaction easier to test and understand.

\vspace{2mm}

Outside the app itself, I improved the signup confirmation loop. I added a small static confirmation page under \texttt{deploy/signup-confirmation}, served through \texttt{nginx} with Docker Compose and hosted on my VPS behind the existing reverse-proxy setup. I also corrected the Caddy routing target so the page resolved correctly, and customised the Supabase confirmation email into a cleaner HTML email while keeping the required confirmation-link placeholder. This made account creation feel more complete and presentable from signup through email confirmation.

\vspace{2mm}

Toward the end of the project, I contributed to verification and delivery preparation. I used TypeScript checks, linting, manual runtime testing, and database inspection during timer and session work, because interaction-heavy behaviour could not be fully verified by static checks alone. I also updated the test setup and several test files in commit \texttt{419463e} so they matched the newer logic across auth, subject, assignment, and task flows. Finally, I adjusted the Android package name in \texttt{app.json} to match Google Play Console expectations and added the APK artifact for delivery.

\vspace{2mm}

Overall, my contribution was broad, but it was tied together by one main goal: making the app feel like a coherent study tool rather than a set of separate screens. I worked on the timer, task integration, session persistence, dashboard visibility, break-cycle behaviour, onboarding, signup confirmation, testing, and Android delivery. Strategically, this strengthened the parts of the project most closely connected to the product vision: helping users move from planning study work to actually starting and tracking focused study sessions.
