STEP 7 OF 8
Write useful feedback
Turn your observations into clear answers.
Use observation → impact → example. Describe what happened, how it affected your play, and one concrete moment that supports your answer. Mention things that worked as well as friction.
Too vague: “The tutorial was bad.”
“At the first locked door, I tried interacting with the handle because it was highlighted, but the game needed me to find a switch behind the camera. I spent about two minutes circling the room, so a clue near the door would have helped me understand the next step.”
Your Firstplay feedback
Answer each required question with yes or no, then explain in 2–3 sentences and at least 30 words. The form asks one question at a time and blocks incomplete answers. Creator-specific written questions follow the same explanation rules.
- Would you wishlist this game?
- Would you choose to play this game again?
- Were the goals and next steps clear?
- Did the controls feel intuitive?
- Did the game run without technical problems?
Finish the overall rating and confirm you actually played. An honest “no” qualifies just as much as “yes”; you are paid for useful work, not praise. Use your own observations rather than copied, invented, or padded answers.
Firstplay’s submission is written feedback. Screenshots and recordings support your notes; they do not replace the answers. If the brief requests evidence, include a creator-accessible, view-only link in the relevant written answer or use the sharing method in the brief. Check access before submitting; keep unreleased material private.