Designing a LiveOps alerting system to reduce production incidents
Role
Product Designer
Duration
3 months
Team
Product Manager, CTO, 2 BE Engineers, 1 FE Engineer
Skills
Product Design
Product Strategy
Prototyping
Live mobile games rely on continuous updates after release.
At Tactile, updates are managed through an internal LiveOps Dashboard, where teams configure events, experiments, player targeting, and feature rollouts without shipping new app versions.
The flow looks simple, but it depends on multiple backend systems staying in sync. When something breaks, the impact often appears first in the live game.
Ideal flow
A creator configures a feature in the Dashboard, backend systems process it, and the result reaches players as expected.
The problem
Failures were detected by backend systems, but not surfaced in the LiveOps Dashboard. As a result, creators had no indication that a live feature was failing until players or support teams raised the issue.
Goal
Surface backend failures to LiveOps creators early so they can act before players are affected
Solution
Add password to keep reading.