Dashboard and UIs for Node-Red (opens in new tab)

Hi, I'm the lead developer on FlowFuse's Dashboard - thanks for the question.

We have had to restart the project from scratch due to the original Node-RED Dashboard's (I'll call this Dashboard 1.0) Angular 1 dependency. We couldn't fork.

That being said, because of how widely adopted and popular Dashboard 1.0 is, we wanted to make sure we mimicked that user experience as much as possible, so that users familiar with 1.0 felt comfortable with 2.0, but still ensured we made improvements in areas, where appropriate. Hence, there is a lot of crossover with the same, familiar nodes (plus a fair few more).

FlowFuse are actively developing and supporting Dashboard 2.0, and it's here to stay. It can be considered the "official" next phase of Dashboard 1.0. Nick, the co-creator of Node-RED, is FlowFuse's CTO, and FlowFuse ourselves are contributing heavily to the Node-RED project.

I wrote this up today: https://flowfuse.com/blog/2024/06/dashboard-1-deprecated/#wh... which gives a summary of the key differences, what we have planned, and how to get started.

> The original Node-RED Dashboard is based on Angular v1, which is no longer maintained. Although small patches have been and will continue to be applied on a "best can do" basis, there will be no major feature upgrades. The lack of ongoing maintenance and updates has the potential to lead to underlying security breakages, a risk we are not comfortable taking. We have recognized the need to innovate and adapt, which is why we are creating a completely new project to replace the existing Node-RED Dashboard.

https://flowfuse.com/blog/2023/06/dashboard-announcement/

The original ("v1") Node-RED Dashboard is now deprecated

https://discourse.nodered.org/t/node-red-dashboard-v1-deprec...

From what I understand the original dashboard is based on Angular v1 which is not maintained anymore.

This would be the main reason for the rewrite...