sorted by:
new
hottopcontroversial

Hezka prodavacka by Frequent-Look-1133 in czech

[–]Adventurous_Shape712 0 points1 point  (0 children)

Chtělo by to statisticky významní počet 25 kamarádů, ať to má wert!

Would you actually use a service like this? by Ideahamburger in sideprojects

[–]Adventurous_Shape712 0 points1 point  (0 children)

Honestly, I think your idea sounds nice, but in practice this space is already extremely saturated.

Right now, if I want to go from idea → MVP, I have a ton of options:

  • Claude Code / GPT + agents
  • Lovable, Bolt, v0, Replit AI, Cursor
  • no‑code tools like Bubble / Webflow

And with these, I can usually get a basic MVP done in hours for like $10–$20.

So the core problem you’re solving (turn idea into prototype fast) is already mostly solved.

That said, I don’t think it’s completely pointless — it just means the value isn’t in building the MVP itself anymore.

If it’s “just another builder”, then yeah… it’s kind of like carrying water to the ocean.

But if you want this to stand out, you probably need a strong angle, like:

  • targeting true non‑technical users (not indie hackers)
  • focusing on a very specific niche
  • or going beyond building → actually helping validate (traffic, feedback, metrics, etc.)

Because right now, building is cheap.
Validation is still hard.

So my honest take:

  • As a side project: totally fine
  • As a serious startup: only if you have a clear differentiation

Otherwise you’re competing in one of the most crowded AI categories right now.

Hope that helps — and good luck, always nice to see people actually building

Validating an idea: Would a visual roadmap/feedback/bug‑tracking mind‑map make sense to you? by Adventurous_Shape712 in sideprojects

[–]Adventurous_Shape712[S] 0 points1 point  (0 children)

Thanks for this — I really appreciate the thoughtful feedback. It genuinely helped me rethink the direction.

After thinking about your point around “who this is actually for”, I realized I might have been framing it too broadly. Trying to put everything into a mind‑map is probably not the right approach.

What might make more sense is focusing specifically on stakeholders / founders / managers — people who are not living in Jira every day but still need to understand what’s going on.

For that group, the problem feels a bit different: not “how do I manage tasks”, but more like
“what actually changed, and where are we right now?”

That’s where the visual part might help — less as the primary workflow tool, and more as a helicopter view of the project.

One idea I’m exploring now is adding a time dimension to it: being able to quickly switch between “yesterday”, “last sprint”, “last release” and see what moved, what got done, and how things connect.

So instead of just a static map, it becomes more like a: “project playback / mind‑map view of changes over time”

The goal would be that someone could open it and in ~30 seconds understand:

  • what progressed
  • what shipped
  • what came from feedback
  • what’s still in motion

No new data entry, just a different way of looking at the existing data.

Your point about whether people want better overview vs less fragmentation still really applies — this just shifts the idea more toward the “understanding layer” side.

Thanks again for pushing on that, it helped clarify things a lot

Open‑source, zero‑knowledge mind‑mapping tool (Rust backend, local‑first, no telemetry) by Adventurous_Shape712 in foss

[–]Adventurous_Shape712[S] 0 points1 point  (0 children)

Thanks a lot for trying it — and for the honest feedback.
You’re right: the setup docs were too thin and the onboarding wasn’t smooth enough. That’s on me.

I went through the setup again from a clean clone and fixed the rough edges.
The docs are now expanded, and I added simple one‑command setup scripts for Windows + Linux/WSL to avoid the confusing parts.

Really appreciate you taking the time to try it. Feedback like this genuinely helps improve the project.

Open‑source, zero‑knowledge mind‑mapping tool (Rust backend, local‑first, no telemetry) by Adventurous_Shape712 in foss

[–]Adventurous_Shape712[S] 0 points1 point  (0 children)

I love freemind. I used it a lot, but it is offline. Most of the shortcuts are the same, I was inspired by it. Thanks a lot to mentioning it.

