The confirmation disappears after 3 seconds.
Someone who looks away can’t tell the invitation went out, and may send it again.
Proposed change. Keep the confirmation until it’s dismissed or the page changes, and put it in a status region.
The usability side of a review reads each attempt the way a design review would: missing feedback, wrong turns, repeated steps and dead ends. AI proposes each issue with the screens behind it. You decide what to do about it.
Analytics shows where people left. An attempt shows the screen it was on when the task got hard, and what it tried next.
1 retry · 1 duplicate · completed, at a cost
Heuristics a product designer would recognize, applied to a whole captured attempt, not a single screenshot.
Did the product say what happened, clearly and for long enough to be noticed?
Could the attempt tell where it was, and find the next step? Wrong turns and backtracks are counted and shown.
When something went wrong, did the screen say so, and was there a way back? Error messages are quoted exactly as they appeared.
Every issue has a title, why it matters to the perspective attempting the task, a proposed change, and the screen. Its tag says where it came from: a rule, the AI, or a person.
Someone who looks away can’t tell the invitation went out, and may send it again.
Proposed change. Keep the confirmation until it’s dismissed or the page changes, and put it in a status region.