Slothy

The Idea

I built Slothy because every task manager I tried was either too complex or too forgiving. I wanted one that gently called me out when I kept pushing the same task to tomorrow.

The concept is simple: you have two lists — Today and Tomorrow. Any task you drag from Today to Tomorrow increments a "procrastination counter" tied to that task. The counter stays visible. It doesn't reset. It just quietly accumulates.

Core Features

• Two-list structure — Today and Tomorrow, nothing else
• Procrastination counter — each defer increments a badge on the task card
• Swipe gestures — swipe right to complete, swipe left to defer to tomorrow
• Midnight reset — Tomorrow becomes Today automatically at midnight
• Dark mode — full system-aware dark mode support
• Local notifications — optional daily reminders
• On-device storage — all data stays on your device via Hive, no accounts, no sync, no server

Technical Decisions

I chose Flutter because I wanted to target both Android and iOS from a single codebase without sacrificing the feel of a native app. Dart's strong typing made the state management code clean to reason about.

For storage, Hive was the clear choice. It's fast, purely local, and has excellent Flutter integration. I didn't want to pull in Firebase for something that fundamentally doesn't need a server.

The midnight reset was the trickiest piece. I ended up using a combination of flutter_local_notifications for the scheduled trigger and a startup check that compares stored dates — so it works even if the app was closed at midnight.

What I Learned

Building Slothy taught me that constraints are features. Limiting the structure to two lists forced me to make harder decisions about what the app should and shouldn't do. Every time I wanted to add a third category or a priority flag, I asked: does this serve the core idea? Usually the answer was no.

It also taught me to think carefully about persistence across app restarts and OS kills — something that catches a lot of mobile developers off guard.