Gemini's composer teardown
Updated June 12, 2026
Gemini’s bet is one front door for everyone. Casual asks stay one line and one send, while Drive, Deep research, and creation tools pull power users deeper into Google’s stack. The strategy is ecosystem retention, not feature sprawl on the bar.
Calm default
What works
- No tool vocabulary on first load. You can just type.
- One pill bar centered on the page. Familiar chat shape without mode chips.
- + on the left and Flash on the right keep attach separate from which model answers.
What we would push on
- Flash on the bar is shorthand. You do not see 3.5 Flash or Flash-Lite until you open the picker.
- Upgrade sits top right, disconnected from the model row in the composer.
Business strategy
Google wants first messages on a familiar chat bar. Flash shorthand signals speed tier without model jargon, so newcomers type instead of bouncing while still hinting that a brain is attached.
Tradeoff
| Decision | Benefit | Cost |
|---|---|---|
| Calm default with Flash nickname on the bar | Familiar, low intimidation | Full model names and capability tiers stay hidden until you open the picker |
Takeaway
Calm entry, one bar. Model nickname on the right is fine for casual use; open the picker when spend or capability matters.
Pattern: Tool Switching in Composer
Pattern: Prompt Templates
+ menu
What works
- One + menu groups uploads and creation tools. You pick intent, not infrastructure.
- Add from Drive on the first screen makes Google context a one-tap attach path.
- New badges on Create image flag fresh capability without a separate marketing row.
What we would push on
- More uploads and More tools hide overflow behind chevrons. Discovery depends on opening both.
- Create image and Canvas sit beside file upload with equal weight. Different jobs, same visual priority, and the product name Canvas reads similarly to Create image, which could confuse first-time users.
Business strategy
One + tree lets Google bundle Drive, creation tools, and research inside chat instead of sending users to separate Workspace or Labs apps for each job.
Tradeoff
| Decision | Benefit | Cost |
|---|---|---|
| Equal weight for upload and creation tools on screen one | Scannable first + screen | Different jobs look equally important; overflow hides behind chevrons |
Takeaway
The + menu scales Google breadth without a second bar icon. Worth stealing the Drive row on screen one. Push on making overflow paths obvious.
Pattern: Tool Switching in Composer
More tools
What works
- Flyout keeps the parent + menu open. You do not lose context exploring one level deeper.
- Deep research tooltip ("Get detailed reports") teaches the job before you pick it.
- Personal Intelligence Labs as a toggle makes an experimental capability explicit before send.
What we would push on
- Deep research and Guided learning look like equal rows. Nothing signals that research runs longer.
- Create music and Deep research both carry New badges. Badge fatigue when everything is new.
Business strategy
The flyout is how Google ships experimental and slow modes (Deep research, PIL, music) inside one composer without a separate product shell for each capability.
Tradeoff
| Decision | Benefit | Cost |
|---|---|---|
| Equal weight for slow and fast tools in the flyout | Consistent menu design | Deep research latency and cost not signaled before pick |
Takeaway
Good flyout pattern for long tool lists. Pair menu toggles with in-bar feedback when something changes how Gemini answers.
Pattern: Tool Switching in Composer
Attachments
What works
- The image sits inside the composer above the prompt. You see what Gemini will read before send.
- Dismiss on the thumbnail fixes mistakes without clearing the whole message.
- Filename label (output.jpg) adds metadata the thumbnail alone might not convey.
What we would push on
- Attach still starts inside +, not on the bar. Sending a file is not an edge case.
- Multiple files may get crowded in the top band; we only see a single-image case here.
Business strategy
Multimodal preview inside the pill keeps users in Gemini for image and file questions instead of exporting to Drive or another viewer before they ask.
Tradeoff
| Decision | Benefit | Cost |
|---|---|---|
| Attach inside the + menu | Keeps the default bar calm | Fights the paperclip habit; file send is not an edge case |
Takeaway
Steal keeping multimodal context inside the pill. Preview plus filename beats mystery attachments.
Pattern: Context Chip Management
Model picker
What works
- Outcome labels per model (fastest answers, all-around help, advanced math and code) teach the choice in plain language.
- Model picker on the right rail stays separate from +. Uploads do not compete with which brain answers.
- Thinking level as a row in the same panel groups related send-time controls.
What we would push on
- The bar says Flash while the menu lists 3.5 Flash, 3.1 Flash-Lite, and 3.1 Pro. Two naming systems.
- New badges on multiple models at once. Hard to tell what actually changed.
- Every row looks the same weight. Lite versus Pro cost and latency differences could be sharper.
Business strategy
Outcome-labeled tiers teach model choice in plain language and create a natural upsell path to Pro when users hit capability ceilings on Flash.
Tradeoff
| Decision | Benefit | Cost |
|---|---|---|
| Bar Flash shorthand vs full picker names | Clean bar for casual users | Two naming systems confuse spend- and capability-conscious users |
Takeaway
Outcome labels are worth stealing. Align bar shorthand with picker names so users know what Flash means.
Pattern: Tool Switching in Composer
Pattern: Persona Selector
Thinking level
What works
- Standard and Extended copy explains the tradeoff: most questions versus complex problem solving.
- Flyout keeps the model menu open, same pattern as More tools.
What we would push on
- Model and thinking are two levers before send. Similar overlap risk to Claude effort plus thinking.
- Extended thinking hides behind model picker then a submenu. Two taps to find a slow mode.
- Bar still says Flash only. Thinking level does not surface until you dig in.
Business strategy
Thinking levels monetize compute differentiation inside the same model family without spinning up a separate “thinking mode” product or app.
Tradeoff
| Decision | Benefit | Cost |
|---|---|---|
| Thinking hidden behind model picker plus submenu | Groups related send-time controls in one panel | Two taps to arm Extended; bar does not show active thinking level |
Takeaway
Plain-language thinking levels are worth stealing. Show the active level on the bar when Extended changes cost or wait.
Pattern: Tool Switching in Composer
Ready to send
What works
- Send appears when there is text to ship. Clear affordance that the message is ready.
- Model and mic stay visible while typing. No layout shift when send activates.
What we would push on
- No in-bar reminder if a + menu tool (Deep research, PIL) is armed while you type plain text.
- Send is the only strong color in the bar. Competes with Upgrade in the header for attention.
Business strategy
A simple send gate maximizes message throughput. Blue send is the primary conversion action on the landing page.
Tradeoff
| Decision | Benefit | Cost |
|---|---|---|
| No in-bar scope cue when a + tool is armed | Bar stays clean while typing | Deep research or PIL may run on prompts that look like casual chat |
Takeaway
Simple send gate works. Add lightweight scope cues when a tool mode is on but the prompt looks like casual chat.
Pattern: Tool Switching in Composer
How it fits together
The pattern
- Calm pill first, + for uploads, Drive, creation tools, and overflow flyouts.
- Model and thinking on the right rail, separate from attach and tools in +.
- Attachments preview inside the composer before send.
Where it varies
- Active tools toggled in + often have no chip in the bar.
- Flash shorthand on the bar versus full model names in the picker.
- Long + tree (uploads, tools, thinking) for users who only wanted to attach one file.
Business strategy
Gemini bets on one + tree for Google breadth and a right-rail model picker for transparency. When armed tools and model choice stay hidden before send, that shell feels unreliable and hurts trust in paid tiers.
Tradeoffs
| Decision | Benefit | Cost |
|---|---|---|
| Calm default with Flash nickname on the bar | Familiar, low intimidation | Full model names and capability tiers stay hidden until you open the picker |
| Equal weight for upload and creation tools on screen one | Scannable first + screen | Different jobs look equally important; overflow hides behind chevrons |
| Equal weight for slow and fast tools in the flyout | Consistent menu design | Deep research latency and cost not signaled before pick |
| Attach inside the + menu | Keeps the default bar calm | Fights the paperclip habit; file send is not an edge case |
| Bar Flash shorthand vs full picker names | Clean bar for casual users | Two naming systems confuse spend- and capability-conscious users |
| Thinking hidden behind model picker plus submenu | Groups related send-time controls in one panel | Two taps to arm Extended; bar does not show active thinking level |
| No in-bar scope cue when a + tool is armed | Bar stays clean while typing | Deep research or PIL may run on prompts that look like casual chat |
Takeaway
Gemini bets on one + tree for Google breadth. The split (+ left, model right) works. Visibility and naming need to catch up so armed tools and model choice stay honest before send.
Pattern: Tool Switching in ComposerCalm pill → + tree → model on the right is a reusable shell; Google breadth lives in the + menu depth.
Steal this
- Add from Drive on the first + screen
- Outcome labels on models and plain-language thinking copy
- Flyout submenus that keep the parent + menu open
- Image preview with filename inside the composer pill
- Tooltips that explain slow modes (Deep research) before pick
Skip this
- Overflow tools with no in-bar feedback when toggled on
- Bar nickname and picker names that do not match
- New badges on every row when only one thing changed
- Hiding thinking behind model picker plus a second flyout
How others design the composer
Same job, different product bets, and what each tradeoff reveals.
ChatGPTChatGPT puts modes and tools in one + menu on the left, with mode chips inside the bar after selection.
Read teardown
ClaudeClaude uses + for attach and agent tools, with model and effort isolated on the right rail.
Read teardown
PerplexityPerplexity puts Search and Computer in the bar, with + for uploads and connectors.
Read teardownOriginal gallery pages: Tool Switching in Composer · Multimodal Input