View as Markdown

Device calendar sync

Calendite can read the calendar your phone already has — the one your work account, your family's shared calendar and everything else already syncs into — so you don't start from an empty grid.

It is one way. Calendite reads that calendar and never writes to it: nothing you create here appears in Google Calendar or Apple Calendar, and Calendite cannot edit or delete anything in them.

Android and iOS. The web build has no device calendar to read. On iOS a skipped occurrence of a repeating event is lost, because the system exposes it as a detached event this read doesn't reach — the rest of the series comes across correctly.

Turning it on

Either from the setup wizard's first step (Import My Events), or later at More → Calendar sync → Import from device calendar.

The first tap asks for the calendar permission. Refuse it and the switch goes back off, because without the permission there is nothing to read.

Every calendar on the device is read. The same event carried by two accounts — a meeting in both your work and personal calendars — is collapsed to one, chosen the same way every time so a resync doesn't swap one copy for the other.

What keeps happening afterwards

This is a sync, not a one-time import. Calendite watches the device calendar and re-reads it when something changes there, and again when you bring the app to the foreground. An event edited in Google Calendar shows the edit here; an event deleted there is removed here.

That only works because the two sides own different things:

Owned by the device calendar Owned by Calendite
The title The tag you gave it
When it happens, and for how long Alerts you added
Whether it repeats, and how Notes and description you wrote
Its location Colour, visibility, inner events

So tagging an imported event, adding an alarm to it and writing a note against it all survive the next read. Re-reading only rewrites what the device calendar owns, and only when it has actually changed.

A read that fails — permission revoked, a provider that threw — is not the same as a calendar that is now empty, and Calendite treats it that way: nothing is deleted on a failed read.

Turning it off

Flipping the switch off asks what should happen to the events it brought in:

What happens
Keep events They stay, as ordinary Calendite events. Nothing will update or prune them again
Remove events They go, along with the tags, alerts and notes attached to them

Keeping them is the safe answer if you have built anything on top of them.

Where it reads from

Calendite has no calendar account of its own. It reads whatever your phone has already synced — so the way to add a calendar to Calendite is to add it to your phone, where your accounts already live, and it appears here on the next read.

For a published list of dates rather than a calendar account — bank holidays, term dates, a fixture list — use data sources and feeds, which turns a JSON feed into a named category your rules can use.

Next