You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some people like me are very prone to automatically postponing the alarm each time it rings, or even sometimes dismissing it completely, which is all really unhealthy (you aren’t really getting useful sleep in that piecemeal way, moreso it has tendency to tire you even more). The decision should be made when you’re already conscious, and adding a setting to the app to completely disallow doing anything with the signal until you do some conscious thing would be great.
Things that can be suggested that I’ve seen elsewhere:
A small list of three or so simple arithmetic problems like addition/subtraction of two-digit numbers, or maybe also multiplication by a one-digit number. The user should enter all answers from the (default) numeric keyboard, then if they are all right, they would be able to access dismissing/snoozing.
A grid of circles of several different colors, the user is prompted to tap on all circles of an arbitrary color before the unlock.
A grid of circles which flash in a sequence of, say, seven-ish. The user is prompted to tap the same sequence.
There are probably more good candidates that might be easier to implement and also require conscious thinking which will wake the user up before they can make a decision if they really want to sleep further or not.
(There can also be an option to disable snoozing entirely, which can be handy if just the dismissal is locked under the “awareness task”, because there can be cases when that’s more useful but after thinking about it and filing a FR into another FOSS alarm clock, I now think both should be locked away because if you want math then you won’t use the snooze button.)
A better option to add is to make this behavior be settable per-alarm (which is even more useful if more than one gets implemented eventually). So you can use alarms as notifications when you’re expected to be awake already, without needing to distract yourself too much, and also do this for sleep alarms.
The text was updated successfully, but these errors were encountered:
Some people like me are very prone to automatically postponing the alarm each time it rings, or even sometimes dismissing it completely, which is all really unhealthy (you aren’t really getting useful sleep in that piecemeal way, moreso it has tendency to tire you even more). The decision should be made when you’re already conscious, and adding a setting to the app to completely disallow doing anything with the signal until you do some conscious thing would be great.
Things that can be suggested that I’ve seen elsewhere:
There are probably more good candidates that might be easier to implement and also require conscious thinking which will wake the user up before they can make a decision if they really want to sleep further or not.
(There can also be an option to disable snoozing entirely, which can be handy if just the dismissal is locked under the “awareness task”, because there can be cases when that’s more useful but after thinking about it and filing a FR into another FOSS alarm clock, I now think both should be locked away because if you want math then you won’t use the snooze button.)
A better option to add is to make this behavior be settable per-alarm (which is even more useful if more than one gets implemented eventually). So you can use alarms as notifications when you’re expected to be awake already, without needing to distract yourself too much, and also do this for sleep alarms.
The text was updated successfully, but these errors were encountered: