Re:The Nokia N9 Alarm Clock (2014)
by wl on Sunday April 07, 2019 @01:00PM
(#19598145)
Manipulating dials on displays is not good design, whether it's with a mouse or on a touchscreen.
[ Parent
| on HN ]
I can see how it's flawed with a mouse, but why is it bad design on a touchscreen? I haven't seen a better time picker.
I think the comment is getting at the fact that a knob/dial actually has a physical affordance (being grabbed and twisted), which is absent on a smooth glass surface. Hence, aiming to create interactive dials on a touchscreen is an inherently challenging endeavor.
I suppose the main solution in N9 was to make the dial big enough (not unlike a rotary telephone dial) as opposed to a small knob that you would wish to grab and twist.
The N9 would vibrate slightly as you turned the dial which helped make it feel tactile.
Maybe it depends on the input device quality and the task at hand, like for scrolling a huge file I will use dragging with the mouse then the left button or the wheel. Ideally your code is designed in such a way you can have an alternative input method for the clock like just typing in the vules and maybe up/down arrow spinners
They aren't necessarily good design, but affordances are often useful in Human-Computer Interaction.
How so? The various “circle” alarms on the App Store all have very high ratings and millions of downloads. So it works great for countless people.
I have found a faster way to set both hour and minutes for an alarm than two short circular motions.
Do you have a better design?
While this certainly true in some cases, I don't think this is one of them. They can be large enough to easily use, only 2 values are entered and are familiar for that purpose. The commonly seen alternatives are worse.
Re:The Nokia N9 Alarm Clock (2014)
by Synaesthesia on Sunday April 07, 2019 @02:09PM
(#19598670)
Ha you should see audio software, VST's etc.