The Case Against Feeds

You know how this goes. You install a read-later app. It's clean and quiet, you save things, it feels like a calm place. Six months later there's a "For You" row, then streaks, then trending saves from people you don't know, and one day you open it and feel — unmistakably — behind.

Apps for keeping things have a strange habit of becoming apps for consuming things. It's worth asking why, because the answer has very little to do with what users want.

The gravitational pull

A feed is the most efficient machine ever built for turning a person's presence into time-on-app. Every metric a growth team runs — retention, session length, daily opens — moves when the home screen pulls you back in. So the saved-items app learns that showing you new things (even your own things, re-shuffled) measurably "engages" better than showing you the shelf you came to reach for.

The product didn't get worse by accident. It got worse on purpose, one A/B test at a time, each test measuring attention rather than usefulness.

Your saves are context, not content

Here's the reframe. A thing you save is not an article waiting to be consumed — it's context for something you're doing or intend to do. The link to the library you'll use, the PDF you'll reference next week, the note that explains why any of it matters in the first place.

Content is consumed and then it's gone. Context is retrieved when you need it, and completely inert otherwise. An app that understands this is a filing system. An app that doesn't is a feed wearing your bookmarks.

The design test we use

One question decides it, and you can run it against any tool you use: does this screen ask anything of you?

A feed demands attendance — an unread count, a "pick up where you left off," a sense that leaving means falling behind. A filing system demands nothing. You arrive with a purpose, you retrieve, you leave. The app's job is to make that retrieval instant and then shut up.

How Bottles is built around it

Bottles is a quiet place for your links, notes and files, and its whole design bends around that test.

No feed, anywhere. Nothing in Bottles counts your unread, nothing is "trending," nothing waits for you at the door. The front page is your own shelf, exactly where you left it.

Two spaces, so nothing muddles. One space for what you keep: bookmarks, files and references, filed properly so you can find them again. One space for what you write: notes and docs that live right next to what inspired them. The two don't bleed into each other, because reading a reference and composing a thought are different jobs that deserve different rooms.

Nothing competing for your attention. The app has no opinion about what you should open next. It's a shelf, not a magazine.

The uncomfortable part

Designing this way means refusing free growth. Feeds work. They genuinely retain better, in the short term, for the same reason slot machines do. Every product that chooses quiet over engagement is choosing to grow slower than it could. We're fine with that — Bottles is a tool you keep for years, and tools you keep for years are the whole point of this studio.

Bottles is live now, at bottles.taohq.org. Open it, save something, and then — this is the feature — feel free to forget about it until you need it. It'll still be on the shelf.