I Tried 17 Second Brain Apps. Here's What They All Get Wrong
An honest editorial autopsy of the second brain app category — the two fatal flaws (manual capture, locked-in AI), how each tier commits them, and what the category actually needs next.
By BrainTube Team · · 12 min read
Seventeen apps, five years, roughly the price of a decent used car in subscription fees. The apps got prettier every year and the outcome got worse. Two failures kept repeating across every tier — the workspace giants, the local-first vaults, the AI-notes upstarts, the research notebooks, the developer-facing memory SDKs. This is what I actually learned, category by category, without the diplomatic hedging.
Failure 1 — Manual capture assumes discipline you don't have
Every app in this category asks you to do the organising you're already failing at. The onboarding shows a clean workspace with three neatly nested pages and asks you to build the rest. Nobody does. The friction of stopping to file a video after watching it, or to paraphrase a podcast into a note, is exactly the friction that made you save the video in the first place instead of engaging with it. Tools that require ongoing user effort become archaeological sites — pretty, layered, dead.
Failure 2 — Locked-in AI turns every save into a rental
The apps that added AI in 2023–2024 all made the same choice: the AI lives inside the app. Notion AI works on Notion pages. NotebookLM works on notebooks. Recall's chat works inside Recall. This is fine until the model landscape shifts — which it does every few months — and now your knowledge is trapped where the best AI isn't. You built the corpus once; you can only use it in one place. That's not ownership, it's tenancy.
Workspace giants — powerful, but AI locked inside
Notion is the most capable app in the lineup. Its database model is genuinely great; the team wiki story is unmatched. The failure mode is not the tool, it's the physics of where the AI lives. Notion AI reads Notion; nothing else does. You end up with your best-organised knowledge visible only to the assistant most tightly coupled to a workspace tool, not the assistant that's currently ahead on reasoning. Not Notion's fault — a category-wide pattern — but the consequence is the same: your workspace is a walled garden with excellent gardening tools.
Local-first vaults — you become the maintainer
Obsidian is the beloved counter-example: everything is your file, forever, in Markdown. It's true and it matters. What the fandom softens is the maintenance load. Backlinks decay, tags drift, plugin conflicts compound, and the vault becomes a second job. AI features exist through plugins of uneven quality and unclear futures. If tending the vault is the point for you — some people genuinely love the practice — this is heaven. If you were hoping the vault would tend itself, it won't.
AI-notes apps — organise well, capture little
Mem and Reflect are the polished modern take: fast, beautiful, backlink-heavy, with an assistant built in. Both are excellent at helping you find what you wrote three months ago. Both share the second-brain original sin: capture is manual. If you didn't type it in, it isn't in there. The assistant is genuinely useful and genuinely locked to the app. Migration path out is uncertain because the value isn't the notes, it's the graph the app built on top of them.
Research notebooks — excellent, but Google-only
NotebookLM is the rare app that gets grounded, cited AI answers right. When you dump 20 papers into a notebook and ask a real question, it responds like an intern who actually read the papers. The failure is scope: it's Google's, it's session-bounded, and the corpus doesn't leave. You can't build a lifelong personal library in NotebookLM; you build one project's corpus at a time. Perfect for a thesis chapter; wrong shape for the thing you're actually trying to have.
Dev memory SDKs — memory for agents, not for people
Mem0, Zep and Letta are the developer-facing side of this space: memory primitives you wire into your own AI product. They're good at that job. They are not, and don't claim to be, consumer knowledge tools. If you're an engineer, they're excellent building blocks. If you're a person trying to make sense of what you watched last month, they're the wrong shape — you'd have to build the app the shape suggests, and you already have work.
What the category actually needs next
Two things. Capture that builds itself — a system that ingests what you already watch, listen to and read without asking you to file it. If the user has to organise, the tool has already lost. And memory that travels with you — a corpus that speaks an open protocol (MCP today), so whichever AI you're using this quarter can query it. Together those two properties would fix both failure modes described above. This is the standard to hold any second brain app to — including ours. If a tool doesn't clear both bars, it's another beautiful archive you'll abandon in 18 months. BrainTube tries to clear them, and we invite the same scrutiny.
FAQ
Aren't you biased? Yes — BrainTube is the tool we built, so we have skin in the game. That's exactly why the standard above applies to us too. If we quietly locked the corpus behind our own chat surface tomorrow, we'd be committing failure 2, and readers should call us on it. Doesn't ChatGPT Memory solve this? No. Memory in ChatGPT is short, opaque, and locked to ChatGPT. It personalises the assistant; it doesn't give you an inspectable, portable corpus of what you've consumed. What about pure LLM context windows? Long context helps within a session. It doesn't survive across sessions or across tools. Persistence and portability are separate problems from context length.
Takeaways
- Every second brain app fails on one of two axes: manual capture or locked-in AI. Most fail on both.
- Workspaces and vaults are strong tools, but keep AI inside their own walls.
- AI-notes apps organise well, capture little; research notebooks nail retrieval but stay session-scoped.
- Developer memory SDKs are memory for agents, not for people.
- The category needs auto-capture + open-protocol portability. Judge every app — including BrainTube — by that bar.
Try BrainTube on your own corpus
Free tier, no card. Export anytime.
More to read
- Stop watching videos. Start querying them. — The 60-minute video you bookmarked won't get watched. But the four answers buried in it will get used — if you can pull them on demand.
- How to build a second brain from your YouTube history — A practical workflow for turning years of passive watching into a knowledge graph you can actually use.
- MCP, and why your personal knowledge graph is suddenly worth something — Model Context Protocol turns your private corpus into a first-class citizen for Claude, Cursor and every agent shipping next year. Here's what that means for the way you save.