Development retrospective
Chat, feedback, and learning from playtests
Adding secure community features and a feedback loop without losing sight of the game.
Feedback where the game lives
A bug report and suggestion system reduced the distance between noticing a problem and telling us about it. Reports include enough run context to investigate while the interface stays out of the way during play.
Account chat
Chat and announcements gave signed-in players a shared space. That required retention rules, authentication checks, input handling, mobile layout work, and clear loading states. Community features are product features and need the same care as combat.
Analytics with a question
Playtest tracking was added to answer specific design questions: where runs end, which options are selected, and where progression stalls. Collecting events without a decision attached only creates noise.
Closing the loop
Reports are useful when they lead to visible changes. Revive behavior, shop feedback, avatar layout, and late-stage progression all benefited from direct player observations.