# Interfaces beyond the screen

> How clear task state, familiar controls and deliberate approval points support interfaces that combine conversation and direct interaction.

- Category: Interface Systems
- Reading time: 2 min
- Published: 2026-08-07
- Updated: 2026-09-13

A useful interface makes the next decision clear. Sometimes that needs a screen; sometimes it needs a short exchange, a preview or a confirmation.

## Start with the task

Define the outcome before choosing the interface. What does the person want to change, what information is missing, and what must stay under their control?

An agent can help translate a request into work. The interface still needs to make the scope visible before that work begins.

## Show what is happening

A useful progress view distinguishes work that is planned, running, blocked and complete. Describe actions and results in plain language.

Keep decisions close to the evidence needed to make them. A preview is often more useful than another page of configuration.

## Use familiar controls

When a task needs comparison, editing or precise selection, provide a direct interface. Conversation should not make a simple action harder.

Build generated views from tested components. Consistent labels, keyboard behaviour and error states help people move between tasks.

## Keep control visible

Make cancellation and recovery easy to find. Ask for approval at the point where the consequence is clear, and retain enough context for work to resume.

The interface is successful when someone can understand what changed and decide what to do next.

## Index

- [Journal](https://brittek.net/journal)

Canonical URL: https://brittek.net/journal/interfaces-after-the-screen