Mobile games are shaped by where they are played rather than by what phones can do. Modern handsets are powerful, yet the design conventions still assume a few minutes of attention.
The device is used in gaps, not in blocks
Phones are carried everywhere and used during waiting, commuting and short breaks, which means a session can be interrupted at any moment by something more important.
A design that requires twenty uninterrupted minutes will be abandoned mid-session repeatedly, and every abandonment risks the player not returning.
So the unit of play becomes something that can be started and completed inside a short window, with a clean stopping point the player reaches naturally.
Interruption has to be survivable
A call, a notification or a locked screen can suspend the game without warning, and the operating system may close it entirely to reclaim memory.
Mobile games therefore save state constantly rather than at checkpoints, and progress is usually kept on a server so a closed application loses nothing.
That requirement shapes the architecture from the beginning, and it is one of the reasons ports from other platforms often feel wrong on a phone.
Energy systems formalise the session length
Many designs limit how much can be played at once through a resource that regenerates over time, which makes the short session structural rather than optional.
The stated purpose is pacing, and it does keep players from exhausting content quickly, but it also creates a scheduled reason to return.
The same system provides the point at which a payment can be offered, which is why it appears so consistently in games that are free to start.
Controls have to work with a thumb
Touch input is imprecise, occludes part of the screen and offers no physical feedback, so complex control schemes fail regardless of how well they are drawn.
Successful mobile games reduce input to a small number of unambiguous gestures, and often to a single tap, with the depth living in the decisions rather than the execution.
One-handed play is a further constraint, since a large share of use happens while the other hand is occupied with something else entirely.
Retention is measured in returns, not hours
The metric that matters commercially is whether a player comes back the next day and the day after, rather than how long any single session lasted.
Daily objectives, streaks and timed events exist to create a reason to open the application, and they are tuned around a short visit rather than a long one.
Design decisions that would seem strange on other platforms follow directly from that goal, and the short session is the assumption underneath all of them.