All posts
Product

How designers can make UI changes in the real app

Designers can make UI changes in the real app by editing in a browser workspace that runs it. In Ensemble Studio, you describe the change in chat ("make the billing toggle's hit area bigger"), and a live preview of the app, with its data, hot-reloads beside you. No repo to install, and engineers review the same URL.

4 min read

Why design QA is hard in the real app

The questions designers care about most (real copy, empty states, long names, loading states) only show up in the running app, and the running app lives on an engineer's laptop.

A Figma frame shows the happy path with perfect placeholder data. The shipped product has a customer named "Wolfeschlegelsteinhausenbergerdorff," an account with zero projects, a table with 400 rows, and a button that wraps on a small phone. That's where the design actually succeeds or fails.

Designers usually see those states in one of two ways: a design QA pass on staging after the work is "done," or screenshots from an engineer. Both are late. By the time a designer spots that a toggle is too small to tap, the engineer has moved on, and the fix becomes another ticket that waits a sprint.

The fix is often tiny. Four pixels of padding. A different color token. A shorter label. The cost is almost entirely coordination.

How to change UI in a live preview

You make the change in chat and check it on the running app, in four steps.

1. Open the preview

Open the preview for the branch you're reviewing, or start a new one from a ticket. The preview is the real app for that branch, with seeded accounts and data.

2. Describe the change in design terms

You don't need to know the code. Describe what you want the way you'd annotate a frame:

Increase the hit area of the billing toggle to at least 44px. Use the existing team-plan color for the active state. Shorten the label to "Annual (save 20%)."

Reference your design system by name where you can ("use the accent token," "use the secondary button style"). The agent looks up how the codebase implements those.

3. Check it on real data

The preview hot-reloads as the change lands. Then check the states that matter:

  • the empty account and the busy account,
  • the longest plan name and the longest customer name,
  • a narrow mobile width,
  • loading and error states, if the change touches them.

Seeded data is what makes this possible. If your team's seeds don't include the states you care about, ask an engineer to add them once; every future preview gets them.

Send the preview URL to the engineer who'll review the pull request, and to anyone else who should see it. It's the same link for everyone.

What designers change, and what stays with engineers

Designers change what users see and touch. Engineers keep control of protected branches and secrets.

Good fits for designers:

  • spacing, sizing and alignment,
  • copy and microcopy,
  • color, type and design tokens,
  • component states: hover, focus, disabled, empty, error,
  • layout at breakpoints,
  • small interaction changes, like tap targets and focus order.

What stays with engineers: merging into protected branches, secrets, infrastructure and anything that changes how data is stored. Every preview is isolated, so a design experiment can't break someone else's work or touch production.

A useful rule: if you'd normally file the change as a design QA ticket, you can probably make it yourself.

How review works

Review happens on the same running preview, not in a thread of screenshots.

The engineer opens the preview and the pull request side by side. They click through the change first, then read the diff. Feedback goes in the pull request or the ticket, tied to a change everyone can open.

Where this fits with Figma and prototyping tools

Figma is still where you decide what a screen should look like. Prototyping tools are still great for exploring ideas quickly. A live preview is for the next step: checking how the design holds up in the real product, with real data, and fixing it directly.

If you're comparing AI UI generators with editing the real app, see v0 and Bolt alternatives for an existing codebase.

FAQ

Is Ensemble a Figma replacement?

No. Figma is for deciding what a screen should look like. Ensemble is the running app, for checking how a change feels with real data and making the fix directly.

Can a designer change production?

No. Designers change a preview. The change reaches production only after an engineer approves the pull request and your normal pipeline deploys it.

Do designers need to know how to code?

No. You describe the change in plain language and check the result on the preview. Engineers review the code in the pull request.

Does a designer need a paid seat?

Yes, if you chat, edit or create previews: that's a builder seat. If you only open links to look at other people's changes, you're a free reviewer.


Ensemble turns every change into a running copy of your real app, with its services and data, at a private link anyone on the team can open. What is Ensemble?

Stop shipping the hard way

Agents write the code. Ensemble runs it. Everyone clicks it: product people in the browser, agents in parallel, engineers deciding what merges.

Start free