Designing Mobile Game Mechanics
Every second mobile project fails due to boring mechanics: the player leaves by the third minute, day one retention drops below 20%. The cause is a poorly designed feedback loop. We design the core loop so that every tap delivers a dose of dopamine and the meta loop makes players return daily. For example, for a hyper-casual slicer, day one retention grew from 28% to 41% after adding difficulty escalation through an AnimationCurve. Time saved on balancing by externalizing parameters into ScriptableObject: up to 30%. We guarantee retention increase to 41% based on practice. Contact us for a project analysis.
How core loop differs from meta loop
Core loop — an action repeated every 30–120 seconds. In Tower Defense: place a tower → wave of enemies → result → resources → next wave. In an idle game: tap → coins → upgrade → more coins per second → tap less. The loop must be understandable without a tutorial and be satisfying on its own. Meta loop — progress over several sessions: unlocking new towers, characters, levels. Meta loop retains the player between sessions — gives a reason to return tomorrow. A common mistake: designing meta loop before core loop. If base gameplay is boring, no progression saves retention. In a mobile game, core loop should be 3 times shorter than on PC due to attention span differences.
How mobile constraints change mechanics
The mobile screen dictates mechanics. A click at 100 ms on PC — a tap at 200 ms on a touchscreen. A mouse with pixel precision — a finger 10 dp wide. These are not drawbacks — they are design parameters. As Game Design Workshop states, mobile mechanic design must account for these delays.
Works well on mobile:
- Swipe mechanics (Tinder-style, match-3, slice)
- Tap and hold (charging, aiming)
- Time management (Cooking Dash) — limited time on a small screen creates tension
- Pinch to scale (strategies, city simulators)
- Gyroscope (mazes, racing games) — via
Input.gyroin Unity
Works poorly:
- Precise aiming (mouse shooters)
- Simultaneous control of multiple objects
- Fast reactions (<100 ms) — physiological limit of touchscreens
Designing mechanics with monetization in mind
Monetization should not break the core loop. Energy system (lives in Candy Crush) — artificial throttling of the core loop. Works in terms of IAP but damages user experience. Alternative: cosmetic monetization (skins, effects) — does not limit gameplay, preserves player experience. If the project uses ad monetization (rewarded video via Unity Ads, AdMob, IronSource), mechanics are designed with "decision moments" — points where the player willingly watches an ad: continue a level after losing, double the reward. Forced ads destroy flow. Reducing balancing costs through parameterization: up to 40%.
How to design a mechanic: 5 steps
- Define the genre and target audience. For hyper-casual, core loop should be 5–30 seconds; for RPG, 10–30 minutes.
- Draw a state machine of input event → state → effect. Ensure all loops close.
- Externalize numeric parameters (speed, damage, timers) into
ScriptableObject(Unity) or JSON config — this speeds up balancing 3 times compared to hardcoding. - Build a prototype by day five and test retention on 20 subjects.
- Iterate: after mechanic tweaks, day one retention increases on average 10–15%.
// Example state machine for a slicer (pseudocode) states: IDLE, SWIPING, CUTTING, COMBO, EXPLOSION IDLE -> SWIPING (on touch start) SWIPING -> CUTTING (if collider hit) CUTTING -> IDLE (if combo timer > threshold) CUTTING -> COMBO (if combo multiplier active) IDLE -> EXPLOSION (on bomb touch) -> GAME_OVER Case study: Hyper-casual slicer
A hyper-casual game on Unity, mechanics: slicing (slicer). Core loop: swipe at objects → cutting → combo multiplier → high score. Initial tests showed: players lost interest by the third minute — lack of escalation. We added dynamic object speed increase plus new types (uncuttable "bombs") via an AnimationCurve in Unity — day one retention rose from 28% to 41%.
Average payer conversion after implementing rewarded video to continue playing reached 3.5%.
Documenting mechanics
Each mechanic is documented in a GDD with:
- Description of player action
- Expected feedback (what they see/hear)
- Parameters (numbers, timers, multipliers) — in format for
ScriptableObject - Edge cases: what happens at 0 HP, when inventory is full, on connection loss
Parameter constants in code are the enemy of balance. All numeric parameters are externalized to ScriptableObject or JSON config. Game designer can tweak balance without a developer.
Typical mechanics by mobile genre
| Genre | Core loop | Key mechanics |
|---|---|---|
| Hyper-casual | 5–30 sec | Single input, difficulty escalation |
| Match-3 | 2–5 min | Cascade, special tiles, boosters |
| RPG | 10–30 min | Combat, loot, leveling, quest |
| Tower Defense | 5–15 min | Placement, wave management, economy |
| Idle | Passive | Tap, upgrade, offline earnings |
| Runner | 1–3 min | Obstacle avoidance, collection |
Typical mistakes in mechanic design
| Mistake | Solution |
|---|---|
| Designing meta loop before core loop | First make core loop engaging |
| Hardcoded balance parameters | Externalize to ScriptableObject |
| Ignoring touch latency | Account for 200 ms tap delay |
| Forced ads in core loop | Use rewarded video at decision moments |
What is included in the work
- Genre and target audience analysis
- Core loop design considering mobile input
- Description of all mechanics with balancing parameters
- State machine diagrams for key systems
- Documentation in GDD format (mechanics sections)
- Monetization recommendations without breaking gameplay
- Prototype verification of key mechanic (by agreement)
Timeline
3–5 working days for mechanic design of hyper-casual or casual project. For midcore RPG / strategy with several interconnected systems — 5–10 days. Price is calculated individually after concept analysis.
Contact us for a project evaluation. Order end-to-end mechanic design and get a prototype for retention testing within a week.