Timezone

Setting itThe row shows the zone and the time in it

On the web the zone is under Settings › Account; on the phone it has its own Timezone section in Settings. Either way, one row names the current zone with the clock time there beside it. That clock is the check worth making: a zone name is easy to misread, a wrong hour is not.

Tap the row to open a search over every zone, type a city or a region, and pick one. It saves as you pick, and the row closes with the new zone and its time.

TravellingThe app follows the device's zone by itself

When a device opens the app somewhere new, the app switches to that device's zone on its own. The phone announces the move in a brief banner. The web does it silently, on the next page it loads. The reasoning is that today is where you are, and the device already knows where that is.

A zone you pick by hand in Settings stands. The switch is triggered by a device travelling, so sitting still leaves your choice where you put it. Each device reports where it is. The last one to move somewhere new sets the zone.

The phone also offers the move instead of waiting for it. When the device is standing in a zone the app is not set to, its Timezone section shows This device is on that zone with the time there, and one tap switches.

Switching rewrites nothing. Times are stored with their zone attached, so an entry written at 9am in one place keeps its moment. What changes is which day the app files things under from now on.

What it touchesDays, the timeline, and reminders

Three things follow from the zone. A late-night note is filed on the night you wrote it rather than the next morning. The Day timeline reads in local hours, top to bottom. And reminders are worked out in it: one set for 9am means 9am in this zone.

It touches nothing you have already written. There is no re-filing pass and no rewrite. The stored times were always absolute.