screensdesign

Time zones: explain which clock changes

An event’s zone, the calendar’s display zone and an additional reference clock are different settings. Ten recorded screens show how mobile scheduling interfaces can distinguish them.

A person changes a calendar from Manila to Los Angeles. Did the meeting move, or is the same meeting now displayed on another clock? A control called Time zone does not answer that question by itself. Mobile scheduling has to distinguish the zone used to interpret event input from the zone used to display an existing event and from an extra reference clock.

Start by naming the object affected. Use Event time zone, Calendar display time zone or Additional time zone when those are the actual concepts. Show the date as well as the hour after conversion, because an apparently small change can cross midnight. The recordings below show interface choices, not proof that every provider handles daylight-saving transitions or recurring events correctly.

The calendar and scheduling examples cover the broader task. This article isolates the clock-setting decision that can otherwise make a correct calendar look wrong.

Put the zone beside the event it interprets

Artful Agenda’s Create Event form includes a Time Zone row with Manila and its GMT offset. Fantastical’s event detail explicitly labels EVENT TIME ZONE and offers Show Time Zones. Both provide a reference point for interpreting the displayed start and end rather than burying the value in unrelated preferences.

When editing a zone, explain whether the action preserves the event’s instant or preserves the entered wall-clock time. Those choices can produce different meetings. Use a before-and-after date and time summary when the consequence is material. Do not silently adopt the device’s new zone while someone is halfway through creating an event.

Keep the zone choice attached to the event draft until save. If the calendar account enforces another setting, reveal the effective value before confirmation. A locally selected zone should not remain on screen after the provider rejected it. Preserve the person’s intended time and let them correct the unsupported configuration instead of silently changing the event.

Artful Agenda: Artful Agenda exposes Time Zone within the event form next to time and date fields.
Artful AgendaArtful Agenda exposes Time Zone within the event form next to time and date fields.
Fantastical Calendar: Fantastical labels the event’s zone explicitly and separates Show Time Zones.
Fantastical CalendarFantastical labels the event’s zone explicitly and separates Show Time Zones.

A reference clock should not rewrite event data

TickTick’s Additional Time Zone setting explains that multiple zones can be viewed in the calendar. Notion Calendar’s zone settings identify Los Angeles as Primary time zone and allow a custom LA label. These are display-context decisions, distinct from choosing the zone of one event.

Keep display preferences separate from stored event timing. Adding a comparison clock should not modify existing meeting invitations. If making a zone primary changes the visible day boundaries, explain that the calendar is being re-presented rather than rescheduled. Retain a way to inspect the event’s original time-zone context.

A custom short label can make comparison useful, but it should not replace the actual zone identity everywhere. An LA label does not explain the date-specific offset on its own. When a reference zone is removed, keep events intact and preserve any valid event-level settings. Test the difference between hiding a column and deleting a saved display preference.

TickTick:To-Do List & Calendar: TickTick explains additional zones as a calendar-view feature.
TickTick:To-Do List & CalendarTickTick explains additional zones as a calendar-view feature.
Notion Calendar: Notion Calendar separates the primary-zone setting from a custom LA label.
Notion CalendarNotion Calendar separates the primary-zone setting from a custom LA label.

Selected, pending and applied should agree

Calendly’s native-style zone selector uses radio choices with Cancel and Done. A second Calendly example shows a zone selector inside a mobile web view with search, local times and an am/pm versus 24h control. The surrounding surface matters: time format and time-zone identity are related presentation choices, not the same field.

Choose an immediate or staged save model and use it consistently. With Cancel and Done, people reasonably expect to inspect alternatives before committing. If a web view updates automatically, show the effective result when it closes. Avoid leaving the host app’s summary stale while the embedded scheduler is using another zone.

Retain format preferences independently. Switching to 24-hour time should not change the selected zone, and choosing a zone should not reset the customer’s format without a product reason. Keep the apply action reachable above the keyboard. If a search result has no supported equivalent in the connected scheduling provider, explain the mismatch before saving.

Calendly: Meeting Scheduling: Calendly offers a selected zone with distinct Cancel and Done actions.
Calendly: Meeting SchedulingCalendly offers a selected zone with distinct Cancel and Done actions.
Calendly: Meeting Scheduling: The mobile web-view picker combines zone discovery with a separate time-format control.
Calendly: Meeting SchedulingThe mobile web-view picker combines zone discovery with a separate time-format control.

