Mobile game development / DIJION
What are you changing when mobile game difficulty increases?
A difficulty plan separating speed, complexity and failure cost, with focused level comparisons informed by observed play.
Slowing every obstacle may look like an easy response to a difficult level. The problem could instead be an unclear objective. In an illustrative puzzle game, introducing a new rule, a short timer and a high failure cost together obscures which change caused the problem. Name the component of difficulty before adjusting it.
Treat difficulty as several dimensions
Decision count, movement precision, information load and retry cost place different demands on players. Record these dimensions separately in a level plan. Holding some steady while changing another makes learning easier to examine. This is a design tool for discussing the intended experience, not a universal balancing formula or a promised performance improvement.
Record what changes between levels
Scroll the table horizontally to see all columns.
| Variant | Changed dimension | Behavior to observe |
|---|---|---|
| A | New rule, generous time | Discovering the rule |
| B | Same rule, shorter time | Deciding under pressure |
| C | Same time, longer retry | Willingness to continue after failure |
Interpret failures by their causes
Did the player pursue the right goal, miss an input or misunderstand the outcome? Recording only lost hides these differences. Asking about strategy can help, but separate observation from a later explanation if questioning disrupts play. Behavior in a few sessions should not be presented as a preference shared by the entire audience.
Make assistance and difficulty choices clear
Hints, more time and input assistance are different interventions. If an example hint only explains a rule, say so instead of silently changing another setting. Disclose any effect on saves or scoring before selection. Present assistance as an available option rather than framing it as an embarrassing consequence of failure.
Keep a balancing round focused
- Choose one learning question and one changed dimension per round.
- Record objective understanding separately from input errors.
- Check retry time and rediscovery of assistance.
- Keep novice and experienced-player observations distinct.
The result is a map of which skills a level requires and when, rather than one ideal difficulty number. The next iteration should address a specific uncertainty in that map.