Zoho but for ADHD People

Introduction

This document outlines the system requirements for the project "Zoho but for ADHD People," aimed at providing a productivity tool with separate to-do lists for work and personal life, catering to users who need a clear and organized overview of their responsibilities.

System Overview

Product Interpretation and Delivery Boundary

• Domain Descriptor: Task Management

  • Source Evidence: The product is designed to help users manage tasks by providing separate to-do lists for work and personal life.
  • Confidence: 0.9

• What is Being Built: A productivity tool offering separate to-do lists for work and personal tasks.

• Excluded Assumptions: Generic CRM features, Enterprise resource planning modules.

• Access: Application-owned identity.

• Behavior Contracts:

  • Manage Work Tasks:

    • Actor: User
    • Trigger: User adds or updates tasks in the work to-do list.
    • Outcomes: Updated work to-do list.
    • State Lifetime: Durable
    • Identity Continuity: Persistent
    • Audience Entry: Public
    • Failure Outcome: Task not added or updated

  • Manage Personal Tasks:

    • Actor: User
    • Trigger: User adds or updates tasks in the personal to-do list.
    • Outcomes: Updated personal to-do list.
    • State Lifetime: Durable
    • Identity Continuity: Persistent
    • Audience Entry: Public
    • Failure Outcome: Task not added or updated

Page Content and Component Coverage

• Landing Page:

  • Orientation and user acquisition before entering protected workflows.

• Work To-Do List:

  • Interface for managing work tasks.

• Personal To-Do List:

  • Interface for managing personal tasks.

• Authentication Page:

  • Account sign-up, login, and session access.

Functional Requirements as Story Points

• As a user, I want to have separate to-do lists for work and personal tasks to manage my responsibilities effectively. explicit
• As a user, I should be able to sign up, log in, and access my session to ensure my tasks are securely managed. required_inference
• As a user, I want to add or update tasks in my work to-do list to keep track of my work responsibilities. basic_default
• As a user, I want to add or update tasks in my personal to-do list to keep track of my personal responsibilities. basic_default

User Personas

• User: The primary user managing their work and personal tasks.

Core User Flows

1. Landing Page:

   • User visits the landing page to understand the product offering.

2. Authentication:

   • User signs up or logs in to access their to-do lists.

3. Work To-Do List:

   • User navigates to the work to-do list to manage work tasks.

4. Personal To-Do List:

   • User navigates to the personal to-do list to manage personal tasks.

Visuals Colors and Theme

• Primary: #2B579A
• Primary Light: #4A7BBE
• Secondary: #F4F4F4
• Accent: #FF6F61
• Highlight: #FFD700
• Background: #FFFFFF
• Surface: #F9F9F9
• Text: #333333
• Text Muted: #777777
• Border: #DDDDDD

Signature Design Concept

The design will feature a clean and organized layout with a focus on clarity and ease of use. The interface will use a calming color palette with clear typography to ensure users can easily navigate between work and personal tasks. The landing page will have a simple, welcoming design to guide users into the application.

Interaction Model & Motion Direction

• Interaction Model: Animated
  • Moderate scroll-triggered reveals and hover transitions.
  • Suitable for feature-rich product pages.

Non-Functional Requirements

• No additional non-functional requirements were inferred.

Tech Stack

• Frontend: React for Web
• Backend: Python, FastAPI
• Database: MySQL or MariaDB, use Alembic for migrations
• Local Orchestration: Docker, docker-compose

Assumptions and Constraints

• The application will focus on task management without incorporating CRM or ERP features.
• Persistent identity is required for managing durable to-do lists.

Glossary

• To-Do List: A list of tasks to be completed.
• Persistent Identity: The ability to maintain user identity across sessions.
• Durable State: A state that persists across sessions and device restarts.