Chat UX is preventing "User" adoption.

[dustmoo]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Dify is billed as a no-code way to build AI workflows and apps, but the reality in my testing of the current version is that UX often breaks and that if a user doesn't understand code they are hopeless.

As a Software Developer I want a solid UX that does not crash due to bugs or misconfigurations but maintains a working chat flow. Also maybe not in China, but abroad your competitors have much better UX. The users want to chat and get artifacts, easily download files etc.

While we could code our own, it doesn't align with our priorities. I seriously you consider hardening your Chat UX. E.g. Agents break, apis fail something goes wrong and chat fails. Even my "medium code" builders got frustrated quickly.

Thank you for considering this feedback.

2. Additional context or comments

No response

3. Can you help us with this feature?

• I am interested in contributing to this feature.