Many mobile games lose up to 70% of users in the first three days – often because the mobile game progression system is poorly designed. We have seen this firsthand. After 10 years in game development and reworking over 50 projects from hyper-casual to midcore RPG, we know what works. In one project, D1 retention jumped from 25% to 48% after we rebalanced the XP curve and added daily tasks. A progression system is not just a set of levels – it is a mathematical model that keeps players coming back for months. Exponential curves are 30% better than linear ones for retention – proven by our projects.
How to balance the progression curve
The curve is a function linking time invested with perceived progress. A linear curve (xp_required = level * 100) does not work – the gap between level 1 and 50 feels the same. An exponential curve (xp_required = base * multiplier ^ level) gives a fast start but can become too steep with multipliers over 1.5. A polynomial curve (xp_required = A * level^2 + B * level + C) is a compromise, easy to iterate. We tune coefficients for target session time: for casual games, 3–5 minutes per session, 10–20 minutes per level. Parameters are placed in a ScriptableObject (Unity) or CSV so game designers can adjust balance without rebuilding. The cost for such a system typically starts at $5,000.
| Progression Type | Description | Example | When to use |
|---|---|---|---|
| Vertical | Player becomes stronger (levels, stats) | RPG with character levels | Long grind, RPG |
| Horizontal | New abilities without power increase (skins, classes) | Collectible cards | Safe monetization |
| Seasonal | Timed rewards, reset every 4–8 weeks | Battle Pass (Fortnite) | Regular player returns |
Why daily tasks matter
Daily challenges create a commitment to play every day. Technically: a task list is generated on first login, stored in the user profile, and reset at UTC midnight or local time. Use PlayerPrefs (Unity) or Firebase Realtime Database for cloud sync. Tasks with increasing difficulty keep players engaged longer.
Streak mechanics: consecutive login days → bonus rewards. Broken streak → motivation to pay for recovery (free recovery via rewarded video). At code level: timestamp of last login → difference in days → increment or reset counter.
Weekly and monthly milestones provide long-term goals with large rewards. Players see a week's progress ahead – this gives a reason to return.
Case study: midcore RPG on Unity + Firebase
The original linear progression delivered D7 retention of 8%. After we redesigned with an exponential XP curve, a 30-level battle pass, and daily tasks, D7 retention rose to 19%. Designing the system took 5 days and cost $3,000, leading to an estimated $15,000 extra revenue per month.Reward system
Rewards must be immediate and predictable. Loot boxes (random rewards) give a high emotional peak but are regulated by the App Store Review Guidelines (section 3.1.1) and laws in Japan and Belgium. We offer options without regulatory risk: a pity system (guaranteed rare reward every N tries), and a battle pass with fixed rewards per level. For monetization without pay-to-win, we use horizontal progression (skins, emotes) and cosmetics. We guarantee the reward system balances for your target audience.
Stages of designing a mobile game progression system
- Determine target session time and sessions per level.
- Choose mathematical model (polynomial, exponential) and tune coefficients.
- Design vertical, horizontal, and seasonal progression.
- Develop daily/weekly tasks with streak mechanics.
- Balance rewards per regulatory requirements.
- Prepare specification in GDD format and balance sheet.
| Parameter | Casual Game | Midcore RPG |
|---|---|---|
| Average session time | 3–5 min | 10–15 min |
| Target time per level | 10–20 min | 30–60 min |
| Number of levels | 50–100 | 100–300 |
| Battle pass included | Often | Almost always |
What is included in the progression system
- Mathematical model of the XP curve with target time per level.
- Structure of vertical and horizontal progression.
- Daily/weekly task system with streak mechanics.
- Reward system design considering regulations (pity system, battle pass).
- Specification in GDD format with numerical parameters.
- Balance sheet in Google Sheets / Excel for iteration.
Timelines
Designing a mobile game progression system for a casual or hyper-casual project takes 2–3 business days. For a midcore project with multiple interconnected systems (character level + equipment + guild + season) – 5–7 business days. The cost is calculated individually. Evaluate your project – write to us, and we will propose a solution tailored to your genre and budget.