Inferring state from physiology and changing the UI requires informing the user

What it is

Estimating “too stressed / too relaxed” from heart rate or EDA, then auto-changing a theme, pushing a break, or silencing notifications, is no longer showing a number. It turns a body signal into an interface decision. That use needs the user to know beforehand which signals are sampled, that the inference is an arousal-like state, and which UI moves will follow. The requirement attaches to this physiological channel driving adaptation, not to a switch buried in settings after the fact.

Why it happens

Heart rate and EDA run continuously and are rarely experienced as a command. People see the interface change and often do not know the pulse was the cause. Body data is also read as a health or competence verdict, so leaks and mislabels cost more than ordinary clickstreams. Arousal does not line up with named emotions, so the label the system uses when it changes the UI can clash with the user’s own account—“I just climbed stairs.” Without prior explanation, adaptation feels like the device acting on its own; with explanation that sells the inference as a diagnosed emotion, the informing is itself false.

Studying it

A typical contrast hides the physiological adaptation, describes “personalization” vaguely, or names the signal and the action precisely. Outcomes: the fraction who notice the adaptation, agreement with the inference, willingness to turn the feature off, and anger or shame after a mislabel. Field work should test whether copy lets people connect “heart rate rose” with “I just climbed stairs.” Students wearing obvious research sensors in a lab are more informed than a watch that quietly restyles the UI in the background; ecological validity is not equivalent.

Where it stops holding

A heart-rate number the user opened, or a post-exercise recovery curve, is viewing rather than inference-driven UI rewrite, and the informing burden differs. Clinical settings have their own consent and warning rules; a consumer toast cannot stand in for them. For children, employees, and people under guardianship, a tapped “agree” may not make informing valid under power asymmetry. A long text that flashes once at first launch, while inference logic changes for years afterward, is not ongoing informing.

Applying it

• Before heart rate or EDA is allowed to change the UI, use one screen to say what is sampled, what is inferred (arousal, not an emotion name), and which concrete behaviors will change.
• When adaptation fires, show a dismissible reason strip: “pulse rose, nagging notifications paused”—not a silent theme change.
• Split authorization for “drive UI adaptation” from “view only”; do not promote a viewing sensor into a decision-maker by default.
• Verify by planting a clear mislabel during real wear (heart-rate rise from motion) and checking whether the user can find the reason on the current screen and disable that adaptation.

Related

• Same group: C9.03.1 Physiological measures reflect arousal rather than specific emotions · C9.03.2 Motion and ambient temperature contaminate the signal
• Adjacent: C9.13 Informed Consent and Correction of Implicit Inferences · C9.05 Implicit Interaction
• Search: informed physiological inference · adaptive UI disclosure · EDA consent