Time pickers collect an hour and a minute, sometimes a second, sometimes a pair of them marking a span. The shape varies more than it does for most inputs: wheels that scroll, steppers that click up and down, a ruler you drag, or rows of From and To chips covering a week of availability. Twelve blocks cover that spread, from a reminder dial that takes a note to booking flows that put a week of dates above wheels, a ruler or a slot drawn to scale on the day.
The decision that matters is granularity, and most products set it too fine. Offering every minute means scrolling past dozens of values nobody wanted in order to reach the quarter hour they did; picking a step and holding to it makes the control shorter and the stored data cleaner. The second decision is the one people skip. A time with no stated zone is read as local by whoever picks it, stored as something else, and discovered on the day a booking lands an hour out.
One card holding a week of dates above the hour and minute wheels. The wheels scroll, drag and take the arrow keys, the edges fade so the reader sees there is more, and the next button waits for both halves.
Notification settings that silence a window of the day. Each row is a From and a To chip with its own remove button, Add New Range appends another, and an error hint explains the control once the limit is reached.
A settings card that turns the whole thing on before asking for anything else. A switch in the header, a note field for what the reminder says, then a minute wheel with a stepper bubble and Cancel, Reset and Save.
A compact trigger reading zeros until it is opened, then hours, minutes and seconds in three stepper columns. It suits a timer set in place, where the reader is composing a length rather than finding a moment on a clock.
Follow the reader's locale rather than choosing for them, and parse both on typed input whichever you display. If you must settle on one, the 24-hour clock removes the morning-or-evening ambiguity behind the classic booking error, at the cost of reading as foreign to people who never use it. Never show a bare hour with no period indicator at all.
Whatever you decide, put it on screen next to the field. A time picked without a stated zone is read as local by the person picking it and stored as something else often enough to break real bookings. Store an absolute instant rather than a wall-clock string, and remember that on daylight-saving days some local times happen twice and others never happen.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Time pickers collect an hour and a minute, sometimes a second, sometimes a pair of them marking a span. The shape varies more than it does for most inputs: wheels that scroll, steppers that click up and down, a ruler you drag, or rows of From and To chips covering a week of availability. Twelve blocks cover that spread, from a reminder dial that takes a note to booking flows that put a week of dates above wheels, a ruler or a slot drawn to scale on the day.
The decision that matters is granularity, and most products set it too fine. Offering every minute means scrolling past dozens of values nobody wanted in order to reach the quarter hour they did; picking a step and holding to it makes the control shorter and the stored data cleaner. The second decision is the one people skip. A time with no stated zone is read as local by whoever picks it, stored as something else, and discovered on the day a booking lands an hour out.
One card holding a week of dates above the hour and minute wheels. The wheels scroll, drag and take the arrow keys, the edges fade so the reader sees there is more, and the next button waits for both halves.
Notification settings that silence a window of the day. Each row is a From and a To chip with its own remove button, Add New Range appends another, and an error hint explains the control once the limit is reached.
A settings card that turns the whole thing on before asking for anything else. A switch in the header, a note field for what the reminder says, then a minute wheel with a stepper bubble and Cancel, Reset and Save.
A compact trigger reading zeros until it is opened, then hours, minutes and seconds in three stepper columns. It suits a timer set in place, where the reader is composing a length rather than finding a moment on a clock.
Follow the reader's locale rather than choosing for them, and parse both on typed input whichever you display. If you must settle on one, the 24-hour clock removes the morning-or-evening ambiguity behind the classic booking error, at the cost of reading as foreign to people who never use it. Never show a bare hour with no period indicator at all.
Whatever you decide, put it on screen next to the field. A time picked without a stated zone is read as local by the person picking it and stored as something else often enough to break real bookings. Store an absolute instant rather than a wall-clock string, and remember that on daylight-saving days some local times happen twice and others never happen.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.