Everyone Is Adding Chat to AI Design Tools — Here’s Why We Didn’t
Most AI design tools start with the same idea:
“Let the user talk to a chatbox, and the AI will build the design.”
It felt smart. It looked modern.
And then we realized… it actually slows people down.
Prompt → guess → adjust → repeat. It's a loop of negotiation with the model instead of building a product.
So we took a different route.
After the user describe a product in simple words, Sketchflow.ai generate the actual structure — logic, pages, navigation — front-end code.
And then we give the user full control to modify anything directly: drag it, cut it, reshape it, rebuild it.
No prompt guessing. No hassle of adjusting page by page.
Why?
Because real products don’t start as paragraphs.
They start as workflows, decisions, and relationships. Visuals come later.
This approach isn't perfect yet, but it feels closer to how product teams actually think.
Curious how others see it:
Is prompt-driven UI already hitting its ceiling?
Or do you think chat will remain the default interface for AI design tools?
Saying no to chat is an interesting constraint — most teams add it before they’re clear what problem it’s actually solving.
Curious — what’s the one user behavior you’re watching to validate that this decision is helping (faster task completion, fewer missteps, repeat use, etc.)?