What is a use case for chaining sleep/wake-up alarms?
Currently I’m only doing it to achieve a decreasing “snooze” duration, the idea is basically:
assuming I always snooze until the limit I set,
and I have the first alarm with longer snooze duration, snooze until its limit and treat the final dismiss (without CAPTCHA) as a pseudo-“snooze” for myself (I understand it’s not how it’s designed),
and then a second alarm with shorter snooze duration, snooze until its limit and treat the final dismiss (with CAPTCHA) as the real dismiss for myself,
but sometimes the second alarm’s CAPTCHA gets skipped if I planned their timings (alarm time, snooze duration, snooze limit) without careful calculations (which may cause alarms #1 to ring (without CAPTCHA) when alarm #2 is also supposed to ring (with CAPTCHA), causing alarm #2’s CAPTCHA skipped upon dismissing alarm #1).
So in other words, I’m doing all of the above just so that I can get decreasing “snooze” duration, there is no need to reconsider the design, but perhaps consider allowing “Halve the Snooze” to be set for each individual alarm and/or consider my “snooze list” idea?
The second alarm cannot start while there is the first alarm still in progress. After you dismiss this first alarm, the second alarm cannot start - it is already past its schedule, and also, you just confirm you no longer need alarms (by tapping the dismiss). Chaining alarms for the same time makes sense for reminders, but not for wake-up alarms.
Ok, so in the case of reminders, even if I tapped dismiss (e.g. for reminder alarm #1), that doesn’t mean I also no longer need to be reminded for reminder alarm #2, right? I understand “the second alarm cannot start - it is already past its schedule” from a mechanics point of view, but why not have a queue system so that alarms can ring one at a time? (instead of getting completely skipped if it happens to conflict with another alarm)