Calendar and time
The change feed, event writes, timezone handling while you travel, and the triggers that hang off a moving calendar.
Reading
Today's events ride in the brief, with the timezone you are actually in rather than the one your account was set up with. If you travel or work across timezones, a time without a zone is a bug, and "today" is taken from the machine clock rather than from a home country.
The change feed
Otto currently sees a static list of today's events. The change feed snapshots the next fourteen days on a cycle and diffs successive snapshots into real change events:
| Change | Meaning |
|---|---|
invited | a new event appeared |
moved | the start time changed |
location | the location changed |
cancelled | the event went away |
declined | an attendee declined |
Only differences are emitted, so a poll that finds nothing new produces nothing. The fetch is injected rather than hardcoded, which is what makes the diff testable against fixtures instead of against your real calendar.
This turns the calendar from something Otto looks at into something that can wake it, which is what everything below depends on.
Writes
Creating an event is confirm-first: Otto shows the exact item, with title, time, timezone and target calendar, and waits for a clear yes or a tapped button. Task creation follows the same rule.
Otto never deletes or edits an event it did not create. Every event it does create writes an undo note saying exactly how to reverse it.