How apps work

Interactive components your assistant can show inside the chat.

Apps are custom interactive experiences the assistant renders in the conversation instead of answering in plain text — a comparison, a browsable catalogue, a product card.

Apps — each card is a live component with its state

App library

Pre-installed apps every store starts with.

Building an app

Create your own with the Greatstore MCP and a coding agent.

Two kinds of app

Inline apps render inside the chat flow — a product list appears right in the conversation as the assistant answers.

Full-screen apps take over the panel for richer interactions — a side-by-side product comparison is the canonical example.

States

State	Meaning
LIVE	Published — the assistant can render it now.
DRAFT	Created but never published.
UNPUBLISHED	Was live, has been taken down.

You can publish and unpublish from the Apps screen, or by asking the same coding agent that built the app (via the MCP).

The assistant decides when to use them

You don't wire apps to triggers. Once an app is live, the assistant chooses to render it when the conversation calls for it — ask it to compare two products and it reaches for the comparison app on its own.

That autonomy is why restraint matters: too many apps, or apps whose purposes overlap, confuse the assistant about which one to call. Keep the set small, distinct, and genuinely useful to shoppers.

The Apps screen

Each app appears as a card with its state. Click a card for a live preview rendered the way a shopper would see it. Refresh re-reads the published set — use it after your agent deploys a change.