Well, individual hours and minutes fields are the safest, but slower to use than a single field. You can set the clock to 0 if you do not expect a lot of duration for 1 hour.
It may depend on your population, but I expect users to be able to process hours and minutes in the same text box if you provide an invitation, for example, "Time duration (hour: min):"
With this prompt, accept any initial continuous string of numbers as hours and any subsequent continuous string of numbers in minutes, so that all of the following input are considered equivalent.
I see no reason to require minutes to be less than 60. The user should also be able to express the time as:
When the focus leaves the field, automatically adjust everything that the user enters in the specified (hrs: min) format in order to respond to the interpretation you made.
If everything you need for your purpose is an approximation of time (or your users still rate it), consider the option buttons or a drop-down list with duration ranges (for example, from 0 to 5 minutes, from 5 to 15 minutes, from 15 minutes to 1 hour, more than an hour). Or, if certain duration boundaries exist and the intervals are functionally linear, you can use the marked slider.
Regardless of the input or control format you use, it must be compatible with the source of information. Where do users get this duration? What units, format, intervals and degree of accuracy are used there? How do users think and talk about time among themselves?
Michael zuschlag
source share