Personal OS: ADHD Smart Planning List

The company appears to be a solo project (1 person) building an iOS app for people with ADHD-related planning friction. The product is described as a working alpha that helps users break projects into smaller actions and see what to do next. It uses Swift, SwiftUI, and SQLite, and incorporates AI tools like Codex and GPT-5.6 during development.

What changed: The author reports building a native iOS app for ADHD planning, using AI-assisted development tools during a hackathon. The tool is described as an alpha with incomplete features, focusing on local task/project/stage workflow before expanding AI features.

Single most important open question: Is there evidence of user validation or adoption beyond the solo developer's own use? The description states no revenue, customers, or traction data are available.

The description states that Personal OS is a working alpha for planning projects, stages, tasks, and smaller task steps. It helps users keep work visible, break a task into manageable actions, and see what to do next. It is built as a native iOS app using Swift, SwiftUI, and SQLite.

Evidence:

• "Personal OS is a working alpha for planning projects, stages, tasks, and smaller task steps"
• "It helps users keep work visible, break a task into manageable actions, and see what to do next"
• "Built a native iOS app with Swift, SwiftUI, and SQLite"

Inference: The tool appears to be a task management application focused on breaking down larger goals into actionable steps. It is not described as a marketplace, SaaS platform, or developer tool.

The description states that the product helps people with ADHD-related planning and task-initiation friction turn projects into smaller, clearer next actions. The inspiration behind it was to provide a calmer way to handle overwhelming goals, rather than adding more tasks.

Evidence:

• "People with ADHD-related planning and task-initiation friction often do not need more tasks. They need a calmer way to turn an overwhelming goal into one clear next action."
• "A planning tool for ADHD-related friction needs clear hierarchy, low cognitive load, and honest product states instead of pretending unfinished automation is complete."

Inference: The positioning is focused on solving a specific problem (ADHD-related planning friction) with a minimalist approach that emphasizes clarity and low cognitive load. It does not claim to be a general-purpose productivity tool.

The description states the app is for people with ADHD-related planning and task-initiation friction. The author also mentions that they are validating the experience with users, but no specific customer segments or personas are defined.

Evidence:

• "People with ADHD-related planning and task-initiation friction"
• "We will validate the experience with users"

Inference: The target customer is likely individuals with ADHD who struggle with initiating tasks or managing complex projects. No explicit ICP (Ideal Customer Profile) is described beyond this.

The description does not provide any information on pricing, monetization, or business model. It is unclear if the app will be sold, offered for free, or have a freemium model.

Evidence: None provided.

Inference: No business model or pricing evidence is available in the self-reported description.

The product is built as a native iOS app using Swift, SwiftUI, and SQLite. The development was accelerated with Codex and GPT-5.6 during OpenAI Build Week. The author notes that the product is intentionally still half-built, focusing on core workflow before AI features.

Evidence:

• "Built a native iOS app with Swift, SwiftUI, and SQLite"
• "Codex and GPT-5.6 accelerated implementation, testing, and iteration"
• "The product is intentionally still half-built. We focused on a reliable local task, project, stage, and step workflow before expanding the AI-assisted features"

Inference: The technical stack suggests a native iOS app with local data storage. The use of AI tools during development indicates an early-stage, iterative approach.

The description states that this is a working alpha, and that the product is intentionally still half-built. There is no mention of users, customers, revenue, or adoption beyond the developer's own validation.

Evidence:

• "This is a working alpha"
• "The product is intentionally still half-built"
• "We will validate the experience with users"

Inference: No traction or maturity data are provided. The project is described as early-stage and under development.

No information is provided about competitors or market positioning beyond the general idea of planning tools for ADHD users.

Evidence: None provided.

Inference: No competitive analysis or context is available in the self-reported description.

• The project is described as a solo effort with no team, which may limit scalability.
• It's an alpha and not fully built, indicating early-stage development.
• No revenue, customers, or traction data are provided.
• The lack of pricing or monetization strategy raises questions about long-term viability.

Evidence:

• "Team size: 1"
• "This is a working alpha"
• "No revenue, customer or traction data is available"

Inference: The solo developer model and early-stage product raise concerns about execution, scalability, and commercial viability.

1. What specific user feedback have you received so far?
2. How do you plan to monetize the app beyond the current alpha?
3. Are there any plans for team expansion or partnerships?
4. What are your timelines for completing remaining features?
5. Have you identified a clear path to user adoption or market fit?