Canvas gives no illustrative feedback/loading state while AI workflow generation is running
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Epic: #4848 (AI-first UX)
Related: #4868 (Build with AI)
Problem
After clicking "Build it" in the Build with AI flow, generation can take
30+ seconds. The canvas itself shows nothing during that window, and the
only feedback anywhere is the chat window's typing dots — which aren't very
illustrative of what's actually happening. A first-time user watching an
empty canvas with just some dots elsewhere on screen could easily think the
app has frozen rather than that a workflow is being built.
Direction
Put something rough and ready on the canvas while generation is in
progress — e.g. a placeholder workflow shape — just enough to signal "this
is building" rather than "this is broken." It doesn't need to be polished;
a nicer, more illustrative loading UX (richer incremental feedback from the
assistant, etc.) can come later as its own piece of work.
Scope
- Show a rough placeholder on the canvas from the moment "Build it" is
clicked until the generated workflow is ready to render. - Keep it intentionally simple — a stopgap, not the final loading UX.
- Leave room for a follow-up to improve this once richer, incremental
assistant feedback is available.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Build with AI flow and trace the handler for the “Build it” action through the period before the generated workflow renders on the canvas. Show a simple placeholder during generation, remove it when the workflow is ready, and verify that the empty canvas is visibly distinct while building.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- ai, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100