Online game tools · my own product

Calamity

Analytics, messages, content and updates for a live game.

The task

Where we started.

Running an online game needs operational data, player communication, up-to-date content and reliable updates. I built tools that connect these processes.

My work

What I built.

Architecture, backend, frontend, data, launcher and ongoing support

Data for decisions

Custom event collection, dashboards and regular game reports. The relevant information is available in one place.

Communication and content

Tools for email, push, multilingual news and a public Wiki with its own editor.

Player products

A launcher delivers game updates. Armory lets players explore items and plan builds.

Project screens

The tools behind the game

From installing the game to working with data, content and communications.

Real product interfaces. Metrics, news and launcher states shown here are illustrative.

01

Install, update, play

The Windows and macOS launcher installs and updates the game. It also brings together news, notifications, chat and access to the Wiki and Armory.

Launcher: game launch, updates, news and player services.
Launcher: game launch, updates, news and player services.
View screen
02

Understand what happens in the game

Custom analytics collects game events: activity, player retention, progression, the economy and launcher actions. The team can explore them by period and topic.

Analytics dashboard: activity, retention and the game economy.
Analytics dashboard: activity, retention and the game economy.
View screen
03

News and live ops from one platform

The admin platform handles news and translations, push messages and email campaigns. Dedicated tools manage launcher releases and Wiki content.

Admin platform: the news editor, images and translation preparation.
Admin platform: the news editor, images and translation preparation.
View screen

Try the workflow

One task, a visible result.

Prepare a multilingual message

Review the prepared example in different languages and set its delivery options.

  1. Review the example
  2. Choose delivery
  3. Prepare the summary

Result: The message, languages and delivery options are collected in one campaign for review.

Prepared translations · local draft, no message is sent

Now

Published project

The public Wiki and Armory run alongside internal analytics, content and communication tools. This is my own product, which I develop and maintain.

A similar task

Who this could help.

Teams with a digital product, a community, regular updates and their own operational workflows.

Discuss your project
Technical details

FastAPI · React · DuckDB · Parquet · Celery · Tauri

  • Parquet/DuckDB analytics with rollups and regular reports.
  • News and messages in 14 languages.
  • Signed launcher updates; a public Wiki with a custom CMS.