Mobile game development / DIJION
When a call interrupts the game: pause and resume design
An interruption matrix separating backgrounding, persistence, audio and reconnection for local play and online sessions.
A call can arrive halfway through a move. The player may lock the screen or switch apps. Returning to a running game is not enough: progress, input, audio and time must still match expectations. Treat interruption as an ordinary mobile condition, rather than an exceptional error.
Separate local pausing from an online world
A local single-player level may be paused while a real-time online session may continue. A Paused label does not remove that difference. In an illustrative networked game, explain if the world continues after disconnection and avoid presenting an old screen as current server state.
Scroll the table horizontally to see all columns.
| Interruption | Local game | Online session |
|---|---|---|
| Switching apps | Apply simulation and input policies | Assess session and connection state |
| Screen lock | Check audio and persistence behavior | Reconcile with server state |
| Process termination | Restore from an actual save | Verify session validity |
| Brief notification overlay | Check focus and input | Do not confuse visibility with connectivity |
Pausing is not the same as saving
A level held in memory differs from a persistent save. Android’s lifecycle documentation describes how a background process may be terminated. Avoid a vague promise to return exactly where the screen closed; specify the safe recovery point. An interrupted save write needs its own test.
Avoid making return an instant penalty
In a fictional reflex game, an obstacle colliding immediately on return may feel unfair. Consider an explicit Resume action or suitable preparation interval. Choose according to the game rather than adding the same countdown everywhere. Check that the tap dismissing a panel does not also trigger an unintended game action.
Restore audio and input deliberately
A visible screen does not necessarily mean audio sources and input devices are ready. Repeated pause/resume cycles can expose overlapping music, stuck controls or duplicate timers. Returning to play should not override the person’s saved sound preference.
Interrupt at different moments
- Background before a move, during it and on the result screen.
- Repeat the interruption several times; progress must not be applied twice.
- Restart the application and verify the actual save point.
- Disconnect and reconnect; the local image must not misrepresent the server result.
Add the expected save point, audio behavior and return action to every row. This lets the lifecycle implementation and the promise made to the player be assessed in the same matrix.