What if the app lived inside the conversation?

Description and use

Embedding app controls inside the chat keeps users in a single interface while preserving structured task views and explicit actions, reducing the need to reconstruct context in prompts.

Problem

How can a conversational interface serve as the primary UI for a structured work application without losing clarity and control?

Outcome

Embedding the app’s controls inside the chat keeps users in a single interface while preserving structured task views and explicit actions, reducing the need to reconstruct context in prompts.

Workflow

• 1. Incoming work items (email, chat, issue) are aggregated into a shared timeline. 2. The assistant brings a selected item into the conversation, preserving its context. 3. The task card is rendered inside the chat, showing current state and next actions. 4. Users click a control or ask the model for clarification. 5. The assistant performs the requested action or drafts a reply. 6. Drafts are displayed with approve/reject/regenerate controls before final submission.

Evidence

The first screen should make that work visible, rather than asking you to reconstruct it in a prompt.

Source

The request, task state and next actions are together.

Source

I used all sorts of AI for the whole app, including the backend, frontend and task-card interface.

Source