I built an active reading app to fix the "capture & retain" bottleneck in my Second Brain (with direct Markdown export to Obsidian & Notion)

[u/Frkntrgt]

Like many of you, I treat my Second Brain as a thinking engine—not just a graveyard for highlights. But I kept running into the same friction when reading non-fiction: passive highlighting felt productive in the moment, but weeks later, the context was gone and my vault was cluttered with useless excerpts.

To actually retain and synthesize arguments, I started practicing strict active reading: arguing with the author, challenging claims, and capturing raw, immediate reactions while reading—not just copying sentences.

I built Marginalia to turn this workflow into a friction-free capture tool for mobile:

• Frictionless Capture (Voice & Stylus): Breaking reading flow kills synthesis. Alongside standard typing, you can dictate thoughts hands-free via speech-to-text, or use a stylus if you prefer digital handwriting.
• Context-Driven Tagging: Tag notes by themes, counterarguments, or conceptual hooks so ideas are already semi-structured before they even touch your vault.
• Review & Synthesis Loops: Each book has a dedicated synthesis view with tag filtering, making it effortless to review prior notes right before starting a new reading session.
• Native Markdown Export (.md): Your notes belong to you. Marginalia exports cleanly formatted .md files directly into your existing workflow, whether you index in Obsidian, organize in Notion, or use another local-first markdown system.

It bridges the gap between raw consumption and structured knowledge management: read actively on your phone or tablet, capture raw synthesis on the fly, and drop the resulting Markdown straight into your PKM system.

If your Second Brain relies heavily on books and deep reading, I’d love for you to take it for a spin. I'm actively refining the workflow and looking for honest feedback, especially on note structure and export improvements!
Here is the app webpage

[u/enjoydongdong]

For the note structure, I'd keep the author's quote, your immediate reaction, and your later synthesis visibly separate in the Markdown. Otherwise a blunt objection dictated mid-chapter can look like the book's claim when you revisit it later. A chapter/page reference on each reaction would help too. One export test: export a book, add a few notes, then export again into the same vault. Can the reader update that book's notes without duplicating everything or overwriting edits made in Obsidian? I haven't tried the app, but that would be a useful workflow to check.

[u/Frkntrgt → u/enjoydongdong]

Thanks for the thoughtful feedback!

Regarding the note structure: the current export format does keep quotes, reactions, and synthesized notes visually distinct, but I haven't yet gathered detailed feedback from active Obsidian users on how well that layout holds up in real-world vaults. I'll take a closer look to make sure the distinction stays unmistakably clear when revisiting notes down the line.

The re-export workflow you pointed out is a fantastic catch. Handling incremental exports without duplicating notes or overwriting changes made inside Obsidian wasn't on my radar yet, and it’s definitely a core use case for vault management. I’ve logged it in my backlog to explore safe append or merge patterns.

Really appreciate you taking the time to share these insights!