Ratings cover two jobs that share a name and very little else: a picker that collects one person's score, and a summary that reports the average a population has already left. The picker is an input with a small labelled scale and a hit target per step. The summary is read-only, a number, the glyphs drawing it, and the count of responses behind it, which is the part that says whether the average deserves any trust.
A score on its own gives you a mood and nothing to act on, so the picker worth shipping is the one with a note field under it: the number sorts the responses and the sentence explains them. One detail decides whether the picker works at all, and it is easy to miss, every step has to look different. A row of identical glyphs filling left to right says only that a rating was left. A row of faces running from angry to grinning says which one, which is the entire job of the control.
A resolved support ticket ends with a five-face pick and a note field. The faces take a second to answer and the note is where the reason lives; without it the score has no route back to a cause.
A store page leads with the average, the total it was drawn from, and a link into the reviews themselves. Stacked, that anchors the top of a page; the same figures inline suit a dense comparison row.
A prompt after a completed task asks how it went and takes a sentence with the score. It gets answered because it is short, it is in context, and ignoring it blocks nothing the person came to do.
A heart score counts affection rather than quality. Drawn from its own solid, half and outline glyphs, it reads as saves and likes and is not mistaken for a review average that came out of a survey.
Five is the usual answer, because a person can hold five positions in mind at once and each one can be given a name, from very dissatisfied through to very satisfied. Ten points buy a precision nobody has: the middle values blur together and responses cluster anyway. Pick the scale your reporting genuinely distinguishes, then label the ends so the values mean the same thing to everyone.
Show halves in a summary and not in a picker. An average is a computed number, so a half-filled glyph renders it honestly; a picker that accepts halves asks for a precision people do not have, and the targets get small enough to mis-tap. Expose the underlying value as text as well, so the meaning is not carried by glyph shapes alone.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Ratings cover two jobs that share a name and very little else: a picker that collects one person's score, and a summary that reports the average a population has already left. The picker is an input with a small labelled scale and a hit target per step. The summary is read-only, a number, the glyphs drawing it, and the count of responses behind it, which is the part that says whether the average deserves any trust.
A score on its own gives you a mood and nothing to act on, so the picker worth shipping is the one with a note field under it: the number sorts the responses and the sentence explains them. One detail decides whether the picker works at all, and it is easy to miss, every step has to look different. A row of identical glyphs filling left to right says only that a rating was left. A row of faces running from angry to grinning says which one, which is the entire job of the control.
A resolved support ticket ends with a five-face pick and a note field. The faces take a second to answer and the note is where the reason lives; without it the score has no route back to a cause.
A store page leads with the average, the total it was drawn from, and a link into the reviews themselves. Stacked, that anchors the top of a page; the same figures inline suit a dense comparison row.
A prompt after a completed task asks how it went and takes a sentence with the score. It gets answered because it is short, it is in context, and ignoring it blocks nothing the person came to do.
A heart score counts affection rather than quality. Drawn from its own solid, half and outline glyphs, it reads as saves and likes and is not mistaken for a review average that came out of a survey.
Five is the usual answer, because a person can hold five positions in mind at once and each one can be given a name, from very dissatisfied through to very satisfied. Ten points buy a precision nobody has: the middle values blur together and responses cluster anyway. Pick the scale your reporting genuinely distinguishes, then label the ends so the values mean the same thing to everyone.
Show halves in a summary and not in a picker. An average is a computed number, so a half-filled glyph renders it honestly; a picker that accepts halves asks for a precision people do not have, and the targets get small enough to mis-tap. Expose the underlying value as text as well, so the meaning is not carried by glyph shapes alone.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.