Split off from #63, where it came up as a fair ask and was deferred.
A ring closes a sleep session when the wearer gets up and opens a new one when they settle, so one night can arrive as two records minutes apart. The app merges them into one stored session, which is right — that is the night, and the merge is what #63 fixed.
But the individual records are real information the app now hides. On the reporter's night the ring recorded 23:51–05:02 and 05:11–08:02, nine minutes apart, and the app shows a single 23:51–08:02 session with the nocturnal wake as an awake stretch inside it.
The vendor app keeps each record as its own row and never lets one displace another, so it shows both.
What to do: surface the underlying records somewhere on the sleep detail screen, without losing the merged session as the headline. The stage blocks are already stored per session and carry their own start times, so the record boundaries are recoverable from stored data.
Related, and now landed: a session's reported duration is time asleep, and the start-to-end range is shown separately. That distinction is what makes showing both records legible rather than confusing.
Split off from #63, where it came up as a fair ask and was deferred.
A ring closes a sleep session when the wearer gets up and opens a new one when they settle, so one night can arrive as two records minutes apart. The app merges them into one stored session, which is right — that is the night, and the merge is what #63 fixed.
But the individual records are real information the app now hides. On the reporter's night the ring recorded 23:51–05:02 and 05:11–08:02, nine minutes apart, and the app shows a single 23:51–08:02 session with the nocturnal wake as an awake stretch inside it.
The vendor app keeps each record as its own row and never lets one displace another, so it shows both.
What to do: surface the underlying records somewhere on the sleep detail screen, without losing the merged session as the headline. The stage blocks are already stored per session and carry their own start times, so the record boundaries are recoverable from stored data.
Related, and now landed: a session's reported duration is time asleep, and the start-to-end range is shown separately. That distinction is what makes showing both records legible rather than confusing.