Overview

The Experience Designer builds one page at a time. You describe a campaign — an offer, an audience, a season — and a design agent builds it against your live shop, on a canvas that renders inside your real storefront. When it looks right, you publish it, and it goes live in place. Where Frontic Studio produces code in a repository, the Designer produces an experience: a self-contained fragment that mounts into a page your shop already serves.

​

What an experience is

An experience is a single, emotional commerce moment — a Black Friday landing page, a brand collaboration, a category takeover, a seasonal hero. It renders with your header, your footer, your theme, and your real add-to-cart, because it lives inside your storefront rather than beside it. Concretely, an experience is:

• One unit of work with its own name, its own canvas, and its own chat
• Versioned — every save is an immutable version you can publish, roll back to, or share
• Bound to a place — a URL on your shop, and optionally a specific container on that page

Products and prices in an experience are real. The agent pulls them from your project’s live catalog through the typed API, so a price on the page is the price your shop charges. It doesn’t invent offers, and it doesn’t bake prices into text.

​

Who it’s for

Marketing and e-commerce people who think in offers, audiences, seasons, and brand — not in files and builds. The Designer’s chat is deliberately non-technical: it talks about the experience, the canvas, the hero, and the offer, and it keeps framework and build details to itself. That also sets the boundary. The Designer designs experiences. Prices, product data, and shop settings live in your shop system or in project settings — ask the Designer to change one and it’ll tell you where it lives, then offer what it can do toward the same goal.

​

Creating an experience

Two entry points, depending on where your project’s storefront lives. When a project is connected to Shopware, experiences are created from the Shopware side — the layout owns where the experience lives, so Frontic doesn’t offer a New Experience button that would produce a page with nowhere to go. See Frontic Experiences in Shopware for that flow end to end. Either way, opening a new experience provisions a workspace for it: Frontic reserves the sandbox that runs the build, wakes the design agent, and loads a private, editable copy of your storefront behind the canvas. It takes a moment the first time; after that the workspace sleeps and wakes with the experience.

​

The Designer surface

Two panels: chat on the left, canvas on the right. The canvas is not a mockup. It’s your storefront — the real page at the preview URL — with the experience rendered in place of the container it replaces. Scroll it, switch between phone and desktop, click through to another page and come back. What you see is what shoppers get. Above the canvas sits a toolbar with the version picker, the share link, and the controls for pointing the experience at a different page or a different container on it. Everything on the Building an experience page happens here.

​

How the agent works

The Designer’s chat follows a deliberate arc, and each step shows something real on the canvas rather than describing it. The arc scales to the ask. A tweak skips it entirely; “just build it” compresses it into one pass. Every meaningful round ends with the canvas updated and one sentence about what changed. The agent proposes one concept with conviction rather than a menu of options, and it will push back once — politely — when a request would hurt the result. After that, your call is final.

​

What it draws on

The Designer doesn’t start from zero on a new project either. Initialize writes the first draft of all of it by reading your storefront once.

​

Related