Comfy-Org / Comfy-Org/ComfyUI_frontend
Difficulty ensuring workflow stability and providing user guidance within AppMode
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 699
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 490
Description
### What problem are you experiencing?
The current AppMode implementation lacks the necessary constraints and documentation layers to make workflows "production-ready" for non-technical users or artists.
Specifically:
- Lack of Input Validation: Without the ability to define boundaries (Min/Max/Step), it is very easy for a user to input values that cause the generation to fail, produce artifacts, or exceed hardware VRAM limits (e.g., setting latent dimensions too high or CFG values to extremes).
- Lack of Contextual Guidance: Complex workflows often have specific parameters that require explanation. Without a space for a high-level description or per-parameter tooltips, users are forced to refer back to external documentation or the original node graph to understand the intended use of a field.
### When does this problem occur?
This issue occurs whenever a "Power User" or "Workflow Builder" prepares a tool for a "Creative User":
- During Handoff: When an artist opens the AppMode interface and is presented with a "Seed" or "Scale" slider without knowing the safe operational range.
- Onboarding: When a new user tries to use a specific AppMode template and doesn't understand the nuance between two similar-looking text fields (e.g., "Main Prompt" vs. "Style Modifier").
### How often do you encounter this problem?
Several times per week
### How much does this problem affect your workflow?
Blocks me from completing tasks
### Current workarounds
Currently, I'm not using the native AppMode for production environments at all. Instead, I have had to build and maintain a completely separate, custom frontend for artists, that supports these fundamental features (ranges and tooltips). This creates a fragmented experience where I cannot take full advantage of the official ComfyUI AppBuilder ecosystem because it doesn't yet provide the "guardrails" necessary to keep workflows from breaking during creative sessions.
### Ideas for solutions (Optional)
_No response_
### Additional context
_No response_
┆Issue is synchronized with this [Notion page](https://app.notion.com/p/Issue-11801-Difficulty-ensuring-workflow-stability-and-providing-user-guidance-within-AppMode-3536d73d36508172b27fe81b89ce7172) by [Unito](https://www.unito.io)
Contributor guide
Assessment
This issue has not been assessed yet.