When noise looks like an interruption
The assistant stops. You weren’t trying to say anything.
Ari is adding a calendar event. His son drops a package on the desk. The assistant mistakes the noise for an interruption, but cannot make out a request. How does it return to the task without losing the information already given?
Settings review
with Will
May 14 · 3:00 PM
- Invitee
- Jon Bloom
- Calendar
- Work
A calendar draft. One unexpected sound.
Optional browser voice. No microphone or calendar connection.
The assistant loses its turn, not your event.
Recover without starting over
The storyboard keeps the event visible while the assistant stops and retries its confirmation. Nothing about the noise should change the title, time, or person. The final “Yes” lets the assistant finish the original task.
The adjacent motion-sketch slide compares words on the voice strip with no words. Here you can switch captions at any point. The transcript below the scene stays available in both versions.
Original frames & reconstruction notes
Source: Portfolio_WJ, slides 39–41. Slide 39 establishes the dropped-package scenario; slide 40 compares voice-strip treatments; slide 41 supplies the confirmation, false interruption, retry, “Yes,” and completion.
This is a new Apple-inspired web motion study, not the original product interface. Sheet transitions, grouped calendar fields, speech animation, timing, and confirmation treatment are new interpretations. The interrupted sentence and recovery dialogue follow the storyboard; ready-state wording and explanatory labels are new. The source images are unchanged exports. No original motion or product audio has been recovered. The voice-strip transition between these stills is an interpretation, not extracted prototype wiring. The package drop is a scheduled moment in the scene, not a live sound detector. “Saved” only changes this demonstration; no real event is created.