[Clock] Too easy to accidentally turn off the alarm instead of snoozing

[Robie Basak]

While half asleep and when I want to snooze, it's too easy to hit the wrong button and accidentally turn off the alarm instead of activating the snooze option.

I expect the snooze button to be more easily available, and for the "turn off" button to be made harder to activate - for example with a slide or something.

Other phones I've had have had the snooze button much bigger, or the snooze activate when the phone is turned over, or something like that, to assist with preventing accidental alarm switch off.

[Nekhelesh Ramananthan (nik90)]

Thanks for taking the time to report this bug. I can confirm this issue as well. Often I turn of the alarm while trying to snooze it. We need a better design for this. May be something similar to the call accepting/declining design that vivid has at the moment?

[Robie Basak (racb)]

Since reporting this I've read the design guidelines. I note that the "turn off" button is on the right and green, and the "snooze" button is on the left and white.

I suggest that maybe this is backwards. Turning off the alarm is essentially deleting this instances of it and is potentially dangerous, and so perhaps should be red and on the left? The "safe" action is to snooze, so that should be default, green and on the right.

However, even with that change (if you or design team agree - I admit it is subjective), the off button would still be too easy to hit, so I still think something further needs to be done to avoid user accidents.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Philippe Vaucher (philippe-vaucher)]

Ideally you'd want the volume buttons or the other button to snooze the alarm, which avoids the user having to watch the bright light of the display to snooze.

[Nekhelesh Ramananthan (nik90)]

Removing ubuntu-clock-app task from this bug report since the work needs to only be done in indicator-datetime.

[James Mulholland (jamesmulholland)]

As mentioned by Nekhlesh, this bug relates to UI elements belonging to indicator-datetime, rather than the clock application itself. Will reassign.