| Issue description | Severity | Task Flow | Solution(s) |
| Onboarding buttons nonfunctional | Severe | Onboard | Add functionality to the plus/minus for study session duration, break duration, long break duration, long break session count (how many sessions before a long break, Pomodoro-style), and ensure it is clear that this is part of the onboarding taskflow. |
| Break selections do not allow for those of differing ability | Severe | Break Session | A lot of the breaks revolve around things like walking, seeing, etc. but there is an easy fix: we will include a section in our onboarding flow that asks about specific preferences (avoid strenuous physical activity, avoid outdoor, avoid indoor, avoid staying still, etc.). |
| Profile has very limited display of usage information/user history | Severe | Review | Our main value prop is awareness of poor break habits, and treating that awareness as friction for the behavioral habit spark. We want clear demonstrations of the disparity in restorativeness (after break) between when they skip the break and when they take it. To do so, we will include prompts before starting the next work session just asking the user to mark if they took the suggested break, then regardless of their answer (yes or no), rate how tired they feel from 1-5. We’ll be able to display overall stats over time once we have that data available, at least 1 per condition, and will display both time worked (all time, weekly, daily) as well as the break restorativeness (delta from baseline/skip break/no break) |
| No sort option for breaks | Trivial | Choose Activity | Implement timesort filters (it’s currently the most recent break first) so that we can look through a day chronologically, from start to end. |
| Start break button should directly lead to guided activity | Moderate | Work/Break Session | Start break and select guided activity are 2 different options. Combine them into one workflow, and try to condense the selection process to improve the speed to start a break and reduce the feeling of user friction (# of buttons pressed, loading animations/overall duration). This is reminiscent of a 147 heuristic violation, as we want to help super-users pursue speed and efficiency above all. |
| Break timers are too small to see | Trivial | Work/Break Session | Our solution is twofold, since this is a larger issue from the fact that we’re trying to host a mobile app on web for Angela to be able to test our app. Firstly, we’ll increase the text size and darken text color from light gray to dark gray. Secondly |
| The current descriptions for activities on the selection screen are too lengthy. This causes visual clutter, reduces scannability, and forces users to read too much text when they just want to quickly browse and select a task. | Trivial | Choose Activity | Implement a truncated, summarized version of the activity descriptions on the main list view (e.g., a one-to-two sentence preview with a “Read More” expansion). |
| Users currently lack a direct way to favorite an activity while they are reading its detailed description, creating unnecessary friction in the user flow. | Moderate | Choose Activity | Integrate a clearly visible “Favorite” button (such as a star or heart toggle) directly into the activity description view. This allows users to save the activity immediately after reading about it, without having to navigate back to the main list. |
| The label for the “5 more minutes” button displayed during the break screen is ambiguous. It is unclear to the user whether clicking this button adds 5 minutes to their current break time or 5 minutes to their upcoming work session. | Trivial | Work/Break Session | Update the button copy to explicitly state the action’s outcome. Change the label from a generic “5 More Minutes” to a highly descriptive action phrase, such as “Add 5 Mins to Work Session” or “+5 Min Work Time.” |
| The UI on the active session screen is repetitive. The exact same text is displayed both inside the central timer circle and in the description view at the bottom of the screen, resulting in a cluttered and redundant layout. | Trivial | Work/Break Session | Streamline the interface to reduce cognitive load. Remove the descriptive text from inside the timer circle, reserving the circle strictly for the numerical countdown/progress visual. Keep the descriptive text solely in the bottom view. |
| While on the active working screen, users cannot see their break time status or watch it deplete. They currently have no visibility into how their break time is reducing unless they switch over to the dedicated break screen. | Trivial | Work/Break Session | Integrate a secondary, smaller break countdown timer directly into the main activity view. This will provide users with real-time visibility into both their active working time and their dynamically reducing break time simultaneously, eliminating the need to toggle between different views. |
.
