Action at the bottom and feedback at the top get missed
Aliases: toast miss · stacked layout miss · top banner miss
What it is
A phone form’s primary button sits at the bottom; the success bar drops from the status bar. The thumb is still on the lower edge, the eyes are still near the button, and the banner often dies unseen. That is a vertical feedback split: the action at one pole, a short-lived confirmation at the other, a full column of content in between.
This is not the generic claim that feedback is “too far”. Far could mean the next column. Here the split is the two vertical poles, and the feedback usually lives only a second or two.
Why it happens
At the moment of a tap, gaze typically rests just above the contact, finishing the aim. The useful field of view is then a small region around that fixation; a jump across the full height of the screen is already outside it. A high-contrast top banner still needs an extra saccade to reach the fovea, and people filling a form will not spend that saccade on a success. Timed dismissal then removes even the chance to catch up.
Desktop dialogs that pin the primary button at the bottom and write the error under the window title open the same split. The hand is not in the way, so miss rates drop, but on a long form the eyes have already moved to the next field.
Studying it
Place the same brief confirmation above the button, mid-content, and at the top of the screen, and test whether it is seen before it auto-dismisses. Eye tracking is the clean measure: did a fixation land in the banner’s band during its lifetime. Without a tracker, ask “did that just succeed?” the instant the banner is gone, and forbid looking back.
Independent variables: vertical position of the feedback, duration, whether the primary button is at the bottom or the top. Dependent variables: detection before dismissal, time to first fixation on the feedback band, subsequent double submits.
Measure this in the rhythm of “tap, then fill the next field”. Staring at a banner on its own will erase the split.
Where it stops holding
If the feedback stays at the top until it is dismissed (a blocking error, a warning that must be handled), the split still costs discovery time but does not equal invisibility — people can look up after the current action. After a full-page jump, or after scrolling sends the button off-screen, yesterday’s “top” may no longer be the top. Landscape and an unfolded foldable shorten the pixel distance between poles, and the split weakens. Feedback parked just above a bottom button, rather than in the status-bar band, is not this split.
Applying it
- Write short-lived success or failure for a bottom primary button above the button or inside it, not in the top band under the status bar.
- Events that must use a top notification should persist until handled, or leave a local mark on the button that does not auto-dismiss.
- In desktop dialogs, put validation errors next to the field that failed, not under the window title.
- How to check: keep the product’s real banner duration, tap the bottom button, move gaze to the next field as the task requires, and ask “did it succeed?” If the answer is missing, the vertical split is doing the work.