Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.

3recommend
0warn against
Jan 3, 2026first mention
Sep 10, 2026latest mention
Nov 25 – Oct 26
Used forgraph visualizationnode graph visualizationpatch editor uinode-based ui in react

Why people recommend it

“which is pretty great for the purpose”

“The visual canvas (React Flow) was a deliberate choice over a form-based UI”

Caveats and dissent

No one in these comments warned against it.

Often compared with

All comments 8

“which is pretty great for the purpose”

I find it disrespectful how you shape React Flow, an open-source library you managed to built something on top and charge people money for. Quoting from your other website (linked from OT website): https://www.overflow.dev/ > React Flow examples show possible approaches, not production coverage. They omit edge cases, performance considerations, and maintenance paths. Overflow gives you the end result: hardened behavi

“The visual canvas (React Flow) was a deliberate choice over a form-based UI”

“The frontend uses React Flow for the graph visualization.”

“The graph visualization is built with React Flow.”

“play with the Web MIDI APIs and React Flow”

“I was writing a React application at work based on React Flow”

Threads where it came up

Data: react-flow.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.

Keyboard shortcuts
j / kNext / previous item
o or EnterOpen selected item
/Search
g hHome
g tTop
g rRising
g cCategories
tToggle dark mode
?This help