Project.Supplies

Breaks down DIY projects into discrete, sequenced tasks with dependency tracking and timeline estimation. The system likely uses a directed acyclic graph (DAG) structure to model task dependencies, allowing users to define prerequisite relationships (e.g., 'frame walls before drywall') and automatically calculate critical path and project duration. Task sequencing prevents logical errors like scheduling finishing work before structural completion.

Automatically generates consolidated shopping lists from project tasks by aggregating materials specified across multiple tasks, deduplicating items, and calculating total quantities needed. The system likely maintains a materials database or allows free-form entry, then uses string matching or fuzzy matching to identify duplicate items (e.g., '2x4 lumber' vs '2x4 board') and sum quantities. Output formats typically include categorized lists (hardware, lumber, paint, etc.) for easier shopping.

Renders project tasks as a visual timeline or Gantt chart showing task duration, sequencing, and overall project span. The visualization likely uses a canvas-based or SVG rendering approach to display tasks as horizontal bars positioned along a time axis, with visual indicators for task dependencies (connecting lines or arrows). Users can interact with the timeline to adjust task dates or durations, with automatic recalculation of downstream tasks.

Automatically or manually organizes aggregated materials into logical categories (lumber, hardware, paint, tools, etc.) to match typical store layouts and shopping workflows. The system likely uses a predefined category taxonomy or allows custom categories, then assigns materials to categories via keyword matching or user selection. Categorized lists reduce cognitive load during shopping by grouping related items together.

Allows users to create new projects from scratch or from predefined templates for common DIY tasks (kitchen remodel, deck building, bathroom renovation, etc.). Templates likely include pre-populated task lists, material categories, and estimated timelines that users can customize. The system stores templates in a database and allows users to fork or clone existing projects as starting points for similar work.

Allows users to mark tasks as complete, in-progress, or blocked, and tracks overall project completion percentage. The system likely maintains a simple state machine (not started → in progress → complete) for each task and aggregates task states to calculate project-level progress. Progress visualization may include a progress bar, completion percentage, or visual indicators on the timeline showing which tasks are done.

Stores project data (tasks, materials, timeline, progress) in cloud storage, allowing users to access projects from any device and maintain persistent state across sessions. The system likely uses a simple database backend (possibly Firebase, Supabase, or similar) with user authentication to isolate projects per account. Data synchronization ensures changes made on one device are reflected on others.

Allows users to share projects with others (family members, contractors, friends) via shareable links or email invitations, with read-only or limited editing permissions. The system likely generates unique share tokens or uses role-based access control (viewer, editor) to manage permissions. Shared projects may be viewable without requiring recipients to create accounts, reducing friction for casual sharing.