AppReviewX Log in

Feedback on your first app: a guide for beginners

How to share a first app, what kind of feedback to expect and how to use it without getting discouraged.

In this guide

Showing your first app to strangers is uncomfortable. That is normal, and it is also the fastest way to improve. This guide helps you share it with a realistic scope and handle what comes back.

Is it ready to show?

It does not need to be finished or pretty. It needs to be usable enough that someone can try the main thing. Use this checklist before you share a first build.

  • [ ] The app installs and starts on a clean device.
  • [ ] One main flow works from start to end.
  • [ ] You know the one thing you want feedback on.
  • [ ] You wrote short instructions: what to try and how long it takes.
  • [ ] You know where testers should send feedback.
  • [ ] You tried it yourself once, as if you had never seen it.
  • [ ] Known problems are listed, so testers do not report them again.

Keep the scope small

Do not ask "what do you think?" Ask one or two things:

  • "Can you finish [task] without help?"
  • "Which step was confusing?"

A small question gets a useful answer. A big one gets "looks nice".

What feedback to expect

  • Bugs. Expect some. A crash on someone else's phone is normal, and it is data, not a verdict.
  • Confusion. Things that are obvious to you will puzzle others. This is the most valuable kind.
  • Taste. "I'd change the colours." Note it, but weigh it less than problems that stop people.
  • Silence. Some testers send nothing. Do not take it personally; ask fewer, easier questions next time.

How to use it without getting discouraged

  1. Read it once, then wait a day. The first reaction is rarely the useful one.
  2. Separate the app from yourself. Feedback is about a build, not about you.
  3. Sort into three piles: blocks use, annoys, nice to have.
  4. Fix the top two or three and ignore the rest for now.
  5. Look for repeats. One person's opinion is a note; the same point from several people is a finding.
  6. Ask again after your fixes, so you see progress.

What a first round usually leaves you with

A short list of real problems and a clearer idea of what to do next. That is a good result, even if the list feels long.

With AppReviewX

Developers give each other private, structured feedback, so your first app is not judged in public. 1 feedback = 1 credit, and new accounts start at 0 credits. You can also give feedback on other apps, which is a good way to learn what makes feedback useful. For Android apps there are Google Play test groups (12 testers, 14 days at a stretch).

Start free and share your first build.

Related: App testing for developers · What testers look for in your app · How to write test instructions testers will follow