Hearing on Typing Indicator Tension
A small animated ellipsis has been assigned a higher priority than most of the messages it precedes.
Hearing convened to examine the matter of typing indicator tension.
Q: Describe what happens when the typing indicator appears.
A: The conversation thread is open. The other person begins typing. The indicator appears. The person waiting reads the indicator and waits. The indicator disappears. No message arrives.
Q: What happens next?
A: Someone watches a typing indicator disappear and waits for a message that never arrives. There is a pause. The person checks whether the other person has sent something in a different thread. They have not. The person returns to the original thread. The indicator is gone.
Q: How long is the wait?
A: The wait is usually under thirty seconds. Its duration is not the issue. The issue is that the wait is obligatory. The indicator has created an expectation of incoming information, and the expectation cannot be withdrawn by the person who has it. Only the message's arrival or a decision to close the app can end it.
Typing indicator tension steals one extra check of the screen. The check becomes habitual even after alerts are muted. Attention management turns into another inbox.
Q: Is this a design problem?
A: That question is not within the scope of this hearing.
Q: The alert is called noise while ignoring it creates more attention. Is that consistent?
A: No. It is the condition that makes the behavior persistent. Under the governing rule, typing indicator tension becomes procedure once repetition feels safer than reconsidering it. The repetition is daily.
Q: Does the message eventually arrive?
A: Sometimes. Sometimes the person was typing and then deleted what they wrote. Sometimes they switched applications. Sometimes they responded in a different thread. The ambiguity is the source of the tension, not the delay.
Q: Is there a resolution?
A: The hearing notes no resolution. The indicator is a feature.
Hearing adjourned.