Active Call UI Should Show State Without Competing with the Conversation

During a call, the screen is for confirmation and control feedback rather than continuous content.

The acceptance condition for Active Call UI Should Show State Without Competing with the Conversation only became clear after the system was split into boundaries. LOUP active-call state needs only the information that helps the user understand who is connected and what controls are active.

Contact name, call state, mute status, volume feedback and basic connectivity can fit in stable regions. Avoiding animation reduces refresh noise and leaves physical controls in charge of immediate actions.

The design became clearer when configuration, runtime state and recovery behaviour were specified separately instead of being implied by implementation details. Evidence marker: active-call-ui.

A voice-first interface should become quieter after the call connects, not busier. Once that contract is written down, firmware and server changes can be reviewed against the same expectation instead of relying on memory.

Project evidence

LOUP engineering marker: active-call-ui. This note records the design or debugging lesson without publishing device credentials, private keys, customer data or manufacturing secrets.