Claim all
Duration
Appx. 2 months
Role
1 UX designer, 1 UI artist, 1 UI programmer, 1 QA
Tools
Competitive analytics, Wireframes, Prototype
Challenge
UX efficiency vs. emotional reward
While designing the Bootcamp feature, I pointed out that making players manually claim rewards every time could cause repetitive fatigue from a UX standpoint and proposed a “Claim All” feature. However, others in the team had the assumption that pressing the Claim button each time enhanced the sense of achievement—requiring further persuasion to find balance.
D7 Retention hypothesis
Claim actions repeatedly occur throughout the play routine, especially in the transition phase from novice to expert players. This repetition was assumed to negatively affect D1, D3, and D7 retention by increasing friction and drop-off during early engagement.
Process
Discover
Self Diary Study & Journey Map
To validate the hypothesis, I conducted a self-initiated 7-day diary study and visualized the daily play routine in a user journey map to illustrate where claim fatigue occurs.
Validation from Real Player Data
The journey map influenced the UR team’s research plan after the soft launch, leading to two official diary studies with real players.
Benchmark References
I analyzed benchmark competitive mobile game (F2P FPS & AAA) to understand how their reward systems handle convenience and repetition.
Define
2-1 UX principle in gaming product
The smoother the control and routine surrounding core gameplay,
the deeper the player’s immersion and enjoyment
In R6M, How might we make gameplay loops feel seamless
so players stay fully immersed?
2-2 First journey map based on self-run diary study
The initial journey map clearly showed where claim interactions repeatedly interrupted player flow.
And it influenced UR team to conduct two rounds of diary studies for validation.
2-3 Second & Third Journey Maps — Bootcamp feature & Soft Launch Builds
Subsequent journey maps based on Bootcamp and Soft Launch builds revealed
that manual claim interactions were consistently one of the top-reported pain points across players.
2-4 Comparative Benchmarking — AAA Mobile Titles
By reviewing the reward collection flows of leading AAA mobile games,
I confirmed that the Claim All feature was a common, standardized convenience function proven to address similar UX challenges effectively.
Design
3-1 Define
When players tap the 'Claim all' button, then they get every eligible rewards at once.
3-2 User flow & Tap density
Assumed generic routine of an average D3 player
3-3 Feature highlights
Consistent placement of Claim All buttons,
Standardization of all screen types
Across all reward-claiming features, improving both development efficiency and user experience consistency.
Also, it is for creating clear design guidelines for future scalability
Unified reward-value hierarchy & visual feedback rules
To minimize edge cases and enhance predictability
Validate
-
Anticipated that no similar fatigue issues will reappear in subsequent UR testing.
-
Quantitative validation is underway through event tracking of Claim All usage rates.
Since multiple features were updated simultaneously, retention improvements cannot be solely attributed to this feature.
However, Likely to have a positive effect on D1–D7 retention and early engagement by reducing repetitive friction