← All studio notes

Mobile game development / DIJION

One more round or later? Designing mobile game session endings

A session-ending guide connecting level results, save points and exit options so players understand where they will return.

Mobile games often fit into journeys, short breaks and gaps between other tasks. There may be no time for another round. In an illustrative level-based game, the result screen should support leaving confidently as well as continuing. Ending a session is an ordinary use case, not a failure to engage with the product.

Define a natural stopping point

A round result, reward grant and completed save may happen at different times. Define the boundary at which leaving is safe. Progress saved should reflect a real persistent outcome. If confirmation takes time, explain waiting and exit behavior; do not leave people assuming that closing the app guarantees every operation will finish in the background.

Name the continue and leave choices

Scroll the table horizontally to see all columns.

Example session-ending decisions
ActionEffectReturn point
Next levelStarts another roundNew round save policy
Main menuEnds the current roundCompleted level
Take a breakApplies the pause policyExplained safe return point

Avoid unnecessary friction when leaving

Repeated promotions or confirmations can obstruct a clear intention to leave. If there is no actual loss, an understandable exit may be more appropriate than asking Are you sure each time. When progress is at risk, explain its scope precisely. Losing an unfinished round should not sound like losing every previously completed level.

Match the next opening to the ending

The next opening should honor the return point previously explained. A daily task or time-limited event may have changed; avoid presenting an old result as a current event. If reminders are considered, review permissions and preferences separately. Choosing to end a session does not authorize future notifications by itself.

Walk from ending to reopening

  1. Leave from results and reopen the application.
  2. Disconnect while a save is pending and inspect the state.
  3. Compare leaving before and after the next round begins.
  4. Check changed event information after a longer absence.

The deliverable is an ending-and-return map. A short session can still feel worthwhile when the player understands what was completed and where play will continue.