Tuck-In App — Usability Issues from Testing
- Onboarding settings don’t carry over to the main app (Severe)
Angela’s bedtime didn’t transfer from onboarding into the actual app. We will fix this by ensuring all onboarding inputs (bedtime, wake time, preferences) persist into the user’s profile and home screen.
- Confusion about what’s being logged: last night’s sleep or tonight’s? (Severe)
Candy couldn’t tell if she was logging sleep she already had or setting a goal for tonight. We plan to fix this by including clearer labeling and time context (e.g., “Log last night’s sleep” vs. “Set tonight’s bedtime”) to limit confusion.
- Too many notifications (Moderate)
Both participants flagged that the onboarding showed too many notifications, and many of them were not clear whether the notification was going to come from the bear or the phone. We will fix this by clearly indicating which notifications would come from the phone and the bear.
- Hard to find how to set up a wind-down routine (Moderate)
Candy needed help navigating to the routine setup. She assumed onboarding already handled it. We will fix this by making the path to creating or editing a wind-down routine be more visible, ideally surfaced on the home screen or through the teddy bear interaction.
- Onboarding felt impersonal and some content didn’t resonate (Moderate)
Candy didn’t agree with some of the statements presented during onboarding and felt the experience wasn’t tailored to her. We can fix this by providing more flexible response options during the onboarding process.
- Content library isn’t discoverable from the home screen (Moderate)
Candy noted that nothing on the home screen points you toward the content library. For a first-time user, they might not think to experiment with it. We should add a prompt or card on the home screen under quick actions (maybe “Queue music, podcasts, and more for tonight”) that links directly to the content tab.
- No error prevention or undo for sleep logging (Moderate)
Candy noticed there’s no way to undo or correct a sleep log once it has started, which can cause irregular data collection. We will add a button to cancel a sleep log in case of misclick.
- Audio content icon reads as “text/stories,” not sounds (Trivial)
Candy expected the icon to mean reading content, not audio. A speaker or headphone icon would communicate the full range of content types more clearly without requiring extra thought. On the other hand, we will not be addressing this issue because our other users found it intuitive and it is important that users know that the content library isn’t just music, but breathing exercises, sounds, podcasts, and more.
- Unclear how sleep consistency is measured (Trivial)
Candy was curious how the consistency metric works and worried it wouldn’t be fair for people with irregular schedules (shift workers, etc.). A brief explanation or tooltip would help set expectations. However, our other user liked the included metrics, and we worry that if we add too much text, we would impede on minimalist design. Thus, we will not be implementing this change.
- Achievements/progress doesn’t feel essential (Trivial)
Angela didn’t see the rewards system as adding much value and felt it leaned toward app engagement rather than actually helping her sleep. We believe this is a user-specific issue, though, since she had previously reported she doesn’t like apps. Hence, we will not address this.
