4 ms·
I'm on stock Android using the stock Google made Clock app for my alarms and I still sometimes need to double-take and make sure I'm not snoozing instead of tur
by flanbiscuit 6y ago
I'm on stock Android using the stock Google made Clock app for my alarms and I still sometimes need to double-take and make sure I'm not snoozing instead of turning my alarm off.
This[1] is what it looks like when the alarm goes off. (Swipe left to the "zzz" snooze icon or swipe right to the off icon). I can't always rely on muscle memory because I am not always consistent in which direction I put my phone down on the nightstand. This is not the best UI for a person who has just been woken out of sleep and still groggy.
1. https://www.androidpolice.com/wp-content/uploads/2015/07/nexus2cee_Screenshot_20150711-110009.png https://www.androidpolice.com/wp-content/uploads/2015/07/nex...
- godshatter 6y agoThere is also plenty of room to replace those three icons with "Snooze" and "Stop Alarm" buttons. Plenty of room even for multiple snooze buttons of varying duration. There is a downside to the button approach, though. I have one app that uses buttons to snooze or stop the alarm and I almost always touch some random one when I'm pulling the phone out of my pocket. That's why I like some apps that use buttons that have to be held down for a second or two to register for certain actions. Phone interfaces are a minefield for me for some reason. It's too easy to accidentally push a button you didn't realize was a button when you were trying to scroll down the screen but pressed it too hard when you did so. I run into lots of pitfalls like this. I grew up in the era where the OS interface was a "READY" prompt, so I've seen most of the paradigms out there over the years. Nothing has annoyed me as much in recent memory as having a touch-sensitive interface on a slick, compact phone with rounded edges that I desperately don't want to drop.