# Node-RED Survey: Shaping the Future of Node-RED's User Experience

**URL:** <https://discourse.nodered.org/t/node-red-survey-shaping-the-future-of-node-reds-user-experience/98346>\
**Category:** News\
**Created:** [28 July 2025 10:46 UTC](https://discourse.nodered.org/t/node-red-survey-shaping-the-future-of-node-reds-user-experience/98346 "2025-07-28T10:46:15Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![gregorius](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gregorius/32/73816_2.png) [@gregorius](https://discourse.nodered.org/u/gregorius)\
**Post date:** [28 July 2025 15:53 UTC](https://discourse.nodered.org/t/node-red-survey-shaping-the-future-of-node-reds-user-experience/98346/18 "2025-07-28T15:53:23Z")

</div>

> [@MyRandomThoughts](#):
>
> The problem with having people share their code is that you still need to wade through 1000's of entries for something that may do half of what you want.

Something that somehow doesn't happen at GitHub or GitLab or Sourceforge or SourceHut where software is shared successfully _and_ simply.

I think there is a lack of imagination of how to do this _right_ for visual code is the issue here.

There are no problems in sharing code, the problems lie in seeing the solution of proper, well indexed and searchable visual code repository. It's solving the issues that is hard. But - as many social code websites prove - it's possible.

> [@dimitrieh](#):
>
> Could you elaborate here?

Have a look at what I have done with FlowHub - install the [nodes](https://flows.nodered.org/node/@gregoriusrippenstein/node-red-contrib-flowhub), create a github token and try it out in Node-RED. I also created some [screencasts](https://blog.openmindmap.org/blog/introduction-to-flowhub) explaining flowhub in more detail how and for what to use it.

Which actually brings me to a third wish (after all there are three wishes with each good genie!) that creating nodes was easier and doable within Node-RED itself. Again, I created my own solution using [NodeDev](https://flows.nodered.org/node/@gregoriusrippenstein/node-red-contrib-nodedev) but that's perhaps not _the_ solution rather an attempt at a solution.

P.S. I come from a developer background so I'm not the "normal" user of Node-RED, hence my "frustration" at the lack of "developer" tooling around Node-RED. Just between the two of us, I see Node-RED as a glorified Emacs 😉 As such, I want to extend my editor _using_ my editor.

P.P.S. all the tooling I created, I use daily. So I'm doing a lot of dogfooding. I can't stand the taste of it any longer!

---

_[View the full topic](https://discourse.nodered.org/t/node-red-survey-shaping-the-future-of-node-reds-user-experience/98346)._