Meeting Scheduler
Day strip, slot grid and a time zone the visitor can change — because a slot list with no zone on it is how this pattern wastes an hour of everyone involved.
Month grids, availability pickers, booking flows and time slots.
Scheduling is a timezone problem wearing a calendar costume. The interface work is to make the zone explicit at the moment of choice — "3:00 PM your time (10:00 PM in Berlin)" — and to keep slot buttons big enough to hit on a phone. These cover the month view, the availability picker and the confirmation step.
Day strip, slot grid and a time zone the visitor can change — because a slot list with no zone on it is how this pattern wastes an hour of everyone involved.
A day strip built as a radio group rather than buttons, so arrow keys move between dates and sold-out days disable properly — the fold for anything sold by the appointment.
The control that turns notification volume down instead of off, which is the choice most people actually want.
A month view where event chips truncate and overflow becomes "+n more", so a busy Tuesday never changes the height of the row it sits in.
Planned downtime with a live countdown, an end time in the reader’s timezone, what still works — and a different sentence once the window overruns rather than a negative timer.
Availability per variant stated before the cart, because discovering it at checkout is where the basket gets abandoned.
A year of daily activity as one square per day, bucketed against a quantile so a single outlier cannot flatten the scale.
Time down the side, tracks across, breaks spanning the width — the one comparison a month view cannot make. Falls to a linear list on a phone, from the same array.
What each integration actually does, not a wall of logos — with availability as a text pill rather than a tinted border, and the name as the link so the card is not one enormous one.
The corner launcher, with real availability instead of a stock reassurance, article deflection before the form, no self-opening, and a way to make it go away.
Planned downtime with an actual end time on it — "back soon" is not a time, and a maintenance page without one looks like an outage nobody has noticed.
Both days in full, as two grids rather than a day switcher — because this is the page people print, and a tab hides half of it from find-in-page.
A booking widget above the fold, every price published including the awkward ones, and a footer carrying the registrations a regulated trade must show.
One thing, one price, named above the fold — for a course, a consultation or a one-time licence, where there is nothing to compare against and hiding the number answers the only question last.
Backwards from now and forwards from it on one screen — a day-grouped timeline, a month grid where a busy Tuesday never changes the row height, and the state both are in on day one.
Written for the person refreshing it during an outage: current state above the fold, the maintenance window as a real block with an end time, and a component list that names what still works.
Calendars, ranges, time fields and duration inputs.
Inputs, selects, checkboxes, radios and segmented controls.
Whole marketing pages, assembled and ready to clone.
Not found, server error, maintenance, offline and permission walls.
Inboxes, unread badges, grouped feeds and preference panels.
Bento grids, alternating rows, icon lists and tabbed showcases.