Arium · UX/UI Design · 3 months
Arium Tournament Redesign
Making competitive cloud gaming easier to join, follow, and scale.
I worked within a three-person design team on Arium’s desktop and mobile tournament experience. The final direction turned a complex, state-heavy feature into clearer actions, accessible tournament details, stronger match context, and adaptable rankings.
Role
UX/UI Designer
Duration
3 months
Team
Three designers
Platforms
Desktop and mobile
Scope
Tournament experience
The problem
Players needed clarity across a changing tournament experience
Review and directional prototype testing highlighted four priorities: actions, essential details, match context, and rankings.
State-aware actions
Pair tournament condition with the action available to the player.
Accessible details
Place rules, rewards, and schedules near the moments where players need them.
Match context
Add summaries and available stream access where players already look.
Adaptable rankings
Support different tournament structures with more player context.
My role
Bringing structure to a complex feature
I proposed a structured way to select and estimate the design work, assisted with the tournament flow, contributed to journey mapping and final UI, created early feature structures and interactive prototypes, and proposed and created component-state documentation for developer handoff.
Direct contribution
Planning structure, flow assistance, early feature organization, interactive prototypes, UI contribution, and component-state documentation for handoff.
Collaboration
Three-person design team, with input from product, leadership, technical stakeholders, and developers.
Key design decisions
Four decisions shaped the final direction
The redesign focused on the moments where players needed clarity most: taking action, finding tournament details, following matches, and interpreting rankings.
01
State-aware tournament actions
We treated the CTA area as a state-aware component, pairing tournament condition with the action available to the player.
State-aware actions
State-aware actions pair tournament condition with the action available to the player.
Feature behavior example
Source-backed Arium tournament interface.
02
Accessible tournament details
Rules, rewards, schedules, and other key details were brought closer to the core tournament flow.
Accessible tournament details
Feature behavior example
Rules, rewards, and schedules are grouped closer to the tournament flow.
Source-backed Arium tournament interface.
03
Match context where players already looked
Results and schedule rows were designed to include match summaries and direct access to available streams.
Match context and stream access
Feature behavior example
Results and schedule rows include match summaries and direct stream access.
Source-backed Arium tournament interface.
04
Adaptable rankings with more player context
The ranking area was reorganized to support different tournament types and show more player information.
Adaptable ranking display
The ranking section differentiates tournament types and adds more player context.
Feature behavior example
Source-backed Arium tournament interface.
Final direction
One connected tournament experience
Across desktop and mobile, the final direction connected tournament action, essential details, match progress, and rankings while keeping conditional behavior explicit for implementation.
01
Discover
02
Review details
03
Join / status
04
Follow schedule
05
Open match
06
Interpret ranking
Final desktop and mobile tournament direction, captured from the original Arium case study.
Design output and learning
A clear design outcome, without overstating impact
Because tournament-specific post-launch metrics were not isolated, broader Arium growth figures are not attributed to this redesign.
Design output
The final direction connected tournament action, essential details, match context, and rankings. Component documentation clarified intended behavior for implementation.
Evidence limit
The project record does not isolate a tournament-specific post-launch metric, so broader Arium growth figures are excluded from this case study.
Learning
State-heavy features need explicit behavior, information timed to the right moment, and a shared model that design and engineering can use.
Next validation step
Validate with external players and tournament-specific measures
With more time, I would measure registration completion, repeat participation, schedule usage, and ranking comprehension.