Make midnight and unusual offsets ordinary test cases

Notion Calendar’s Client Meeting runs from 11:30PM on one date to 12AM on the next, with a visible thirty-minute duration. Evernote’s zone list includes current local-time examples and a half-hour offset, but its captured heading exposes timeZoneTitle. That visible localization defect is a reminder to test the text around the data, not just the conversion.

Show end date when an event crosses midnight. Validate the full date-time interval instead of comparing only hour and minute fields. For date-specific offset changes, use the platform or provider’s supported zone rules and test ambiguous or missing local times explicitly. Do not improvise conversion by adding a fixed number of hours.

Keep all-day events distinct from timed events. A date-based event may have a different interpretation from an instant displayed at midnight. Preserve that product rule through import, edit and display. If a zone change alters the apparent day, explain the result instead of making the item look as though it disappeared from the calendar.

Notion Calendar: Notion Calendar shows different start and end dates for an overnight thirty-minute meeting.
Notion CalendarNotion Calendar shows different start and end dates for an overnight thirty-minute meeting.
Evernote: AI Notes & Notebook: Evernote’s list shows rich zone details but a visible timeZoneTitle heading defect worth guarding against.
Evernote: AI Notes & NotebookEvernote’s list shows rich zone details but a visible timeZoneTitle heading defect worth guarding against.

Test the meaning of the change, not only the list

Ask a participant to schedule a call in a named city, view it from another city and then add a reference clock. Have them explain which steps changed the meeting and which only changed its display. This checks the mental model more directly than timing how quickly they can find a row.

Include a provider save failure, a device-zone change during editing, an event near midnight and a future date whose offset differs from today. Test long translated labels and search aliases on a narrow screen. Review the saved event in another client so a local summary cannot conceal a server-side discrepancy.

Unexpected results need a useful error and recovery state. Track corrected event times, abandoned zone changes and provider mismatches with appropriate privacy. Do not log private event titles or participant details merely to count conversion errors. A successful sheet dismissal is not proof that the meeting remained at the intended instant.

A two-clock scheduling test

Create one timed event in a named zone and inspect it from a second display zone. Ask the participant whether the meeting itself changed. Add a reference clock and repeat the question. These steps should produce clearly different explanations even when they use similar city lists.

Now edit the event zone near midnight and review start date, end date and duration before saving. Use a controlled provider response that rejects the chosen configuration. Preserve the intended input and show the effective saved state instead of leaving a misleading local summary.

Repeat with a future date, an all-day item and a device-zone change while the form is open. Check the record in another calendar client after saving. Review zone identifiers and date-specific offsets through supported provider tooling; do not substitute a fixed-hour arithmetic check. The acceptance criterion is the intended meeting and an understandable display, not merely a picker that closes successfully.

Review every meaning of Time zone

Use these checks on a working build, not only on the polished reference state.

  • Name event input, calendar display and extra reference clocks separately.
  • Explain whether a change preserves the instant or the entered wall-clock time.
  • Keep zone identifiers distinct from their date-specific displayed offsets.
  • Search city and zone aliases without silently selecting an ambiguous abbreviation.
  • Preserve pending values and verify the connected provider’s effective saved result.
  • Test overnight, all-day, half-hour and date-specific rule changes.
  • Check localization keys, long names, selected-state announcements and format independence.

Questions worth resolving before shipping

Is an offset such as GMT+8 enough to store a zone?

An offset can describe a particular conversion but may not capture a named region’s rules over time. Use supported zone identifiers and provider behavior appropriate to the product, then display the offset for the relevant date.

Should changing the primary zone reschedule events?

A display preference should not silently rewrite event timing. If your control edits the event’s interpretation instead, label that scope and explain whether it preserves the instant or the wall-clock time before confirmation.

Why show both start and end dates?

A meeting can cross midnight even when it is short. Explicit dates prevent an end time of 12AM from looking earlier than an 11:30PM start. Validate the interval as a full date-time range.

2,958 apps in the top charts.Ask them anything.

Compare calendar forms and time-zone settings in ScreensDesign Pro. Study the zone selector together with the event summary, so your own scheduling interface explains which clock changes and which meeting stays the same.