From Dream to Done — Project Story

Inspiration

The idea for From Dream to Done came from a deeply personal frustration. I was using five different apps — a habit tracker, a to-do list, a goal planner, a journal, and a calendar — and none of them talked to each other. Worse, they all punished me. Missed a streak? Red warning. Skipped a day? Guilt notification. I started dreading the very tools that were supposed to help me grow.

I noticed the same pattern with people around me — especially those with ADHD or anyone who had ever set a New Year's resolution and quit by February. The problem wasn't a lack of motivation. It was that existing apps focused on deadlines and discipline instead of progress and enjoyment.

I asked myself: What if there was an app that connected your biggest life dreams all the way down to what you do today — and actually made the journey feel good?

That question became From Dream to Done.

What I Learned

Building this project reshaped how I think about productivity, design, and user psychology.

On productivity philosophy: Traditional goal-tracking is built on pressure — streaks, deadlines, daily quotas. I learned that tracking time invested rather than outcomes creates a healthier relationship with progress. The research behind the "70% Rule" (reaching 70% of estimated hours signals success) was a breakthrough in making goals feel achievable instead of all-or-nothing.

On user-centered design: I spent significant time defining four distinct user personas — the Overwhelmed Professional, the Neurodiverse Striver, the Aspiring Self-Improver, and the Methodical Planner. Each one taught me that "simple" means different things to different people. The app had to be simple enough for someone with ADHD to love, but structured enough for an OKR-style planner to respect.

On emotional design: Adding feeling tracking (😫 Drag → 🔥 Flow) wasn't just a feature — it was a philosophy. I learned that Success = Progress × Enjoyment. If someone is making progress but hating every minute, the approach needs to change. This insight shaped the entire product.

How I Built It

The app is structured around a three-layer hierarchy that forms its backbone:

🌟 VISION — "What life do I want?"
    └── 🏔️ MILESTONE — "What must be true to get there?"
            └── ⚡ ACTION — "What work does that require?"

Architecture and data flow: Progress flows upward through time logged. When a user logs 30 minutes on an Action, that time cascades up to its parent Milestone and then to its parent Vision. Every time log also captures a feeling score (1–5), so the app always knows both how much and how well things are going.

Core systems I built:

• User Status System — A state machine (NEW_USER → ONBOARDING → NO_VISION → NO_MILESTONE → NO_ACTION → READY) that ensures the user always lands on the right screen, whether they're brand new or returning after weeks away.
• Daily Planning System — Users plan their day by selecting Actions (manually or via a fun Spin Wheel), then execute by logging time and feelings. A calendar view ties it all together.
• Progress Engine — All progress percentages are calculated fields, not stored values, keeping data clean and always in sync.
• Freemium Model — Free users get 1 Vision and 3 Milestones. Premium unlocks unlimited content plus AI-generated milestones, actions, and time estimates.

Onboarding flow: I designed a guided 3-step onboarding (Welcome → Name → Theme) followed by Vision → Milestone → Action creation. The goal was to get users to their first planned day in under 3 minutes. Premium users get AI-assisted setup; free users enter everything manually with clear, encouraging prompts.

Challenges I Faced

Simplicity vs. depth. The biggest challenge was keeping the app simple while supporting a rich hierarchy (Vision → Milestone → Action → PlannedTask → TimeLog). Every screen had to feel lightweight, but the data model underneath is genuinely complex. I went through many iterations of the home screen alone — balancing today's tasks, progress bars, motivation stats, and navigation without overwhelming the user.

The "no punishment" philosophy. It sounds easy to say "no streaks, no guilt," but it's surprisingly hard to design for. Traditional engagement patterns rely on loss aversion (don't break your streak!). I had to find alternative engagement drivers — the feeling tracker, the momentum widget, the Spin Wheel — that motivate without punishing.

Competitive differentiation. The productivity app market is brutally crowded. Habitica, Todoist, Notion, Strides — each owns a piece of the space. I had to clearly articulate why From Dream to Done is different: it's the only app that combines a dream layer, goal-task hierarchy, time-based progress, built-in weekly reviews, feeling tracking, and a no-punishment philosophy in one simple package.

Subscription balance. Designing the free vs. premium split was tricky. Too restrictive and free users churn before they see value. Too generous and no one upgrades. I landed on a model where the core experience (1 Vision, 3 Milestones, unlimited Actions, full time logging) is genuinely useful for free, while AI features and unlimited Visions provide clear premium value.

Scope management. With features ranging from daily planning to AI-generated roadmaps to activity heatmaps, I had to ruthlessly prioritize. The MoSCoW method (Must Have / Should Have / Nice to Have) kept the MVP focused on what matters most: create a vision, break it into actions, plan your day, log your time, see your progress.

What's Next

The MVP (v1.0) focuses on the core loop: dream → plan → do → track. Future versions will add the Spin Wheel, calendar views, detailed stats and insights, AI-powered content generation, notifications, cloud sync, and data export. The vision is an app that grows with you — from your first dream to your hundredth done.

---

"Track time invested, not deadlines. Enjoy the process, not just the outcome."

Built With

• flutter
• openai
• python