A plea: share designs for feedback with the community before implementation #7188
Description
Please start sharing designs with the community before implementing. We have seen some insane changes to the UI such that it feels like whoever is making these suggestions and changes doesn’t actually use Comfy at all. Or it similarly feels like 5 competing interns making it up as they go along without any consideration. Constantly moving buttons and introducing disparate paradigms is incredibly confusing and does not offer value. These changes spit in the face of accessibility and make the experience worse. I’m not just talking about in nightly - the “stable” release is jarring and has only caused me headaches without addressing actual existing bugs.
The one saving grace and amazing feature has been subgraphs. Getting back to fundamental improvements to how we build workflows and fixing bugs should ideally be the focus.
The Vue Nodes 2.0 work is nonsense. I tried them and it BREAKS most custom node packs, destroys accessibility, and is insanely ugly and unusable compared to the existing litegraph nodes. I can’t see any benefits they offer if backwards compatibility and accessibility aren’t even considered. Further - given how awful they are how is it possible they are enabled by default on stable? That sort of change should be opt in, not default when it is clearly still half baked.
I know this sounds like a lot of complaining, and it is. It’s from frustration in trying to focus on building gen AI workflows and not worrying about which button will disappear next or which new overlay will block half my screen on mobile. So PLEASE get a competent principal designer and start sharing designs far ahead of time for community feedback rather than moving things around, back and forth haphazardly. I think we are getting to a point where if this keeps happening we will start to see more stable forks of the UI get preferred by users.
┆Issue is synchronized with this Notion page by Unito