How to Write Game Feedback That Helps Developers

After playing a mobile game, it is easy to say “It was fun” or “I didn’t like it.” But to improve the game, the developer needs to understand the experience behind your opinion. What did you enjoy? Where did you struggle? Which feature did not work as expected?

Useful feedback helps a developer understand what to keep and what to change. You do not need to be a professional tester to provide it. Careful observation and a clear description of your own experience can make a difference.

1. Play the game before evaluating it

Base your evaluation on your own experience, rather than screenshots, a promotional video, or other players’ comments.

Take time to understand the basic controls, introductory instructions, and progression. If you encounter a problem, note where and when it happens.

You do not have to finish the entire game to share useful observations. If you have only played the opening levels, explain that. Early impressions can be valuable, as long as you do not claim to have tried features you have not used.

2. Give specific examples instead of general statements

“The controls are bad” communicates frustration, but it does not tell the developer much about the problem. Explaining which control failed, when it happened, and what you observed is more helpful.

General statement	More useful feedback
The controls are bad.	In the second level, the character sometimes did not respond when I swiped right. The same issue happened in three attempts.
The game is too difficult.	I completed the first two levels comfortably, but a new obstacle appeared in the third level without an explanation. I could not understand how to get past it.
The menu is confusing.	I struggled to find the settings button because I did not understand the icon on the home screen.
The graphics are nice.	The characters stand out clearly from the background. I could follow them easily, even during busy scenes.

3. Separate what you expected from what happened

One of the clearest ways to describe a problem is to explain what you expected first, then describe the actual result.

“When I tapped the pause button, I expected the game to stop. The menu appeared, but my character continued taking damage in the background.”

This explains both your action and its outcome. You do not need to know the technical cause. Accurately describing what you saw is enough.

4. Explain how to reproduce a bug

A developer can investigate a bug more easily if they can reproduce it. Whenever possible, include:

• The screen or level where the issue occurred.
• The actions you took immediately before it happened.
• The result you expected and what actually happened.
• Whether the same issue occurred when you tried again.
• Your device, operating system, and game version, if known.

For example:

“After completing level four, I tapped ‘Continue.’ The next level did not load, and the screen stayed black. When I restarted the game, my progress had been saved. I completed the same level again, and the problem happened a second time.”

If you can share a screenshot or video, make sure it does not reveal personal information, notifications, or account details.

5. Do not hesitate to share negative feedback

You do not have to give a game a high rating. Explaining bugs and weaknesses with specific examples helps developers improve their games. Concrete, constructive feedback is more useful than praise alone.

Focus your criticism on your experience of the game, rather than the developer’s personality or ability.

Instead of saying “You don’t know how to make a game,” explain: “The opening level did not explain how to jump, so I could not work out how to get past the first obstacle.” This identifies a problem the developer can address.

6. Distinguish personal preferences from technical problems

Not every negative experience is a software bug. Disliking a game’s pace, art style, or music may reflect a personal preference. These opinions can still be useful, but explain what kind of feedback you are giving.

• Personal preference: “I prefer faster-paced games, so the waiting time between levels felt long to me.”
• Usability issue: “The light gray menu text is difficult to read against the white background.”
• Possible technical bug: “I turned the sound off in settings, but the music at the end of the level continued playing.”

This distinction helps the developer interpret your feedback more accurately.

7. Describe what works well, too

Developers also need to know which features players value. This helps them preserve what works while making changes.

Instead of simply saying “Great job,” explain what helped you:

“The short explanation of why I failed at the end of the level helped me on my next attempt. I was able to progress without repeating the same mistake.”

Specific positive feedback can be just as useful as specific criticism.

8. Focus on clarity, not length

A useful evaluation does not have to be long. A few clear observations are more valuable than repeated general statements.

Describe the most important issues first. Distinguish a bug that prevents progress from a minor visual flaw. Avoid reporting the same problem several times in different words just to increase the number of issues listed.

If you suggest a solution, separate it from your observation. “I did not notice the button” is an observation. “Changing the button’s color might help” is a suggestion.

A simple feedback template you can use

Use these prompts to organize your thoughts. This is an optional writing guide, not a required evaluation form.

• What I tried: Which part of the game or feature did I experience?
• What worked well: What did I enjoy, and why?
• The problem I encountered: What happened, and where?
• What I expected: What did I expect to happen?
• Whether it happened again: Did the issue return when I repeated the steps?
• My suggestion: What might improve the experience?

How your contributions are recognized on MGM

On MGM, game evaluations and developers’ usefulness ratings can earn MGM points. Developers can also recommend players whose contributions they value or add them to their favorites.

A long comment or a high game rating does not automatically make an evaluation useful. What matters is sharing your real experience clearly enough for the developer to act on it.

To see which activities earn points and the limits that apply, visit the MGM points section of our Frequently Asked Questions.

You do not need to know how to solve every problem to help improve a game. Clearly describing one detail the developer has not noticed can be a valuable contribution.