UX Design · Study deck
Multimodal Interfaces: Modalities and Trade-offs
Voice works across a room but fails beside a loud machine; touch is private but fails under gloves.
UX Uma is your guide for this deck.
After studying this chapter
Learning objectives
You will be able to:
- Explain: A network outage moves the product to: LEVEL 2 Local Network Control, where physical buttons still work, cached state is identified, and commands may be queued.
- Explain: In each case, the interface must adapt to the user's available senses and limbs rather than demanding a specific posture or focus.
- Explain: When a preferred channel disappears, the design needs a planned reduction in capability rather than a single offline screen.
- Explain: A smart lock that announces "DOOR UNLOCKED" at 2 AM will be disabled by users, losing the security benefit.
Major section
Introduction
In each case, the interface must adapt to the user's available senses and limbs rather than demanding a specific posture or focus.
- Most IoT devices are used in contexts where users cannot devote full attention to a single screen.
- A nurse checking patient vitals has gloved hands.
- A driver monitoring vehicle diagnostics is watching the road.
Major section
Visual vs Audio Feedback
User studies show visual indicators are checked in 0.3-0.5 second glances.
- Color-coded states (green=OK, red=error, amber=warning) are universally understood.
- Limited to line-of-sight; users must look at device.
- Critical alerts use both modalities.
- Accessibility: audio helps visually impaired users; visual helps hearing impaired users.
Major section
Graceful Degradation
IoT interfaces must handle failures gracefully at each layer.
- When a preferred channel disappears, the design needs a planned reduction in capability rather than a single offline screen.
- A network outage moves the product to: LEVEL 2 Local Network Control, where physical buttons still work, cached state is identified, and commands may be queued.
Major section
Pitfalls to Avoid
Voice-Only Trap: Designing a smart device that only supports voice interaction.
- When voice recognition fails (noisy room, accent mismatch, service outage), the device becomes a paperweight.
- Ignoring Quiet Hours: Audio feedback that cannot be silenced or scheduled.
- A smart lock that announces "DOOR UNLOCKED" at 2 AM will be disabled by users, losing the security benefit.
Major section
Pitfalls to Avoid (continued)
Better to have two polished modalities (e.g., app + physical button) than five half-finished ones.
- Prioritize the modalities your users actually need.
- No Offline State Indication: When cloud connectivity is lost, the interface looks identical to the connected state.
- Users issue commands that silently fail, eroding trust.
Deck summary
Key takeaways
In each case, the interface must adapt to the user's available senses and limbs rather than demanding a specific posture or focus.
- User studies show visual indicators are checked in 0.3-0.5 second glances.
- IoT interfaces must handle failures gracefully at each layer.
- Voice-Only Trap: Designing a smart device that only supports voice interaction.
- Better to have two polished modalities (e.g., app + physical button) than five half-finished ones.
Retrieval practice
Recall check
UX Uma says: answer from memory, then check your reasoning.
Q1A homeowner carrying groceries needs to adjust a thermostat. What should determine the interaction mode?
Show answer
Answer: A The introduction selects modalities to fit the user’s current context.
Q2A primary voice channel becomes unavailable for a quick device action. What should the design preserve?
Show answer
Answer: D The section connects modality selection with graceful degradation and offline fallback.
Print reference
Answers
Answer key.
- A · The introduction selects modalities to fit the user’s current context.
- D · The section connects modality selection with graceful degradation and offline fallback.