In this guide
You do not have to wait until everything is done. Early feedback is cheap to act on. The risk is noise: testers report the missing settings screen, the placeholder icon and the bug you already know about, and bury the one finding you needed.
The fix is to scope the test. Tell testers what is ready, what is not and what you want to learn.
Step 1: Decide the one question
Pick one thing the round must answer. Examples: - Is the sign-up flow understandable? - Does the main screen make sense without explanation? - Does the app run on different phones?
One question per round. If you have three, run three rounds.
Step 2: Write a scope statement
Template (adapt it):
Status: early build, not feature complete. Please look at: [the one area, for example onboarding and the first task]. Please try: [3 actions]. Please ignore: the items in the known-issues list below. Please report: device, OS version, what you did, what you expected, what happened.
Example (marked as example): "Early build of a habit tracker. Please look at creating your first habit and checking it off. Ignore the empty settings screen and the placeholder icon."
Step 3: Keep a known-issues list
Write down everything you already know is broken or missing. Share it with the scope statement.
- Missing screens or features
- Bugs you have not fixed yet
- Placeholder text, icons and images
- Things you are unsure about (mark them, so testers do not guess)
A short list saves you reading the same report many times.
Step 4: Set expectations
Say plainly that it is unfinished. People are kinder and more specific when they know. Do not promise to fix everything; say you read every answer.
Step 5: Sort what comes back
- Inside the scope and repeated: act on it.
- Inside the scope, one report: check if you can reproduce it.
- Outside the scope: keep it in a "later" list and do not reply to each.
With AppReviewX
AppReviewX gives you private, structured feedback from other developers, who are used to unfinished builds. You say what testers should check, and they answer against that. One feedback you write earns one credit; one credit buys feedback on your app. New accounts start with 0 credits. Nothing is traded for store reviews or installs.
Start free and paste in your scope statement.
Related: How to write test instructions testers will follow, Get feedback on your app idea before you build it. Back to the overview.