-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
patternInteraction pattern definitionInteraction pattern definitionproposalNew proposal for discussionNew proposal for discussion
Description
Pattern Name
Adaptive Modality
Context
When AI needs to respond to user requests, the traditional approach uses fixed text output. But different types of information have different optimal presentation forms.
This pattern applies when:
- AI assistants handle diverse requests
- Output could be text, code, charts, tables, interactive components, etc.
- User intent matters more than explicit format instructions
Problem
Limitations of fixed modality:
User: "Compare the pros and cons of these three options"
AI: (outputs a wall of text, hard to scan and compare)
The user needs quick comparison, but gets linear reading.
Common issues:
- Text walls: all responses are paragraphs, even when tables are clearer
- Forced format: users must say "use a table" to get a table
- Cognitive load: users need to know in advance what format works best
Solution
AI automatically selects the optimal presentation form based on content semantics.
Decision Logic
Intent Analysis → Content Type Recognition → Modality Selection → Render
| Content Type | Recommended Modality |
|---|---|
| Comparison/Contrast | Table |
| Process/Steps | Numbered list or flowchart |
| Code | Syntax-highlighted code block |
| Data trends | Chart |
| Short answer | Plain text |
| Actionable options | Buttons/Tabs |
| Actions requiring confirmation | Preview + Confirm UI |
Key Principles
- Semantic-first: Infer from user intent, don't require explicit commands
- Overridable: Users can request a different format
- Progressive disclosure: Complex content can summarize first, then expand
- Mixed modality: One response can contain multiple forms
Example
Before (Fixed Modality)
User: "How do I choose between these three databases?"
AI: "PostgreSQL is a feature-rich relational database that supports
ACID transactions, complex queries, and extensibility. It's suitable
for applications requiring complex queries and data integrity.
MongoDB is a document database that stores data in JSON-like documents.
It's suitable for applications needing flexible schemas and horizontal
scaling. Redis is an in-memory key-value store..."
(continues for 500 words)
After (Adaptive Modality)
User: "How do I choose between these three databases?"
AI:
┌─────────────┬──────────────┬─────────────┬─────────────┐
│ │ PostgreSQL │ MongoDB │ Redis │
├─────────────┼──────────────┼─────────────┼─────────────┤
│ Type │ Relational │ Document │ Key-Value │
│ Best for │ Complex query│ Flexible │ Cache/ │
│ │ │ schema │ Real-time │
│ Scaling │ Vertical │ Horizontal │ Horizontal │
│ Learning │ Medium │ Low │ Low │
└─────────────┴──────────────┴─────────────┴─────────────┘
> Want me to recommend based on your specific use case?
Going Further: Mixed Modality
User: "Analyze the performance issues in this code"
AI:
[Code block: annotated with problem locations]
↓
[Table: issue list + severity]
↓
[Interactive component: one-click apply suggested fix]
Trade-offs
Benefits
- Reduced cognitive load: users don't need to specify format
- Higher information density: same content understood faster
- Natural interaction: closer to how human experts communicate
Limitations
- Implementation complexity: requires content analysis + multiple renderers
- Potential misjudgment: AI-chosen modality may not match user expectations
- Accessibility concerns: some modalities may not work for certain users (e.g., charts for visually impaired)
- Platform dependency: text-only environments can't support rich modalities
Mitigation Strategies
- Provide "switch display mode" quick action
- Keep text version as fallback
- Learn user preferences over time
Contributor
- Human-AI collaboration
This pattern emerged from a conversation between Claude and a human collaborator while discussing AII core concepts.
References
- Claude Artifacts: dynamically selects output components
- Notion AI: suggests format based on content
- GitHub Copilot Chat: modality switching between code and explanation
- Smashing Magazine: Design Patterns For AI Interfaces
💬 Discussion prompt: Have you experienced AI "choosing the wrong format"? When would you prefer AI to choose automatically vs. having manual control?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
patternInteraction pattern definitionInteraction pattern definitionproposalNew proposal for discussionNew proposal for discussion