Principles
- 01
Allow deep previews in chat
Opening an Insight, card or result happens inside the conversation, not in a submenu. The composer stays in reach so they can keep asking.
- 02
Chips follow the content
Chips and the menu come from what's on screen: an automation suggests automation actions, product Q&A suggests follow-up questions, a Smart Report suggests report actions. With nothing in view, chips show what Aireal can do.
- 03
Every answer leads somewhere
Replies end on a next action or a follow-up built from data we already have, never a dead end.
“Want me to turn this into an automation?”
Flow
Decisions
Pop-up → full-screen transition
ExploringText and voice entry both open full screen. Logo-anchored navigation and top-down chat are out.
- Text input → full screenChosen
Tap the field; pop-up grows edge to edge.
- Voice input → full screenChosen
Tap the mic; listening opens full screen.
- Logo-anchored navigationRejected
Docked logo doubles as a back pill.
- Top-down chat + Daily BriefRejected
Soft fades; Daily Brief returns home.
Greeting on scroll
ProposedDocking logo is the primary pattern. The docked logo is the way back to the top.
- A · Dock into headerChosen
Logo shrinks 54 → 24 and docks left.
- B · Large-title collapseRejected
iOS-style 17pt title.
- C · Shrink and fadeRejected
Parallax; cards glide over.
- D · Logo-only markRejected
Logo stays centered at 32.
- E · Greeting chipRejected
Frosted pill; tap to top.
Voice: Send sends, Stop reviews
ProposedRecording stays obvious and reversible.
- Separate Send and StopChosen
Fast path and fix-it path, both visible.
- Always reviewRejected
Extra tap; half of voice starters already drop.
- Auto-send on silenceRejected
No way to fix a misheard word.
Open questions
- 3.2.2: Where is last-used input stored?
- 3.3.1: Where do New Chat and Feature Center live?