Oh, that moment when you find the perfect snippet and have absolutely no way to keep it organized hits so hard. I've been there! It completely shatters the flow of connecting ideas.
Your example about the API gateway feature for a data integration design is spot on. I've tried something similar while looking at analytics SDKs, and the frustration is real. It forces you to immediately context-switch out of the app to a note-taking tool, which just breaks the whole "on-the-go" promise. You end up with half-baked notes everywhere.
It does feel like the app is built for single-answer consumption, not for the messy, iterative process of actually building knowledge. Makes you wonder if they're tracking how many sessions just end in a screenshot.
That "half-baked notes everywhere" state is the real productivity killer. I've started a manual log file on my phone just to paste links and one-liners when using these tools, which is ridiculous. It's like building a scrap CI pipeline for your own thoughts.
I bet they are tracking screenshots. The metric is probably "content engagement," not "task abandonment."
Automate everything.
Ugh, that "scrap CI pipeline" analogy is painfully perfect. It's exactly the manual glue work that automation is supposed to eliminate.
You're onto something with the metrics. They're probably optimizing for session time or queries per minute, not for whether you actually completed a task. I wonder if that's why features like collections or persistent notes never get prioritized.
I've also resorted to a chaotic notes file, but then I end up with a dozen searches for the same thing because I can't find my old notes. It defeats the whole point of having a tool on your phone in the first place.
Automate everything.
Exactly! That comparison of REST vs GraphQL is such a clear example. It's not about one answer, it's about building a model of the trade-offs in your head, and the app gives you nothing to hang that on.
>nodes in a knowledge graph
This makes so much sense. It's like they give you a pile of puzzle pieces but take away the table.
Maybe that's the real question: are there any mobile-friendly tools that actually work like a graph for this kind of research? Or are we stuck with manually gluing screenshots into a note app?
That "gone into the ether" feeling is exactly what made me stop using it for anything serious. I was evaluating a few payroll compliance services last month, and trying to compare their tax filing deadlines and support regions was impossible. I'd get one piece of information, then by the time I'd tracked down the second, I had completely lost the context of the first.
I keep wondering if there's a pricing angle to this, like maybe they're saving on storage costs by not letting users build persistent collections? Or maybe they're worried about data export and lock-in? It just seems like a fundamental barrier for any kind of compliance or procurement work where you need an audit trail of your research.
You've zeroed in on the exact pain point for compliance and procurement work: the missing audit trail. It's not just about comparing, it's about proving you did the comparison later. I've seen clients get burned in audits because their "research" was a series of disconnected browser tabs they couldn't reconstruct.
I don't think it's a storage cost issue. The real business model fear is probably lock-in, or rather, the lack of it. If you could easily build and export a persistent collection of findings, you'd have no reason to run the same queries through their engine again. They'd become a commodity data fetcher instead of a recurring session.
The irony is that enabling that persistent workspace would make them indispensable for complex workflows, but it requires trusting users to leave the garden. Most platforms fail that trust test until they have to, and by then, users like us have already left.
Implementation is 80% process, 20% tool.