Designing a widget that knows when to disappear.

A tiny surface can create a lot of friction

Voice products often look simple because the visible interface is small. A microphone, a waveform, maybe a timer. But a small surface does not mean a small design problem.

When a widget appears above the work, every pixel is competing with something the user was already doing. It can cover text, interrupt attention, create uncertainty about whether the microphone is active, or stay around long enough to become visual clutter.

So our question is not ‘how do we make the widget more impressive?’ It is ‘what does the user need to know in this exact second?’

Three states, three different jobs

Before speaking, the widget should create confidence: Lungoor is ready. While speaking, it should confirm that something is happening without turning the waveform into a performance. After speaking, it should make completion obvious and then leave.

Those sound like tiny transitions. They are not. If the listening state is ambiguous, people repeat themselves. If the completion state feels slow, they stop trusting the shortcut. If the widget lingers, it starts to feel like another app rather than part of the workflow.

The design system therefore has to be calm enough to disappear and clear enough to be trusted.

Good design does not ask for applause. It gives you clarity, gets out of the way, and somehow makes the next action feel obvious.

Feedback should answer, not entertain

It is tempting to animate voice products heavily because audio gives us so many visual metaphors: pulses, waves, particles, glowing states. Some motion is useful. Too much asks the user to watch the tool instead of continue the work.

We try to use motion as feedback rather than decoration. Listening should feel alive. A successful transformation should feel complete. A style change can visibly reshape text. But nothing should keep moving simply because the product can.

The best compliment for this kind of interaction is not ‘that animation was cool.’ It is ‘I knew exactly what happened.’

Design for the moment after the widget

A good widget interaction does not end when the widget disappears. The real outcome is the text left behind. Is it readable? Does it feel like the user’s thought? Can they keep typing immediately? Can they select it and change style without starting a new workflow?

This is why the widget cannot be designed in isolation. It is only one state in a larger loop: thought, input, transformation, output, continuation.

If we make the widget beautiful but the user still needs to clean up everything afterward, we have designed the wrong part of the experience.