u/Alternative-Pitch715

The bar for AI design tools is in hell right now. Generation speed doesn't matter if you can't touch the DOM.

I’m building an AI UI canvas and testing it with early users, and I realized people are completely brainwashed by 10-second viral demos.

A tester sent me a screenshot of a dark-mode layout today saying it was a "game changer" because it generated instantly. Cool. But generating UI is not the hard part anymore.

The real problem: what happens when you actually try to edit it?

What happens when your client says "make that logo 10px smaller" or "change the gap on this flexbox"?

In almost every AI tool out there right now, the second you touch the layout, it shatters like Jenga. You're locked out of manual control. The output isn't a native, editable component-it’s a fragile prototype masquerading as a website.

If a tool doesn’t let me manually edit the grid, adjust padding, or swap divs without triggering a cascade of broken CSS, it's just a toy. I end up just rebuilding the whole thing from scratch in Figma or VS Code anyway.

Am I the only one who thinks we're optimizing for the wrong thing? At what point in using tools like claude , paper or stitch do you usually just give up, throw the AI output away, and code it yourself?

reddit.com
u/Alternative-Pitch715 — 8 days ago
▲ 0 r/SaaS

Typing full sentences just to adjust a 16px padding is a terrible user experience.

We spent the last decade perfecting direct-manipulation tools like Webflow and Figma. Now, AI SaaS tools are throwing that away, forcing users to type "make the button slightly larger" into a text box, and praying the AI doesn't completely ruin the layout.

This is a massive friction point, and it causes users to churn. AI is incredible for 0-to-1 drafting, but using a chat box as a precision editing tool is insane.

Tried a different approach to this.

The user generates the initial layout in chat. But instead of being stuck in a prompt loop, the UI is instantly injected onto a visual, fully editable canvas. The user takes manual control. Drag nodes, adjust properties, fix the layout themselves.

(Attached a <2min demo showing the workflow).

I'm curious what other founders think about this. Are pure "chat wrappers" a dead end for complex software?

u/Alternative-Pitch715 — 21 days ago

We kept running into the same issue with AI UI tools: the first draft looks fine, but one small edit and the rest of the layout starts drifting.

That’s what pushed us to build Scytle as an editable canvas instead of a chat-only flow.

The AI generates the first draft, then the page drops into a ReactFlow workspace where you can edit the layout directly without re-prompting everything.

We’re still early and would really value blunt feedback from people who’ve tried these tools before.

Live link: https://www.scytle.com/

reddit.com
u/Alternative-Pitch715 — 21 days ago

I can get a decent first draft fast.
My issue is what happens after one small edit.

Today I changed only one thing in a pricing section: card padding from 24px to 16px.

After that:

  • heading wrapped differently
  • CTA alignment shifted
  • mobile spacing changed

So a 2-minute tweak became ~20 minutes of cleanup.

This is the pattern I keep hitting: local change, non-local breakage.

How are you handling this in real projects?

  • lock/freeze sections before reprompt?
  • switch to manual edits after first draft?
  • rebuild that block from scratch?
reddit.com
u/Alternative-Pitch715 — 26 days ago

This keeps happening to me:

I get a decent AI-generated UI.

I tweak spacing or hierarchy in one section…
and suddenly nearby blocks start drifting.

What should’ve been a small change turns into cleanup across the page.

The frustrating part isn’t generation speed anymore.

It’s that feeling where one edit breaks the overall balance -
and you lose confidence in the layout.

Curious if others hit this too.

What kind of change usually starts that domino effect for you?

reddit.com
u/Alternative-Pitch715 — 27 days ago