The keyboard killed flow. Gestures bring it back.

There is a specific moment when your workflow breaks. Not when an app crashes. Not when the internet goes down. It is when you search for a keyboard shortcut you cannot remember.

That moment of doubt — “was it Cmd+Shift+K or Cmd+Option+K?” — seems trivial. It lasts less than a second. But it interrupts something fragile: the mental state where you are productive.

The problem with keyboard shortcuts

Keyboard shortcuts are brilliant. They are also fundamentally dependent on declarative memory — the kind that requires conscious effort to retrieve. Every app has its own. Many contradict each other. VS Code, Figma, Arc, Notion: each with its own key language.

The result is a fragmented cognitive map that grows with every tool we adopt. You memorize one set for coding work. Another for design. Another for writing. Over time, the cognitive overhead of managing that map competes with the real work.

The perfect tool disappears. You do not think about it — what you want to happen simply happens.

— Tool design principle

Why gestures are different

Cursor gestures do not depend on declarative memory. They depend on procedural memory — the same kind that lets you type without looking at the keyboard. Once a gesture is embedded, executing it requires no conscious thought.

The difference is fundamental: you are not remembering a command, you are making a movement. The human brain is extraordinarily good at movements. Far better than at memorizing arbitrary key combinations.

Designing for flow, not for function

When we designed Curflow, the central question was not “how do we make gestures accurate?” That was a technical problem with a solution. The question was: “how do we design something that disappears?”

• Recognition does not seek exact shapes — it interprets intent
• Configuration is per-app — the gesture adapts to context
• The engine runs native in Swift — zero perceptible latency
• No notifications, no dashboard, no friction to activate it

Every decision points to the same goal: that after two weeks of use, you do not think about Curflow. You only think about your work.

The real cost of friction

Deep work — the state of deep concentration that produces the best work — is built slowly and destroyed quickly. A Microsoft researcher found that after a 2.8-second interruption, errors in cognitive tasks double. That is the cost of searching for a shortcut.

We are not exaggerating when we say gestures change how you work. We are describing a real reduction in cognitive friction that, accumulated over a workday, changes how much you can produce.

One last thing

The best interface is the one you do not notice. The best shortcut is the one you do not remember learning. That is the promise of Curflow — and it is the reason it is worth building.