Calezoo Reminders

Calezoo Reminders hits the sweet spot. We’ve built an all-in-one productivity app that combines the power of advanced scheduling with a clean, dead-simple interface that anyone can master in seconds.

Comment

Building Calezoo (pronounced Cal-Zoo) hasn't just been about writing code; it’s been about solving the "Implementation Gap"—the frustrating space between knowing what you need to do and actually doing it.

What Inspired Me

The inspiration for Calezoo came from observing notification fatigue. Most reminder apps treat every task as a one-time whisper. If you miss that whisper, the task dies. I wanted to build a "Second Brain" for the High-Functioning Forgetful—specifically for neuro-inclusive users (like those with ADHD) who need more than a simple nudge.

I was inspired by the persistence of apps like Due and the simplicity of Apple Reminders, but I wanted something that combined aggressive reliability with smart context.

How I Built It

I chose Flutter for the frontend to ensure a seamless experience across iOS and Android, backed by Firebase Firestore for real-time synchronization.

The core of the app is a custom-built Reliability Engine. To keep the app lightweight and battery-friendly, I implemented a Stateless Sliding Window (SSW) algorithm. Instead of scheduling every reminder for the next year, the system only schedules the next $n$ occurrences.

Key Technical Stack:

  • Framework: Flutter (Dart)
  • Backend: Firebase (Auth, Firestore, Cloud Functions)
  • Local Tasks: Workmanager for background "Heartbeat" sync.
  • Persistence: flutter_local_notifications with custom sound profiles.

🧠 What I Learned

This project taught me that User Experience (UX) is more than just UI:

  1. The Psychology of Persistence: There is a fine line between a helpful nudge and an annoying alarm. I learned to implement "Smart Snoozing" that adapts to user behavior.
  2. State Management: Handling real-time updates across multiple devices while maintaining offline-first capabilities was a masterclass in using the Provider and Bloc patterns effectively.
  3. Background Processing: I learned the hard way that mobile OSs (especially Android) are aggressive about killing background processes. Reliability requires a "Heartbeat" mechanism to re-sync missed triggers.

Challenges Faced

The biggest hurdle was Notification Reliability.

  • The Problem: If a user’s phone is in "Do Not Disturb" or "Low Power Mode," standard timers often fail.
  • The Solution: I had to dive deep into native Android AlarmManager and iOS UNNotificationRequest APIs to ensure that Calezoo reminders are treated with high priority.

Another challenge was managing Recurring Logic Complexity. Calculating the "3rd Friday of every other month" sounds simple until you have to account for leap years and time zone shifts. I used the $RRule$ (Recurrence Rule) standard to ensure math-based accuracy for every task:

Future Vision Calezoo is currently in its growth phase. My next goal is to improve on the AI-driven scheduling already included with suggestions for the best time to complete a task based on the user's past "Completion rate."

Next Step: Would you like me to expand on the technical documentation for the SSW logic, or should I help you draft the About Me/Developer profile for your app store page?

Built With

Share this project:

Updates