# 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:** 49

<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:** [1 August 2025 20:52 UTC](https://discourse.nodered.org/t/node-red-survey-shaping-the-future-of-node-reds-user-experience/98346/49 "2025-08-01T20:52:40Z")

</div>

> [@TotallyInformation](#):
>
> needs to be crammed into Node-RED

Amen to that. Or as they say today: true that. Or 100% this.

Total agree. Please don't cram this stuff into Node-RED.

Less is more when it comes to Node-RED.

Open up the internal APIs so that node packages can do more, things like being able to gets a heads when Node-RED starts/stops/restarts/flows reload, clearly defining when the lifecycle of a plugin begins, accessing the events when messages get passed around.

---

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