Mobile game development / DIJION
Reward feedback in mobile games: explaining what was earned
A reward-feedback guide separating animation from persistent grants across retries, interruptions and grouped results.
A glowing chest or increasing counter suggests that something was earned. Animation alone is insufficient if the player cannot tell what it was, under which condition it was granted and where it went. In an illustrative puzzle game, distinguish the level reward from an optional bonus. Celebration should clarify the result rather than conceal it.
Separate the grant from its presentation
Persisting a reward and playing its result animation are separate events. Closing the screen should not lose an accepted grant; replaying the animation should not grant it again. If a remote service must confirm the reward, communicate that state. Completion of a local visual effect is not evidence of server acceptance.
Explain the reward in concrete units
Scroll the table horizontally to see all columns.
| State | Explanation | Next information |
|---|---|---|
| Level completed | You earned one hint | Hint balance updated |
| Awaiting confirmation | Reward is being verified | Wait without granting twice |
| Inventory full | Item was not added | Offer a suitable safe option |
Keep grouped results understandable
If several rewards appear in sequence, make them available in a summary afterward. Requiring a tap for every item can unnecessarily extend the flow. Explain that Skip skips presentation rather than forfeiting the grant. Starting another level should not let a tap closing the reward layer accidentally activate an action underneath.
Do not rely only on sound or sparkle
Make reward type, quantity and effect understandable through readable text as well. Review icons and labels together for color-vision differences and muted play. Preserve the main action during an elaborate celebration. If a special reward resembles an ordinary result, explain its condition in a brief label instead of depending entirely on visual emphasis.
Exercise reward states
- Background the app while a reward is being applied.
- Reopen results; the reward must not be granted again.
- Check the effects of Skip and Continue separately.
- Identify the amount and destination with sound off.
The acceptance artifact is a reward-state contract, not an animation file. Celebration becomes reliable feedback when the visible amount and persistent record describe the same outcome.