APP SUMMARY: - A habit tracking app for people who want to build simple daily routines without using a complex productivity system. - It is for individuals who want to track a few habits consistently. - It solves the problem of forgetting, abandoning, or overcomplicating daily habit tracking. MVP DEFINITION: - Users can create habits - Users can mark habits complete each day - Users can view a simple progress history - Users can edit or delete habits - Intentionally excluded: social features, coaching, AI suggestions, gamification, advanced analytics USER ROLES: - Role: User - Purpose: track personal habits - Main actions: create habit, complete habit, review progress SCREENS: 1. Home Dashboard - Purpose: show today’s habits - Main actions: mark complete, view status 2. Create / Edit Habit - Purpose: add or update a habit - Main actions: enter habit name, frequency, reminder preference 3. Progress Screen - Purpose: show consistency over time - Main actions: review streaks or completion history 4. Settings - Purpose: manage account basics - Main actions: update profile, basic preferences CORE USER FLOW: 1. User opens the app 2. User creates one or more habits 3. User returns daily to mark completion 4. User checks progress and keeps the routine going CORE MODULES: - Module: Authentication - What it handles: sign up, login, account access - Module: Habit Management - What it handles: create, edit, delete habits - Module: Daily Tracking - What it handles: completion records by date - Module: Progress History - What it handles: past completion display DATABASE STRUCTURE: - Entity: User - What it stores: account identity, preferences - Key relationships: has many habits - Entity: Habit - What it stores: habit name, frequency, active status - Key relationships: belongs to user, has many completions - Entity: HabitCompletion - What it stores: habit id, completion date, status - Key relationships: belongs to habit BUILD FIRST: - what to design first: dashboard and create-habit flow - what to build first: user auth, habit CRUD, daily completion logic - what can wait: reminders, streak visuals, export features OPTIONAL V2 IDEAS: - reminders - streak milestones - weekly summaries ASSUMPTIONS: - one user tracks only personal habits - reminders are not required for MVP - mobile-first experience is preferred