Calendar & Habits
Calendar
A deliberately small app that proves a system we build reads and writes the calendar a client already uses: two-way Google Calendar sync, recurring events with per-occurrence exceptions, and habit tracking.
Some details omitted under NDA
The problem it solved
Clients already live in Google Calendar. Asking them to keep a second diary never works: within a week one of the two is wrong.
This project exists to prove the opposite: that a system we build reads and writes the calendar the person already uses, in both directions, without asking anyone to change habits.
What the app does
Two-way sync
Connect the Google account, push the events created here and pull the changes made over there.
Recurring events with exceptions
One occurrence can be changed without touching the whole series.
Several calendars
More than one calendar, with categories and labels to keep commitments apart.
Habits
Habit tracking by marking completions.
How it turned out
- An event created here shows up in Google, and a change made in Google shows up here.
- Changing a single occurrence does not break the series, which is exactly where most calendar integrations fall apart.
- It is deliberately a small project. It stands as proof that we integrate with Google Calendar, not as a replacement for the calendar a client already uses.
In numbers
2
directions of sync
33
API operations
5
screens
For technical visitors
The rest of this page is written for whoever decides the purchase. This block is for whoever has to maintain the service.
- 33 endpoints, 31 use cases, 35 spec files and 5 frontend pages.
- Google Calendar integration over OAuth: connect the account, push local events and pull changes from the Google side.
- Recurring events with per-occurrence exceptions, so editing one day does not rewrite the series rule.
- Small scope, owned as such: this is the proof of the integration, not a competing calendar product.