4 ms·
For alarms and clock times, my guess is data validation. The app could correct or block invalid time entries (e.g., accidentally hitting 2500), or it could rest
by jljljl 9y ago
For alarms and clock times, my guess is data validation. The app could correct or block invalid time entries (e.g., accidentally hitting 2500), or it could restrict the entry set.
It also means the number will be in the correct format. your example, 930, could mean many things (930 seconds? 9:30am or 9:30 pm?)
- npgatech 9y agoIf all inputs are in hh:mm format, then there is no ambiguity of 930 as 9:30 am/pm. There could be a toggle for AM/PM. Who puts seconds as an input for setting their morning alarm? MAD!
- dogecoinbase 9y agoWhat's the unambiguous setting of 73:45 in hh:mm format?
- oneeyedpigeon 9y agoInvalid input, just as the empty string or a single digit would be.
- KozmoNau7 9y ago3 days, 1 hour, 45 minutes. Simple. The Android clock app silently corrects 73 minutes to 1 hour 13 minutes. So for 1:13:45 (hh:mm:ss) you can input "7345" on the keypad and It. Just. Works.
- lobster_johnson 9y agoBut an alarm clock sets a relative point in time that happens every day. Putting "3 days" into a calendar is fine, but for an alarm clock it makes no sense.
- KozmoNau7 9y agoSo you add basic input validation.
- lobster_johnson 9y agoYes, but the person who originally proposed this argued that there was no ambiguity.