The current mockups. Tap a day, tap a time. Picked times collect as chips. About 6 taps for three times on different days.
Scroll for earlier and later times.
Plain date and time fields; the phone shows its own wheels or calendar. One time at a time, so roughly 5 to 6 taps and spins per time.
Looks native and handles any date. Minute steps depend on the phone.
A column per day, a row per half hour. Tap cells to add times. 3 taps for three times; scroll up and down for the hours, sideways for the next week.
‹ This week · next week ›
Tap to add or remove. Scroll for mornings.
The booking-page pattern. Tap a date, then a time. About 6 taps; good for dates weeks away.
One row per day; tap a day to open its times. Each row shows what is picked. About 6 taps; scrolls naturally into later weeks.
- Sat 10 Oct
- Sun 11 Oct
- Mon 12 Oct
- Tue 13 Oct 6:00pm
- Wed 14 Oct 7:30pm
- Thu 15 Oct 6:30pm5:30pm6:00pm6:30pm 7:00pm7:30pm8:00pm
- Fri 16 Oct
Common times as one-tap chips, worked out from today. 3 taps when they fit; "Another time" falls back to A. The chips here are invented; real ones would need choosing.
Thu 6:30pm only appears if the chips include it; that is the catch.
Type times the way you'd text them. Each becomes a chip; anything unclear is flagged. No taps, but typing and a parser to get right.
"tue" means the next Tuesday. Tap a flagged chip to fix it.
Mornings, afternoons and evenings instead of clock times. 3 taps, but a booking like "Wed evening" still needs a time agreed in chat.
Fast and friendly for casual plans; too vague for anything with a start time.