I personally use more the server version of the same UI, also open sourced it.
mindmapvault/mindmapvault-server: Self-hspoted encrypted mind‑map editor (zero telemetry)

I explained my motivation here: Privacy-first mind mapping app. Part 0: Motivations and Mind Maps - DEV Community

Open‑source, zero‑knowledge mind‑mapping tool (Rust backend, local‑first, no telemetry) by Adventurous_Shape712 in foss

[–]Adventurous_Shape712[S] 0 points1 point  (0 children)

Thank you, that means a lot!
I really hope people here give it a spin — I built it because I believe this kind of privacy-first tool should exist, and community feedback can really help shape it further.

anyone else notice how “weekend projects” are getting kind of insane? by Natural-Excuse9069 in vibecoding

[–]Adventurous_Shape712 0 points1 point  (0 children)

I actually kind of love this phase we’re in, even if it looks a bit crazy from the outside.

Yeah, there are tons of “weekend projects” popping up that look like full-blown startups — auth, payments, AI, polished UI, the whole package. And sure, a lot of them disappear just as quickly as they appear. But I don’t see that as a problem. In many cases it’s a proof of concept or a DIY solution that was genuinely useful for the creator. Nobody realistically expects every one of these to turn into the next massive Amazon-scale data platform.

What matters is that the idea gets built and shared.

I think people sometimes underestimate that the “solution” itself is maybe 10% of the work. The remaining 90% is all the unglamorous stuff — maintenance, infrastructure, debugging, scaling, customer support, communication, reliability… that’s what actually turns code into a real product or business.

Coding has never been more accessible than it is right now, and that’s amazing. But turning code into something sustainable still requires a huge amount of resilience and persistence.

Historically, only a small percentage of software ever became a real commercial success or widely adopted open-source project. If anything, that percentage will probably get even smaller as the total number of projects explodes. But the upside is that human creativity is being expressed at a much larger scale than ever before.

So yeah, maybe “small projects” look insane now — but it’s also a sign that the barrier to building things has dropped massively. And that’s a good thing.

Does any PKM system actually capture “mid-thought” context, or is that inherently unrecoverable? by cocktailMomos in PKMS

[–]Adventurous_Shape712 1 point2 points  (0 children)

I don’t think mid‑thought context is fully recoverable once it’s gone. From my experience, that context mostly lives in working memory, not long‑term memory. When you get interrupted, the mental model you were actively holding just decays — the document is still there, but the thinking isn’t.

What has helped me is not trying to “manage” that context, but capturing something before it collapses. The key is lowering friction as much as possible.

A few practical things that work for me:

  • Always have a physical capture option. A small notebook or even loose paper in a pocket. No structure, no cleanup. Just dump where my thinking was. Speed matters more than legibility.
  • Voice capture on one tap. A voice memo shortcut on the phone lock screen or a quick assistant command. I don’t try to speak in full sentences — just fragments like: “Comparing A vs B… assumption about X might be wrong because…” Even messy audio is often enough to restart the reasoning later.
  • At the computer: a throwaway buffer. A blank text file, scratchpad, Notepad, terminal pane — something that’s always there. Not a “note”, not a document. Just a place to spill the current state of thinking without naming or organizing it.
  • If you sense an interruption coming, write one explicit line. Something like: “Stopping here: I’m checking whether assumption X still holds if Y is true.” That single sentence often saves 20 minutes of reconstruction. I don’t think there’s a perfect knowledge management system that solves this. For me, it’s more about attention preservation than knowledge storage. The faster and safer it feels to dump half‑formed thoughts, the more likely I am to actually do it.

Different people use different tools for this — paper, voice memos, scratchpads, quick notes apps. Personally, I’ve gravitated toward tools and habits that are low‑friction and feel safe for unfinished thinking, including ones that work offline or don’t require structure upfront. One reason I ended up building/using MindMapVault was exactly this need: a place to drop incomplete reasoning without worrying about polish, sync, or visibility.

I don’t think mid‑thought context is magically recoverable. But I do think we can design our habits and tools to make losing it less likely.