View as Markdown

Your phone's assistant

Calendite publishes its calendar to Android's AppFunctions: the mechanism that lets an on-device assistant act inside an app rather than merely open it. Ask for a dentist appointment on Tuesday afternoon, and the appointment appears in Calendite — no dictation into a form, no leaving the app you were in.

Android 16 and above. The functions are part of the app; whether an assistant may call them is decided by Android, not by Calendite. Google is opening that up to assistants gradually. When your assistant gains access, Calendite's side is already there — nothing to install, enable or configure.

What an assistant can do
Add events, reminders, deadlines and time periods
Find what is on between two days, by meaning as well as by name
Change the title, day, time, length or place of something it has found
Delete one occurrence, or a whole series, after you have confirmed it
Tick off a reminder or a deadline for a particular day

Repeats travel as the words you said. "Every other Tuesday" is translated by the same on-device model the app uses when you type it yourself, so an assistant can set up a repeating event without knowing anything about Calendite's rule language — and if a phrase cannot be turned into a rule, the assistant is told so rather than quietly setting up something else.

Finding is the same matching the app uses: it works on meaning, not spelling, so "my teeth thing" finds Dentist even though they share no words. That matters more when an assistant is relaying speech than it does when you are typing.

What it will not do on your say-so

The surface is deliberately narrow. Some of it is disclosure, and some of it is damage:

  • It cannot read or write your notes and descriptions. Overwriting something you wrote destroys work that nothing has read. They are not exposed in either direction.
  • It cannot change how an event repeats. Reshaping a rule changes every occurrence at once, which is not a thing to do from a sentence.
  • It cannot touch tags, colours or who can see an event. Those are organisation and disclosure, not the event itself.
  • A partner's events are read-only. What arrives through calendar sharing is not yours to move.

Deleting, and changing a repeating event

Two questions the app always asks, and an assistant has to ask them too.

Deleting always confirms. The first request to delete anything is refused, and the refusal says what would go — including anything that would disappear with it, such as an event that only exists inside the one being deleted. The assistant puts that to you, and only deletes once you have answered. There is no undo behind it, so there is a question in front of it.

A repeating event has to say which occurrences. "Move the stand-up to ten" means one day or every day, and getting that wrong rewrites a schedule silently. A request that does not say is refused with the question, so the assistant asks rather than guesses.

If something could not be honoured — a repeat that made no sense, a change that was cancelled — the assistant is handed a sentence saying so, to read back to you.

Where this happens

On your phone, inside Calendite.

An AppFunction runs in the app's own process, with the app's own access to its own database. There is no server in the path and nothing is uploaded to make it work: this is the same calendar, touched the same way, by something other than your finger.

What an assistant is shown of an event is a deliberate subset — its title, when it is, how long it lasts, where it is, how it repeats in words, and whether it is done. Not your notes, not your tags, not a location's coordinates, and never the underlying rule. Adding anything to that list is a decision to disclose it.

Everything else Calendite says about your data still holds; see what leaves your device.

Next