Hey IH! 👋
I just came up for air after the most intense 2-week sprint I've had building Calendar0 (my menubar calendar app with AI).
The TLDR:
✅ Microsoft Outlook integration (full CRUD + webhooks)
✅ Complete UI/UX redesign with drag-and-drop timeline
✅ Multi-calendar support (read from all, write to one)
✅ Automated blog system
✅ Landing page redesign
✅ 110+ files modified, +2,000 lines of code
What triggered this sprint?
A user emailed: "Why doesn't this work with my work Outlook calendar?"
That simple question snowballed into:
1. "I should add Microsoft support" → 280 lines of provider code
2. "Wait, people have multiple calendars" → multi-calendar architecture
3. "The UI doesn't show this well" → complete day view redesign
4. "I should show this progress" → blog system + automation
The biggest win: Drag-and-drop timeline view
Before: Simple list of events
After: Visual hourly timeline where you can drag events to reschedule
The hardest part: Microsoft's API is... different
Google Calendar: Clean, well-documented, consistent
Microsoft Graph: 3 different date formats, weird recurrence patterns, Teams links everywhere
Spent 6 hours debugging why all-day events were showing as 12 AM...
What I learned:
1. Scope creep can be good - Each feature naturally led to the next improvement
2. Refactor first, add features second - The multi-provider abstraction made Microsoft integration 10x easier
3. Users don't see the code, they see the value - Nobody cares about my clean architecture, they care about Outlook support
The metrics:
Code: 110+ files touched, +2,000 net LOC
Time: ~14 days of focused work
Coffee: Too much ☕
Sleep: Not enough 😅
Now I'm wondering:
Should I slow down and focus on polish, or keep this momentum and add Apple Calendar next?
What's your experience with "build fast" vs "build perfect"?
If you want to try it: calendar0.app (macOS & Windows, Microsoft Store available)
Would love any feedback on the approach or the product itself!