Gravity's Missing Features Are the Product

Someone recently asked me why Gravity doesn't have folders.

My first instinct was to say "we'll add that eventually." Then I caught myself. We're not adding folders. We're not adding tags either, or bidirectional links, or a plugin system, or templates, or a knowledge graph.

These aren't items on a roadmap we haven't gotten to yet. They're deliberate omissions. The missing features are the product.

The retrieval assumption

Every note-taking app makes the same assumption: the hard problem is finding things later.

If retrieval is the goal, then organization is the solution. Folders help you browse. Tags help you filter. Links help you navigate. Search helps you query. Each feature exists to solve the retrieval problem.

But most notes are never retrieved.

Think about the last 100 things you jotted down. How many did you actively go looking for later? For me, it's maybe 5-10%. The rest served their purpose in the moment of capture: offloading from working memory, clarifying a thought by writing it down, creating a record I could theoretically access but never actually do.

If 90% of notes exist purely for the relief of capturing them, then optimizing for retrieval is optimizing for the wrong thing. You're building elaborate infrastructure for a use case that rarely happens, while adding friction to the use case that always happens.

Gravity inverts the assumption. The hard problem isn't retrieval. It's capture, specifically, making capture so fast and frictionless that you actually do it consistently.

What organization features cost you

Folders look sensible until they force placement decisions on every note: Work/Projects/ProjectName, Work/Reference, Personal, maybe a new "half-formed ideas" bucket. You spend 5-15 seconds classifying a thought that took 3 seconds to have, a small paradox-of-choice tax that compounds. Months later, you still have to remember where you filed it.

Tags fix hierarchy but create taxonomy maintenance: #ideas, #idea, #thoughts, #concepts. At capture time, you're betting Future You will remember the exact label. Usually Future You doesn't, the tag pool drifts, and the system decays. Asking for taxonomic precision when you're trying to get a thought out of your head is backward.

Links and graphs create the same pattern at a higher level. You can connect Note A to Note B and build an impressive web, but each connection is another maintenance decision ("should this connect to existing clusters?"), and for daily capture it can turn into a side job. For research workflows synthesizing large source sets, that overhead can be worth it. For most people, it isn't. Gravity's answer across all three: one stream, optional text prefixes (todo:, read:), no forced structure.

The feature treadmill

The pattern is predictable: start simple (text file, Apple Notes), hit a retrieval panic ("I can't find anything"), add structure (folders/tags), hit new friction (sprawl/inconsistency), add more controls (search/filters/views), then add meta-controls (templates/plugins/workflows) to manage the controls, until you realize you're maintaining a system instead of taking notes and either reset to simple or burn out.

This isn't a failure of any specific app. It's an inevitable consequence of optimizing for retrieval in a domain where retrieval isn't the core job. Software engineers have a name for this pattern: YAGNI (You Aren't Gonna Need It). Most features added "just in case" create more cost than value.

The more retrieval power you add, the more organizational overhead you create. The more overhead, the more friction at capture time. The more friction, the less you actually capture.

Gravity's constraint

Gravity has one job: minimize the time between "I have a thought" and "the thought is captured and I can move on."

Every feature decision flows from that constraint: no folders because placement decisions add time and cognitive load; no tags because taxonomies create friction and inconsistency; no linking because graph-building is a separate activity; no templates because capture is unstructured; no plugins because a fixed surface keeps thinking overhead low.

The result is an app that does less. Deliberately. Because doing less enables the one thing that matters to happen faster.

What Gravity is for

The specific use case:

You have a thought. Any thought. A todo. An idea. A quote. A reminder. A fragment you don't want to forget. You capture it immediately, with zero decisions about where it goes or how to categorize it, and move on with your day. The thought is out of your head and somewhere persistent.

Later, minutes, hours, or days later, you scroll through your stream. Most things sink toward the bottom, exactly as they should. But some things catch your eye: ideas still alive, todos still relevant, half-thoughts that suddenly connect to something else. You swipe right, they jump to the top. Rescued.

The entire interaction model: append, review, rescue. Everything else that note-taking apps offer (folders, tags, links, graphs, templates, plugins) is deliberately not here.

Gravity is not for complex project management (Gantt charts, dependencies, assignments), research synthesis at dissertation scale, collaborative workspaces, or long-form drafting.

These are genuine limitations. If your work requires these capabilities, Gravity isn't just suboptimal. It's wrong for you.

But notice that all these use cases have something in common: they're not really about capturing thoughts. They're about organizing information, managing complexity, or producing artifacts.

If what you actually need is a low-friction thought capture tool... the "missing features" stop looking like limitations and start looking like the point.

The question to ask yourself

A useful diagnostic:

In the last month, how much time have you spent inside your note-taking app organizing, categorizing, linking, or restructuring, versus actually capturing and using thoughts?

If the ratio tilts toward maintenance, your tool is eating your attention. More features won't help. More features will make it worse.

What helps is removing the overhead. Using a tool that has nothing to maintain. Trusting that what matters will surface naturally, without you having to architect the surfacing.

Gravity is what that philosophy looks like as an app. One stream. No structure. Let time and attention do the organizing.