Keep going, even offline.

The idea

Timebird already saves calendar snapshots for a quicker start. We want to extend that foundation so you can create and edit supported items while disconnected, with a clear indication of what has been saved locally and what still needs to reach your calendar.

When connectivity returns, queued changes would be reconciled with the latest calendar state. If someone has changed the same event elsewhere, the app should explain the conflict and offer a choice rather than silently replacing their work.

We also want broader undo for event moves and assistant changes. A useful change history would show what happened and what can be restored. Actions that send invitations or emails need particular care: reversing a calendar edit cannot unsend a message someone has already received.

What we want to add

• Queue supported edits while disconnected
• Show local-save and sync states clearly
• Resolve conflicts without silent overwrites
• Event undo and a clear change history

How it could feel

Saved on this device. Waiting to sync. Your change is still here when the connection returns.

Getting the details right

Reliability is the main requirement. Offline changes must remain tied to the right account, survive a restart where supported, and never appear confirmed by Google before the server has accepted them.