Summary

Refine the native iOS chat experience so the conversation reads clearly and the composer feels like one compact, platform-native control.

Problem to solve

The current chat UI gives status chrome, assistant messages, and composer controls similar visual weight. Assistant replies appear as large cards, the gateway status dominates the header, and attachment, voice, text, and send controls read as separate floating elements. The result feels dense and distracts from the conversation.

Proposed solution

• Present assistant replies as open reading content while retaining a distinct trailing bubble for user messages.
• Replace the large gateway-status pill with a compact, accessible status control.
• Consolidate attachment, auto-growing text input, voice, and send actions into one aligned composer surface.
• Preserve Dynamic Type, VoiceOver labels, keyboard dismissal, four-line draft growth, attachment support, realtime voice controls, and iOS 18 fallbacks while using iOS 26 Liquid Glass where appropriate.

Alternatives considered

• Recoloring the existing cards: preserves the competing hierarchy and does not solve the fragmented composer.
• Applying glass to every message: makes reading content visually noisy and conflicts with Apple's guidance to reserve glass for interactive chrome.
• Rebuilding chat transport or state: unnecessary; the problem is presentation-layer hierarchy.

Impact

Affected: iOS chat users.

Severity: noticeable friction on every conversation.

Frequency: always.

Consequence: reduced readability and a less polished primary interaction surface.

Evidence/examples

Simulator baseline captured on iPhone 17 Pro / iOS 26.0. The implementation PR will include matched before/after screenshots and compact/expanded composer proof.