# 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:** 8\
**Page:** 6

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [20 August 2025 20:21 UTC](https://discourse.nodered.org/t/node-red-survey-shaping-the-future-of-node-reds-user-experience/98346/101 "2025-08-20T20:21:25Z")

</div>

Sounds like a sensible enhancement.

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [21 August 2025 08:00 UTC](https://discourse.nodered.org/t/node-red-survey-shaping-the-future-of-node-reds-user-experience/98346/102 "2025-08-21T08:00:07Z")

</div>

> [@Steve-Mcl](#):
>
> and error checking will be available

Don't forget that its role is also to check that each node has the required properties. Of course, this is still possible with the editor.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [21 August 2025 08:06 UTC](https://discourse.nodered.org/t/node-red-survey-shaping-the-future-of-node-reds-user-experience/98346/103 "2025-08-21T08:06:09Z")

</div>

> [@GogoVega](#):
>
> Don't forget that its role is also to check that each node has the required properties

I assume you mean that the JSON is an array of objects with `id` and `type` right? (since Node-RED flow validation is not declarative/schema driven)

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [21 August 2025 08:07 UTC](https://discourse.nodered.org/t/node-red-survey-shaping-the-future-of-node-reds-user-experience/98346/104 "2025-08-21T08:07:42Z")

</div>

Yes that's it

---

<div class="post-metadata">

**Author:** ![dimitrieh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dimitrieh/32/101708_2.png) [@dimitrieh](https://discourse.nodered.org/u/dimitrieh)\
**Post date:** [21 August 2025 08:24 UTC](https://discourse.nodered.org/t/node-red-survey-shaping-the-future-of-node-reds-user-experience/98346/105 "2025-08-21T08:24:31Z")

</div>

Hi everyone 👋. I am back from OOO these last 7-8 days. \*\*

Small update:\*\* The survey has been closed down now. The findings will soon be shared through Node-RED’s social channels :). Discussion can continue as normal here!

---

<div class="post-metadata">

**Author:** ![travisp](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/travisp/32/103702_2.png) [@travisp](https://discourse.nodered.org/u/travisp)\
**Post date:** [6 October 2025 18:10 UTC](https://discourse.nodered.org/t/node-red-survey-shaping-the-future-of-node-reds-user-experience/98346/106 "2025-10-06T18:10:40Z")

</div>

I use Node Red for more complicated automations alongside my Home Assistant install for my smart home. Although Home Assistant works ok for me for simpler things, the approach they've taken makes it not suitable for anything too complicated.

However, one area where it has a real advantage is that it's very easy to go back and see what happened:

 ![Screenshot 2025-10-06 at 2.03.07 PM](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/5/f50e479f6fb2356f0807d703704f0da9ee6d775b.png)

I find that debugging node red is much more difficult. Yes, I can add debug nodes (to watch live) and logging (to go back and look at retroactively), but it's not easy to notice that something didn't work right and then go back and see what happened. It's also not really possible to monitor subflows except for via logging.

For me, this is the biggest downside I have using Node-RED, and every flow I build I weigh my preference for building in node red versus the likely easier debugging I will get in my other system. I have plenty of software development experience, so I don't necessarily need a low code editor, but I find Node Red a nice way of managing and overseeing automations, and much superior to Home Assistant. For a low-code system like Node-Red, however, I would love to see a low-code method of debugging (rather than filtering and wading through hundreds of manually added log lines).

---

<div class="post-metadata">

**Author:** ![AllanOricil](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/allanoricil/32/106911_2.png) [@AllanOricil](https://discourse.nodered.org/u/AllanOricil)\
**Post date:** [6 October 2025 18:47 UTC](https://discourse.nodered.org/t/node-red-survey-shaping-the-future-of-node-reds-user-experience/98346/107 "2025-10-06T18:47:49Z")

</div>

Dont worry. As soon as I finish my library for writting nodes, my next goal is a tracer. Differently than the debug window, it will be possible to filter by "transactions", subtransactions and so on. It is just an idea and I have to validate if it is feasible.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [5 December 2025 18:47 UTC](https://discourse.nodered.org/t/node-red-survey-shaping-the-future-of-node-reds-user-experience/98346/108 "2025-12-05T18:47:53Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/node-red-survey-shaping-the-future-of-node-reds-user-experience/98346.md?page=5)