Apex Legends
Apex Legends
Apex Legends
Designing a new competitive experience: Apex Rumble
Designing a new competitive experience: Apex Rumble
Designing a new competitive experience: Apex Rumble
Apex Rumble introduced a new asynchronous competitive experience within Apex Legends, designed to engage competitive players during seasonal downtime while being flexible enough to be reused across the game.
The experience brought together participation requirements, scoring, progression, tiers, leaderboards, match history and rewards within a single connected flow.
My UX work spanned across research, flows, wireframes, information architecture, interactive prototyping, usability testing and iteration.
Apex Rumble introduced a new asynchronous competitive experience within Apex Legends, designed to engage competitive players during seasonal downtime while being flexible enough to be reused across the game.
The experience brought together participation requirements, scoring, progression, tiers, leaderboards, match history and rewards within a single connected flow.
My UX work spanned across research, flows, wireframes, information architecture, interactive prototyping, usability testing and iteration.
Apex Rumble introduced a new asynchronous competitive experience within Apex Legends, designed to engage competitive players during seasonal downtime while being flexible enough to be reused across the game.
The experience brought together participation requirements, scoring, progression, tiers, leaderboards, match history and rewards within a single connected flow.
My UX work spanned across research, flows, wireframes, information architecture, interactive prototyping, usability testing and iteration.

The Apex Legends Rumble User Interface Menu.
The Apex Legends Rumble User Interface Menu.
Designing the experience
Designing the experience
Designing the experience
I approached Rumble as an end-to-end experience, mapping the wider player journey to identify what information players needed at different points while ensuring the new feature remained consistent with Apex's existing UX conventions.
Throughout development, the feature evolved substantially, culminating in a significant change in direction late in production. I revised the existing experience, and built an interactive prototype for usability testing as a low-cost way to validate this new direction before committing further implementation time.
I approached Rumble as an end-to-end experience, mapping the wider player journey to identify what information players needed at different points while ensuring the new feature remained consistent with Apex's existing UX conventions.
Throughout development, the feature evolved substantially, culminating in a significant change in direction late in production. I revised the existing experience, and built an interactive prototype for usability testing as a low-cost way to validate this new direction before committing further implementation time.
I approached Rumble as an end-to-end experience, mapping the wider player journey to identify what information players needed at different points while ensuring the new feature remained consistent with Apex's existing UX conventions.
Throughout development, the feature evolved substantially, culminating in a significant change in direction late in production. I revised the existing experience, and built an interactive prototype for usability testing as a low-cost way to validate this new direction before committing further implementation time.
My Approach
My Approach
My Approach
Gathered Requirements · Defined the IA & Key States · Connected Full Flow
Prototyped and Validated · Iterated
Gathered Requirements · UX Audit · Restructured IA · Mapped Key Journeys · Wireframes · Supported Implementation
Gathered Requirements · UX Audit · Restructured IA
Mapped Key Journeys · Wireframes · Supported Implementation
Experience Validation
Experience Validation
Experience Validation
I built an interactive Figma prototype specifically for usability testing, focusing the study on whether players could understand and successfully navigate the experience rather than evaluating individual screens in isolation.
I wanted to discover if players could find and make sense of the new experience, successfully enter and participate, interpret its terminology, understand progression and rewards, and move confidently between different areas.
Testing largely validated the core flows while identifying opportunities to improve reward and progression clarity, terminology and navigation. Players generally understood the experience more clearly through repeated exposure, while some existing Apex terminology created unintended expectations due to its overlap with other systems.
I built an interactive Figma prototype specifically for usability testing, focusing the study on whether players could understand and successfully navigate the experience rather than evaluating individual screens in isolation.
I wanted to discover if players could find and make sense of the new experience, successfully enter and participate, interpret its terminology, understand progression and rewards, and move confidently between different areas.
Testing largely validated the core flows while identifying opportunities to improve reward and progression clarity, terminology and navigation. Players generally understood the experience more clearly through repeated exposure, while some existing Apex terminology created unintended expectations due to its overlap with other systems.
I built an interactive Figma prototype specifically for usability testing, focusing the study on whether players could understand and successfully navigate the experience rather than evaluating individual screens in isolation.
I wanted to discover if players could find and make sense of the new experience, successfully enter and participate, interpret its terminology, understand progression and rewards, and move confidently between different areas.
Testing largely validated the core flows while identifying opportunities to improve reward and progression clarity, terminology and navigation. Players generally understood the experience more clearly through repeated exposure, while some existing Apex terminology created unintended expectations due to its overlap with other systems.

The About screen for Apex Rumble.
The About screen for Apex Rumble.
The About screen for Apex Rumble.
Looking back: the challenge of new experiences in a live service product
Looking back: the challenge of new experiences in a live service product
Looking back: the challenge of new experiences in a live service product
Working on Apex Rumble alongside colleagues at Respawn Entertainment and EA was a privilege and a valuable learning experience.
The project highlighted the challenges of introducing a new feature into an established product, balancing the need for something fresh and engaging while ensuring it feels intuitive, familiar and consistent with the existing player experience.
Looking back, I'd place greater emphasis on establishing a shared understanding of these goals and the constraints surrounding them, helping teams make more informed decisions and reduce unnecessary rework.
Usability testing proved particularly valuable. By testing early enough in development, we were able to identify issues with onboarding and make meaningful improvements before the feature was released.
Working on Apex Rumble alongside colleagues at Respawn Entertainment and EA was a privilege and a valuable learning experience.
The project highlighted the challenges of introducing a new feature into an established product, balancing the need for something fresh and engaging while ensuring it feels intuitive, familiar and consistent with the existing player experience.
Looking back, I'd place greater emphasis on establishing a shared understanding of these goals and the constraints surrounding them, helping teams make more informed decisions and reduce unnecessary rework.
Usability testing proved particularly valuable. By testing early enough in development, we were able to identify issues with onboarding and make meaningful improvements before the feature was released.
Working on Apex Rumble alongside colleagues at Respawn Entertainment and EA was a privilege and a valuable learning experience.
The project highlighted the challenges of introducing a new feature into an established product, balancing the need for something fresh and engaging while ensuring it feels intuitive, familiar and consistent with the existing player experience.
Looking back, I'd place greater emphasis on establishing a shared understanding of these goals and the constraints surrounding them, helping teams make more informed decisions and reduce unnecessary rework.
Usability testing proved particularly valuable. By testing early enough in development, we were able to identify issues with onboarding and make meaningful improvements before the feature was released.