← All work 16 / Products

ADHD LIFE OS

I designed an early local-first tool for choosing a next action, keeping focus and picking up again after a rough stretch.

Early build · Pre-release
Role
Founder & product designer
Duration
2026–present
Team
Independent product
Status
Early build · Pre-release

Design for the moment someone comes back

A task list can explain what’s due and still leave someone stuck on how to begin. For ADHD Life OS, I set a design target: the next useful action should make sense within five seconds. That gave me a way to judge what belongs on the screen when someone is tired, distracted or trying to get going again. It’s a target I still need to test with users.

I designed the tool around choosing something that fits the time and energy available, starting a focus sprint and marking what got done. Someone can break down a task offline or park a distraction. For the return after an interruption, I designed a recovery flow that rewards picking the task back up, rather than maintaining an unbroken streak.

Keep the basic support available offline

I chose a local-first architecture so the main workflows can run without a continuous connection. Optional sync uses client-side AES-256-GCM encryption, and the build has no analytics SDK. The implementation spans Vite on the web, Capacitor on mobile and Electron on desktop. It remains a private, pre-release build. Its scope is everyday self-management support for adults with ADHD. Diagnosis and treatment sit outside that scope.

ADHD Life OS / Workflow

How a task becomes a focus sprint

  1. Choose one action

    Use available time and energy to pick a next action.

  2. Start a focus sprint

    Break down the task if needed and park distractions during the sprint.

  3. Mark progress and return

    Record what you finished. After a difficult stretch, the design rewards returning to the task.

Worked explanationFollow a return after interruption
Input
A task remains unfinished after an interrupted focus sprint.
Decision / rule
Choose a next action that fits the time and energy available; break down the task if needed.
Outcome
Start another sprint and record progress. The design treats returning as progress, too.

Scope of this exampleA proposed pre-release experience. Its usefulness in everyday situations still needs user validation.

Designed workflow from the pre-release build.

What I’d do next.

  • Validate whether the next-action and recovery flows help intended users in everyday situations.
  • Complete release validation across web, mobile and desktop before publication.