Tithi MondalBlog

Guide5 min readUpdated

In-App Feedback: Buttons, Rating Prompts and Bug Forms

In-app feedback done well: where to place the feedback button, when to show the app rating prompt and what a bug report form should ask.

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

In-App Feedback: Buttons, Rating Prompts and Bug Forms: cover illustration

A user opens a loan app, enters a wrong OTP three times and gets blocked. At that exact moment the app shows a pop-up: "Enjoying the app? Rate us 5 stars." The user is angry, and the app has just invited the angriest possible review.

In-app feedback means giving users a simple way to tell you their opinion, a problem or a request from inside the product, at the right moment. It includes the feedback button, the app rating prompt and the bug report form. Done well, it gives you honest information from real users. Done badly, it interrupts people and fills your store page with one-star reviews.

When should you ask for feedback in an app?

Ask for feedback right after the user has finished something successfully, and never in the middle of a task. The user feels pleased at that moment, the memory is fresh, and you are not blocking them.

Good moments:

  • After a first order is delivered, or a booking is confirmed.
  • After a student completes a live class or a lesson.
  • After a support chat is closed.
  • After a user has used a feature several times.

Bad moments:

  • On the first launch, before the user has done anything.
  • During sign-up, OTP entry or a UPI payment.
  • Immediately after an error or a failed upload.
  • Every time the user opens the app.

On fintech screens such as loan or tax flows, any pop-up while the user enters money details feels wrong, so I keep those steps clean and ask later, on a calm screen. The same thinking applies to pop-ups, modals and bottom sheets: an interruption must earn its place.

Ask rarely. A good rule is to ask once for each moment and then wait, and never ask again if the user has already dismissed the request.

How should a feedback button look and where should it go?

Place a permanent feedback button where users look for help, and label it with plain words such as "Help and feedback". It should be easy to find, but it should not compete with the main action.

Three placements work for most apps:

Avoid a floating button over every screen. It covers content, gets in the way of the thumb on small phones and teaches users to ignore it.

Keep the feedback form short: one tap rating or three simple face choices, one optional text box and a submit button. Allow typing in the user's own language, and mention that voice input on the keyboard works. For wording, see UX writing and microcopy for apps.

How do you design an app rating prompt?

Use a two-step prompt. First ask a private question: "Are you enjoying the app?" If the user says yes, offer the store rating. If the user says no, open your own feedback form.

StepUser says yesUser says no
1. Private question"Glad to hear it""Sorry about that"
2. Next screenOffer to rate on the app storeOpen a short form: "What went wrong?"
3. Follow-upDo not ask again for a long timeReply to the user within a day or two

This approach gives unhappy users a place to be heard, and it gives you a chance to fix the problem before a public review. Be honest about the purpose. Do not trick people or hide the "No thanks" option. Store rules on rating prompts change, so check the current platform guidelines before you build.

Wording matters. "Rate us 5 stars" asks for a favour. "How was your experience?" asks for the truth. Also make sure the "Not now" button is as visible as the main button. A user who can dismiss the prompt quickly will not hold it against you.

For how ratings and reviews appear to other users inside a marketplace, a different subject, see ratings and reviews UI design.

What should a bug report form include?

A bug report form should ask for as little as possible and collect the rest automatically. A tired user will not write three paragraphs.

Ask the user for:

  1. What happened? One text box with a hint: "For example, the payment page kept loading."
  2. What did you expect? Optional.
  3. A screenshot. Optional, with an "Attach" button.
  4. How should we reach you? Default to the phone number the user already gave. Offer WhatsApp as a choice.

Collect automatically, and tell the user: the screen name, the app version, the phone model and the time. With the user's permission, this saves many follow-up questions.

Use plain language, not "Submit a defect ticket". Use words such as "Report a problem". After sending, show a confirmation with what happens next: "Thank you. We will reply on WhatsApp within 2 working days." Only promise the time that your team can keep.

Include a way to report a problem even when the app is in trouble. If the app fails to load, put a link to a WhatsApp number or an email address on the error screen, as in empty states, loading and error screens.

What should you do after users send feedback?

Read it, group it, answer it and tell people what changed. Feedback that goes into a black hole makes users stop writing.

A simple weekly routine, 30 minutes long:

  • Read all new feedback and bug reports.
  • Add each one to a sheet with a tag: bug, confusing screen, missing feature, praise.
  • Count the tags, and look at which screen is named most.
  • Pick one or two items to fix, and reply to those users personally.

Answer in the same language and channel the user used. A short reply such as "We fixed the slow payment page. Thank you for telling us" turns a complaint into loyalty.

In-app feedback has limits. It shows what people notice, not what they quietly give up on. For that, watch real people use the product, as in usability testing on a small budget, and read the form design basics in form design best practices.

If your app has no clear place for feedback or support yet, I can design these screens as part of mobile app design, and you can write to me to talk through where they belong.

Frequently asked questions

When is the best time to show an app rating prompt?

+

Show it after the user has finished something successful, such as a delivered order or a completed lesson. Never show it during a payment, after an error or on the first launch.

Should the feedback button float on every screen?

+

Usually no. A floating button covers content and gets ignored. A clear 'Help and feedback' row in settings, plus a small question after key tasks, works better.

How long should a bug report form be?

+

Ask for 3 or 4 things at most: what happened, an optional screenshot and a contact method. Fill in the screen name, app version and phone model automatically.

Can I collect feedback on WhatsApp instead of inside the app?

+

Yes, and many Indian users prefer it. Offer both: an in-app form for quick feedback, and a WhatsApp link for people who want to talk to a person.

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.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.