From the workshop

Why SaneFocus Exists

Published by JP Forge Studio. Updated .

SaneFocus started with a very small annoyance: needing somewhere to put a thought without leaving the thing I was already doing.

Most notes apps are good at becoming a place. They have folders, documents, sidebars, sync status, search, templates, and enough room to build a second brain if that is what you want.

That is useful work. It is also not the moment SaneFocus is built for. The moment is smaller: a follow-up appears while coding, a link needs to be parked for the next hour, or a TODO needs to get out of your head before it interrupts the task in front of you.

A scratchpad, not another workspace

I wanted a note window that opens quickly, accepts the thought, and disappears without making me manage it. The app should feel closer to a clean edge of the desk than a filing cabinet.

That is why SaneFocus is intentionally small. The fixed tabs are there for a few active contexts, not infinite organization. The shortcuts are there because reaching for the mouse can be enough friction to lose the thread. The notes stay local because quick capture should not begin with account setup.

The product line

SaneFocus should earn every feature by protecting the same loop: open, capture, return. If something makes that loop heavier, it probably does not belong.

The goal is not to replace your main notes app. It is to protect the fragile little moment before a thought disappears, while letting you get back to the work that created it.

Back to all workshop notes