How to Collect In-App Feedback From Closed Testers
Add a feedback button to your test build in an afternoon: what to capture automatically, simple backends (email, form, Firestore), and privacy considerations.
Short answer
Add a Send feedback button (in Settings or via a shake gesture) that opens a short form, then attach app version, device model, Android version and current screen automatically. Send it to a simple backend: a prefilled email, a Google Form, or a database collection. Testers give far more feedback when it takes ten seconds.
Why in-app beats “email me”
Testers forget where your email is, and when they do write, they leave out the version and device. In-app feedback catches the moment of frustration and adds context automatically.
What to capture
| Field | Source |
|---|---|
| Message | Tester types it |
| Optional screenshot | Capture the current screen with permission |
| App versionName and versionCode | BuildConfig |
| Device model and Android version | Build.MODEL, Build.VERSION |
| Current screen | Your navigation state |
| Pseudonymous tester ID | Your auth, or a random install ID |
Three simple backends
- Prefilled email intent. Zero backend: open the mail app with subject and device info filled in. Easiest, but some testers have no mail app set up.
- Google Form. Open a form with prefilled fields via URL parameters. Responses land in a spreadsheet.
- Database collection. Write feedback documents to Firestore or Supabase with security rules that allow create-only. Best for triage at scale.
Make it easy to find
- A visible Feedback item in the main menu during the test (remove or hide it later).
- An optional shake-to-report gesture.
- A prompt after key actions: “How did that go?” with thumbs up or down and a text box.
Privacy
Feedback can contain personal data, and screenshots can capture other people’s content. Ask before attaching screenshots, don’t collect more than you need, and declare it in your Data safety form.
Then use it
Sort feedback daily (see triage tester feedback), reply so testers know they’re heard, and log what you fixed. That log is the backbone of your production access answers.
Frequently asked questions
Should I remove the feedback button after launch?
Many apps keep a quieter version in Settings. Real users give useful feedback too.
How do I stop spam in a feedback database?
Require sign-in, or use security rules that only allow creating documents with expected fields and sizes, plus rate limits on your backend.
Is Play’s private feedback enough?
It’s a useful extra, but it lacks device context. An in-app channel gives you much more to act on.
Sources and how we keep this accurate
- Play Console Help: Provide information for Google Play’s Data safety section
- Play Console Help: App testing requirements for new personal developer accounts
Policy facts are checked against Google's own documentation on the date shown above. Google can change requirements at any time, so confirm in your Play Console. Where we give advice or estimates rather than Google's rules, we say so. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.
Need 12 testers? Get them free.
Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.
Start freeKeep reading
How to Triage Tester Feedback in a 14-Day Closed Test
Do Closed Testers Have to Leave Feedback?
How to Give App Feedback Developers Actually Use
How to Test In-App Purchases With License Testers
How to Write Release Notes for Closed Test Builds
Add Firebase Crashlytics to Your Closed Test Build
Browse all guides, or see the quick answers, guides and comparisons.