

Yeah I used that too for a while — it works surprisingly well, but I always felt it’s more of a workaround than something designed for capturing.


Yeah I used that too for a while — it works surprisingly well, but I always felt it’s more of a workaround than something designed for capturing.


Sure 🙂
What I ended up building is basically a very minimal “capture layer”.
The idea is simple: no matter where you are (phone, browser, desktop), capturing something should always be the same action.
In practice:
Everything goes into the same place instantly, without deciding upfront what it is or where it belongs.
No tags, no structure, no “mode switching”.
Just capture first, decide later (or never).
I built it mainly because I was tired of stitching together different tools depending on context.
If you want to take a look: https://github.com/oldany/dropmind


Yeah — that’s exactly the feeling I kept running into.
At some point I stopped trying to adapt existing tools and ended up building something around this idea of “uniform capture”.
It’s basically a very minimal layer where you can send anything (text, links, quick notes, etc.) from any device in one step — without worrying about where it goes or how it’s structured.
Still early, but it’s been working surprisingly well for me in daily use.


Good question — I don’t mean organizing or saving things long-term.
I mean that moment when you see or think something and don’t want to lose it.
Like:
The problem for me is that if capturing that takes more than a second, I often just don’t do it — or I postpone it and forget.
So “capture” is really just that instant: taking something from wherever you are and storing it somewhere with zero friction.


Yeah KDE Connect is great for device-to-device flow, I’ve used it too.
What I always found tricky is that it works really well once you’re already “in the flow”, but not so much as a quick capture entry point.
Like, it helps moving things around — but not necessarily deciding to capture something instantly in the first place.
That’s where I always felt something was missing.


Yeah that makes sense — I ended up with similar setups at some point.
What always bothered me a bit is exactly that fragmentation: different tools depending on what you’re capturing and from where.
It works, but it feels like you’re constantly switching “mode” depending on context.
I keep wondering if capturing should really depend on the destination at all, or if it should be something more uniform.


Pretty much everything 😄
The problem (for me) wasn’t what to capture, but how fast and from where.
I tried things like Linkwarden too — great tool, but still feels tied to specific entry points (browser extension, app, etc.).
What I kept missing was something more “universal”, where capturing is always one step away regardless of device or context.


Yeah that’s actually what I tried at some point too 😄
But I always felt it’s still a workaround — you’re adapting a tool that wasn’t really built for capturing.
The friction is lower, but it’s still there.
I keep thinking there should be something more “native” to this use case, something that sits between devices and apps rather than inside one of them.


Yeah I tried similar approaches too (notes to self, chat apps etc.)
They kind of work, but I always felt they weren’t really designed for this use case — more like a workaround.
What I was missing was something more “frictionless”, where capturing is basically instant and doesn’t depend on context.
Yeah I tried going the “second brain” route too (Trilium, Obsidian, etc.)
What I kept running into is that they’re great once something is already in the system — but capturing still feels like a separate step where you have to think about where it belongs.
I started wondering if capturing should be completely independent from organization, and almost “context-free”.
More like a thin layer you can hit instantly from anywhere, without deciding anything upfront.