A calendar of your own that other people can follow
Sending five events one at a time is worse than sending none. What people want is a thing they can follow once.
What most people assume
That sharing a calendar means giving people access to your personal one.
A separate calendar, not your own
The calendar you share is not the one holding your dentist appointment. It is created for the purpose, tied to one of your existing accounts, and it holds only what you put in it.
Because it is tied to an account, it syncs to your other devices like any other calendar — you are not maintaining an island.
They subscribe once
The people you share with subscribe to a link. Everything you add afterwards appears for them without another message, and everything you move moves for them too.
This is what makes it worth doing for a fixture list or a rehearsal schedule, where the changes are the whole point.
What it does not do yet
It is read-only. Followers see what you publish; they cannot add to it or edit it. For a team calendar that is usually right, and for a shared household one it is a real limitation worth knowing before you start.
The feed asks to be refreshed hourly, so treat it as a schedule people follow rather than a chat they watch.
The numbers
| What it describes | Value |
|---|---|
| Hours between refresh requests | 1 |
| What it costs | 0 |
What it looks like
What to do
- Make a calendar for the purpose rather than sharing an existing one.
- Tie it to the account you actually keep, so it reaches your other devices.
- Tell people it is a subscription — some apps file those separately from invitations.
- For urgent changes, message people as well as moving the event.