How to Design a Results or Victory Screen

A results or victory screen—shown after completing a level or match—should celebrate the player's accomplishment, clearly convey how they did, and send them off satisfied, rather than being a dry data dump or anticlimactic end. Designing the screen to celebrate and convey results clearly is what makes it cap the experience satisfyingly.

Celebrate the accomplishment

A results or victory screen comes after the player accomplishes something (completing a level, winning a match), and it should celebrate that accomplishment—conveying a sense of achievement and reward, making the player feel good about what they did, rather than being an anticlimactic or perfunctory end. Celebrating the accomplishment means the screen has a sense of celebration and reward—visual and audio flourish, a sense of achievement, the satisfaction of accomplishment—so the player feels rewarded and good about their accomplishment, which caps the experience on a satisfying high note. A results screen that celebrates (conveying achievement and reward) sends the player off feeling satisfied, while a dry, perfunctory results screen (a flat data dump with no celebration) ends the experience anticlimactically, missing the chance to reward the accomplishment. Celebrating the accomplishment—conveying achievement and reward—is the foundation of a satisfying results screen, capping the experience by rewarding the player's accomplishment with a sense of celebration.

Convey the results clearly to inform and reward. Beyond celebration, the results screen should convey how the player did clearly—the results, the performance, the rewards earned—both to inform the player and to contribute to the reward. Conveying the results clearly means presenting how the player did (their score, performance, rewards, progress) clearly and understandably, so the player sees how they did and what they earned, which both informs them and contributes to the satisfaction (seeing a good result, earning rewards). The results should be conveyed clearly (readable, understandable) and in a way that contributes to the reward (presenting the accomplishment and rewards satisfyingly), rather than a confusing or dry data dump. When the results are conveyed clearly and rewardingly, the player understands and feels rewarded by how they did, which complements the celebration. Conveying the results clearly to inform and reward—presenting how the player did understandably and satisfyingly—completes a results screen that informs and rewards the player. Combining celebrating the accomplishment (conveying achievement and reward) with conveying the results clearly to inform and reward (presenting how the player did satisfyingly) is what makes a results or victory screen cap the experience satisfyingly—celebrating the accomplishment and clearly conveying the rewarding results, sending the player off feeling satisfied and informed. Designing the results screen this way—celebrate the accomplishment, convey the results clearly—is what makes it a satisfying cap to the experience, rewarding the player's accomplishment and conveying how they did satisfyingly, rather than the dry data dump or anticlimactic end that a poorly-designed results screen becomes. Celebrate the accomplishment and convey the results clearly, and the results screen caps the experience satisfyingly, sending the player off feeling rewarded and informed, which is what a good results screen achieves.

Make the common case effortless

Most of what a player does, they do over and over, and most of what you build will be exercised in a handful of common situations far more than in the edge cases. Optimising the rare and neglecting the frequent is a reliable way to make a game that's technically complete and practically annoying.

So spend your polish where the volume is: the action repeated a thousand times, the menu opened constantly, the path every player walks. Making the common case smooth and satisfying does more for how the game feels than perfecting the corners almost nobody reaches.

Protect the thing that makes it special

Every game that connects has some core spark — a feeling, a mechanic, a tone — that's the real reason people love it, and that spark is fragile. In the rush to add content, fix problems, and respond to feedback, it's easy to sand away exactly the quality that made the game worth making in the first place.

Know what your spark is, and guard it. When a change threatens the thing that makes your game distinctive, that's the change to question hardest, because a game can survive plenty of rough edges but rarely survives losing its soul.

Why finishing beats perfecting

The hardest skill in indie development isn't any particular technique — it's finishing. Most games that never ship didn't fail on talent; they failed on scope, polished forever, or chased one more feature. The developers who build a real body of work are almost always the ones who got good at choosing something small enough to complete and then completing it.

That's worth keeping in mind here, because it's easy to let any one part of development expand to fill all your time. Decide what 'good enough to ship' looks like, protect that line, and treat the endless list of possible improvements as a backlog rather than a set of obligations.

Plan for the parts you can't see

Once a game leaves your machine, a lot of what happens to it becomes invisible by default. Players run it on hardware you don't own, hit problems you never reproduced, and most of them never tell you — they simply move on. The gap between 'it works for me' and 'it works for everyone' is where a surprising amount of churn quietly lives.

So plan to see what you otherwise couldn't. Watching real players, capturing the bugs and crashes they hit with the context to fix them, and paying attention to where they drop off all turn invisible problems into ones you can actually act on — which protects the reviews and retention everything else depends on.

Consistency beats intensity

Indie development is a long game, and it rewards steady, sustainable effort more than heroic bursts. A little progress made consistently — on the game, on the marketing, on the community — compounds in a way that last-minute sprints never do. The developers who finish and find an audience are usually the ones who kept showing up, not the ones who worked themselves into the ground for a week and then burned out.

Build a pace you can sustain, and protect it. Momentum is fragile and expensive to rebuild, so steady forward motion is worth more than any single intense push.

A good results or victory screen celebrates the player's accomplishment and clearly conveys how they did, sending them off satisfied—not a dry data dump or anticlimax. Celebrate the accomplishment and convey the rewarding results clearly, so the screen caps the experience on a satisfying note.