mobtimeapp
Enable user configurable comma separated list of times instead of a single time pro rotation
Use of two notification times per rotation (e.g. at 3 and 5 minutes) could be used as an optional early rotation time and a mandatory rotation time and so offer more flexibility to the mob.
When the non-final times are up, the timer should show a notification and/or play a sound and continue counting.
We have tried this kind of timer in our mob retreats as configured at https://www.online-stopwatch.com/full-screen-interval-timer/?c=80wgdfd2hg
I'm going to have to chew on this for a bit.
I'm not sure how common of a use case it is, and it's easy to just stop the timer early and rotate if the mob feels like a specific turn is done before the time runs out.
I'm also not sure what the UI will look like for this. Currently the main timer has the [x] to stop the timer early and rotate. Does the secondary timer have a similar feature? If the app doesn't provide any obvious feedback to the user on the first timer "early" timer, how do I prompt the mob?
I'm not 100% against this feature, but I think I need other users not part of this mob retreat to have some buy in; I'm hesitant to add a complex feature for one particular use case.
Usually, only one time is configured and so this feature would have no implications for the common use case.
There is no secondary timer. if more than a single value is configured, all intermediate values only trigger an additional notification or sound.
After [x] the remaining time should be reset to the first value so that the timer is restarted from the beginning.
Yesterday I facilitated a session with a fix 3 minutes timer. As a facilitator, I pointed out that there is no personal code ownership and the code does not need to compile and pass all tests at the rotation. And, actually, I currently think that it worked even better than having an option to change after 3 minutes. I do not close the issue so that you can decide to implement it or not.
Let's leave this issue open until we figure out if we keep the combined soft/hard limit timer at our MobRetreat events or move to a single timer.
I do understand that use cases besides the MobRetreat events are required for adding this complexity.
