Article5 min readUpdated
Ratings and Reviews UI Design: Show Reviews Honestly
Ratings and reviews UI design: star rating screens, feedback form after an order, review lists, summary bars and honest ways to show low ratings.
By Tithi Mondal, UI/UX Designer
A customer in Kolkata receives a biryani order, finds it good, and closes the app. Ten minutes later a pop-up asks her to "Rate your experience" before she can see her next order. She taps one star by mistake and moves on. Ratings and reviews UI has to prevent this kind of bad data. A rating is a score the user gives, usually from 1 to 5 stars, and a review is the written comment that goes with it. Together they help the next buyer decide, so the screens must be easy to use and honest to read.
When should you ask for a rating?
Ask for a rating right after the user has received what they paid for, and only once. Too early and the rating is a guess. Too late and they have forgotten.
- Food or grocery: after the order is marked delivered, and again after about an hour as a gentle notification if they have not rated.
- Ride or service: at the end of the ride, on the receipt screen.
- Learning app: after a lesson or a live class ends.
- Marketplace product: a few days after delivery, when the user has used the item.
Offer the rating in the place where the result appears, not as a surprise pop-up on another screen. For reminders, see notification UX for push, SMS and WhatsApp. Always include "Not now" so the user can leave without penalty.
What does a star rating screen look like?
A star rating UI is five large stars the user can tap once, followed by optional detail. The order, top to bottom, is below.
- Context. What is being rated, with a photo. "How was your order from Maa's Kitchen?"
- Stars. Five stars, each at least 44 pixels wide, with space between them. Tap to select.
- A label under the stars. It changes with the score: "Poor", "Fair", "Good", "Very good", "Excellent".
- Follow-up chips. After the tap, show 3 to 5 quick reasons that match the score. For 5 stars: "Tasty food", "On time", "Good packing". For 2 stars: "Late", "Cold food", "Wrong item".
- Optional text box. Placeholder: "Tell us more (optional)".
- Optional photo. "Add a photo".
- Submit button. "Submit". It works as soon as a star is chosen.
Do not make users type before they can submit. Quick chips give structured data that a team can count, and they are easy to tap on a phone with one hand.
How do you design the feedback form after an order?
The feedback form after an order should take under 30 seconds. Keep it to one screen, split into the thing that matters most. For a food order, rate the food and the delivery separately, because a good meal can arrive late.
- Question 1: "How was the food?" with 5 stars.
- Question 2: "How was the delivery?" with 5 stars.
- Optional: a comment and a photo.
For low scores, change the next step. If a user gives 1 or 2 stars, show: "We are sorry. What went wrong?" and a button "Contact support". This sends the unhappy user to a person, not to a public review. It is not hiding the review. The user can still post it. It gives the team a chance to fix the issue. See in-app chat and support screen design.
After submitting, show a clear success message: "Thank you. Your review helps others choose." Then take them back to where they were.
How do you show reviews honestly?
Show reviews honestly by displaying the real average, the real count and a full range of scores. Trust grows when the page looks like real life.
Put this at the top of a product or place page.
- Average and count: "4.3 out of 5, from 218 ratings".
- Bars for each star level: 5 star, 4 star, 3 star, 2 star and 1 star, each with a bar and a number.
- Sort options: "Most recent", "Highest rated", "Lowest rated", "With photos".
- Verified label: "Verified purchase" only for people who really bought.
- Date and name: "Anita, 3 November 2026". A first name or initials is fine.
- Owner reply: a short, polite reply under negative reviews.
Several habits damage trust.
- Showing only 4 and 5 star reviews.
- Rounding 4.2 up to 4.5.
- Paying for reviews or filling the page with copied text. The reader can often tell.
- Hiding the count, so one review looks like a hundred.
- Removing a review only because it is negative. Remove only abusive or false content, and state your rule.
An honest 4.2 with real comments is more believable than a perfect 5.0 with three reviews. For wider guidance, see trust signals in website and app design.
What are the states of a ratings and reviews screen?
Each part of the flow has states that need wording.
| State | Example wording |
|---|---|
| No reviews yet | "No reviews yet. Be the first to share your experience." |
| Loading reviews | Grey placeholder rows |
| Failed to load | "Could not load reviews. Try again." |
| Already reviewed | "You rated this 4 stars. Edit your review." |
| Submitting | "Submitting..." on the button |
| Submit failed | "Could not send your review. Your answers are saved. Try again." |
| Review under check | "Thank you. Your review will appear after a quick check." |
| Not eligible | "Only people who bought this item can review it." |
Save the draft if the network drops. Nothing is more annoying than writing a paragraph and losing it. For more, see empty, loading and error screens.
Which review UI mistakes should you avoid?
- Asking for a rating on the first app open.
- Using a tiny star row that is hard to tap.
- Forcing a written review.
- Showing a rating without the number of people behind it.
- Using only English for the form while reviewers write in Hindi or Bengali. Allow any language, and see regional language app design in India.
- Burying the lowest-rated sort option.
- Using the store rating pop-up before the user has had a good experience.
On a seller app for a marketplace, I treat reviews as part of the seller's reputation, so the same honest rules apply to both buyer and seller sides.
If you need your rating and review flow designed so it collects useful feedback and earns trust, you can reach me through get in touch.
Frequently asked questions
When should an app ask for a rating?
Ask after the user has received the result, such as after delivery or after a completed class. Never ask during login or in the middle of a task.
Should a review form be compulsory?
No. Make the star rating one tap and the written text optional. Required text produces short, careless reviews and makes users skip the whole step.
Is it fine to hide negative reviews?
No. Hiding bad reviews damages trust once users notice, and in some cases can create legal problems. Show them, and reply to them politely.
How many stars should the scale have?
Five stars is the common choice and users understand it at once. Keep the labels simple: 1 means poor and 5 means excellent.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.