Ratings

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.

12 blocks

Bar with a note

Post-purchase surveys, ticket close-out, anywhere the score needs a reason

Bar with a note, slide

A rating that should also say why, with one-tap reasons

Bar with a note, composer

Chat and ticket close-outs where the rating and the note are one step

Score stacked

Product page headers, App Store-style blocks

Score stacked, breakdown

Products where an average hides a lot of one-star ratings

Score stacked, recent

Scores that change, where the period matters

Score inline

Review section headers, comparison rows

Score inline, peek

Headers where the detail should be one step away

Score inline, compare

Comparison tables of products or plans

Heart score

Saved and favourited counts, where the summary should not read as a star review

Heart score, love it

Listings and saved items people can join

Heart score, fill

Guest-love summaries with a period switch

01

Using Ratings

Reach for it when

  • Closing a support ticket, where the score needs a reason beside it
  • A product page header that has to carry the average and the number behind it
  • A one-off survey after a purchase, where a short scale is all you can fairly ask for
  • A saved or favourited count that should read as affection rather than as a review

Reach for something else when

  • You need to know why more than how much: ask an open question, because a bare score points at no fix
  • Responses will only ever number a handful: an average over a tiny sample claims an authority it has not got, so show the raw count instead
  • The answer is yes or no: helpful against not helpful is two buttons, not a scale
02

Where it shows up

01

Ticket close-out

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.

02

Product page headers

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.

03

In-app feedback prompts

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.

04

Favourite counts

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.

03

Questions

Should a rating scale have five points or ten?

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.

How should a star rating handle half values?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.