What Gravity Isn't For (And Why That Might Be the Point)

Gravity doesn't have folders. It doesn't have tags. There's no plugin ecosystem, no bidirectional links, no knowledge graph visualization, no daily notes template, no Zettelkasten workflow, no API for third-party integrations.

If you're keeping score, that's a lot of missing features.

Every one of those features solves a problem created by the previous feature. And at some point, you have to ask whether the problem being solved is "I need to capture and use my thoughts" or "I need to maintain this system I built to capture and use my thoughts."

The feature treadmill

A pattern I've seen play out dozens of times:

You start with a simple system. Maybe Apple Notes, maybe a text file. It works. Then you hit a limit: too many notes, can't find things, no structure. So you upgrade to something more powerful. Notion, Obsidian, Roam. You get folders. Tags. Linked references. A graph view that makes your knowledge look like a neural network.

For about three weeks, this feels like a superpower.

Then the weight starts. You're not just capturing ideas anymore. You're maintaining a system. Which folder does this go in? Should I tag this #ideas or #projects or both? Wait, I created a new tag last week that might apply. What was it called? This note references that note, but should the link be bidirectional? The graph is getting cluttered. Maybe I need to reorganize.

The tool that was supposed to free your thinking now occupies your thinking.

I'm not saying these features are useless. For some workflows (academic research, complex project management, collaborative wikis) they're genuinely necessary. But for personal note-taking? For capturing what's on your mind so you can move on with your day?

The features become the friction.

What Gravity doesn't do (and what that saves you)

What's not in Gravity: no folders, no tags, no note linking, no templates, no plugins, no export-to-47-formats matrix. Notes sync across your Apple devices, live in one stream, and that's it.

Reading that list, you might think: "So it's just... worse?" The point is that each "missing" feature removes a specific kind of overhead.

Folders force permanent placement decisions and usually collapse into one of three states: careful hierarchy with ongoing upkeep, chaotic hierarchy, or an always-full "unsorted" bucket. Tags remove hierarchy but add taxonomy drift (#idea vs #ideas, #projectX vs #project-x) and require future-retrieval prediction at capture time. Links and graphs can be useful in research-heavy workflows, but for everyday notes they often become architecture you maintain more than you use.

Gravity's alternative stays the same across all of it: one stream, optional plain-text prefixes (todo:, read:), and nothing structural you have to keep alive.

The cost of "power"

There's a recurring pattern here. Every "power feature" solves a problem by adding complexity. Then the complexity becomes a problem, and the solution is another power feature.

Folders create rigid hierarchies, tags cross-cut them, tags proliferate, search becomes mandatory, search overload pushes you to links, links clutter, filtering/views appear to manage the clutter, and eventually you're maintaining views.

It's not that any single feature is bad. It's that they compound in a specific direction: toward more system, more overhead, more decisions per thought captured.

Meanwhile, the original goal is to get ideas out of your head quickly so you can think about other things. That goal recedes behind the interface.

What Gravity is for (precisely)

Gravity is for one thing: capturing thoughts with zero friction and trusting that what matters will surface.

That's it. Open the app, you're already typing. Your thought goes to the top of the stream. Close the app. Done.

When you review, you scroll. If something catches your eye, an idea still alive, a todo still relevant, you swipe right and it jumps back to the top. Everything else keeps sinking.

There's no system to maintain because there's no system. The stream is the system. Time and attention do the organizing.

This means Gravity is specifically not for project management (dependencies, timelines, assignments), team collaboration, research wikis with dense interconnections, or long-form writing.

What remains is a tool for the most common note-taking use case: a place to dump what's on your mind, fast, so you can focus on whatever comes next.

The real question

Here's the thing I keep coming back to: why do we take notes?

The conventional answer is retrieval. You write something down so you can find it later. Therefore, the tool should help you find things. Therefore, organization features.

But most notes aren't retrieved. They're written once and never looked at again. The ones that do matter tend to surface naturally. You remember them because they're still on your mind, or you stumble across them while looking for something else.

What if the real function of note-taking isn't retrieval? What if it's relief, offloading thoughts from working memory so you can focus on the present moment?

In that frame, the best note-taking tool isn't the one with the best retrieval system. It's the one with the lowest capture friction. The one that gets out of your way fastest.

Gravity is built for that frame.

Who this isn't for (genuinely)

Let me be honest: if you love building intricate systems, if the act of organizing brings you joy, if your work genuinely requires complex knowledge management, Gravity isn't your tool.

Some people thrive with Obsidian vaults and Notion databases. The organizational overhead isn't a cost for them; it's part of their process.

That's real, and Gravity isn't trying to serve that use case.

But if you've ever felt like your note-taking system became a second job... if you have more empty databases than full ones... if you suspect that reorganizing is procrastination in disguise...

Then maybe the problem isn't that you haven't found the right system yet.

Maybe the answer is less system altogether.

Gravity is what that looks like.