One game, three doors - what we think about when a classic mobile strategy lives in a browser tab and a Telegram chat

Voyna Carstv — Wed, 28 Oct 2026 02:16:21 +0000

A note from the team behind Clash of Kings: Война царств, the Russian-language edition of the classic strategy Clash of Kings. You can open it in a browser at clashofkingsgame.com/play or in Telegram via @ClashOfKingsGameBot.

Most people remember Clash of Kings as a phone game: build a city, train troops, join a clan, march across a shared map. When we started bringing the Russian edition, «Война царств», to players again, we decided it should not live behind a single app-store button. Today the same world opens through three doors: a desktop browser, a mobile browser, and Telegram. This post is not a tutorial and it is not a benchmark. It is a list of the questions that turned out to matter most when one persistent strategy world has to feel the same no matter which door a player walks through.

1. The world is the product, the client is just a window

In a city-builder with a shared map, the thing a player cares about is not the client. It is their city, their clan, their place on the map, and the march that is going to land in forty minutes whether their laptop is open or not. That sounds obvious, but it changes priorities.

The first rule we keep repeating internally: nothing important should depend on which client you used last. A player who builds a barracks from a work computer and then checks the result from Telegram on the bus should see one consistent state. That pushes every bit of game logic that matters - timers, resources, combat results - to the server, and keeps the client honest and thin. The client draws the world and sends intentions; the server decides what actually happened.

2. "No install" is a feature only if the first minute is good

The strongest argument for a browser and messenger version is that there is nothing to install. The weakest point is the same: if the first minute is slow or confusing, closing a tab costs the player nothing.

So we look at the first session as its own product:

What does the player see before anything heavy loads? A welcome screen and server choice should appear fast, and the heavier city and map assets can follow.
Is the first choice obvious? Today the Russian edition runs a dedicated Russia server, so the server list is short on purpose. Fewer decisions before you see your city is better.
Can a returning veteran recognise the game in seconds? People who played the original years ago come back with expectations about how the city looks, where the barracks are, and what a hero screen feels like. Familiar layout is part of the onboarding for them.

3. Telegram is not "a smaller browser"

Opening the game from a Telegram bot looks like opening a web page, but the context is very different. The player came from a chat. They may have thirty seconds, one hand on the phone, and a notification from a friend waiting.

That shapes what the Telegram door should be good at:

Short check-ins. Collect resources, start an upgrade, look at the clan chat, send a march. The game has to make those quick actions reachable without hunting through menus.
Coming back from a link. In a messenger, a lot of traffic arrives from someone sharing a link. A player tapping a friend's link should land in the game, not on a wall of instructions.
Respecting the chat. A bot that spams is a bot that gets muted. Anything the bot says should be something the player would actually want to know.

And the most important part: the Telegram door and the browser door lead to the same world and the same account progress, not to two separate games that happen to share art.

4. Big battles are a coordination problem first

The feature our team talks about most is clan warfare at scale - battles with a thousand players on each side. From a player's perspective, the interesting part of a battle that size is not clicking faster. It is coordination: who scouts, who reinforces, who holds a position, which alliance agreed to stay out.

For the people building the game, that means the social tools are as important as the combat formulas. Clan chat, rally points, shared targets, and clear map information decide whether a thousand people act like an army or like a crowd. When the same clan has members on desktop, mobile browser, and Telegram at the same time, the information they see has to match, or the coordination falls apart.

5. Localisation is more than translating strings

«Война царств» is not just Clash of Kings with Russian text. The edition is themed around Old Rus: princes and fiefs, druzhina, bogatyrs, and heroes such as Evpatiy Kolovrat. Doing that well is a design job, not a translation job:

Names have to read naturally to a Russian-speaking player and still fit the original mechanics.
Interface labels have to stay short enough to fit on a phone screen, which is harder in Russian than in English.
The tone of events and quests has to feel like a chronicle, not like a machine translation of a marketing banner.

6. Returning players are a different audience from new players

The original game built a very large audience over the years - by our own count, more than fifty million players - and part of that audience is now drifting back. Our team's view is that returning players and new players need different things:

Veterans want the core loop they remember, the scale of the map, and serious clan politics. They notice immediately if something familiar has been simplified away.
Newcomers who never saw the original need a gentle first hour: what to build first, why the residence level matters, when to join a clan.

Serving both in one world means keeping the depth for the first group while making sure the second group is not lost in the first ten minutes.

7. What we would tell anyone shipping a persistent game to the web and to messengers

Keep authority on the server; treat every client as a window, not as the source of truth.
Measure the first minute separately from everything else, because that is where "no install" wins or loses.
Design the messenger experience for short check-ins and shared links, not for marathon sessions.
If your game is social, the coordination tools are core gameplay.
Localise the experience, not just the text.

Try it and tell us what breaks

We would genuinely like feedback from developers: how the game behaves on your hardware and browser, how the Telegram version feels on your phone, and what confused you in the first session.

Play in the browser: clashofkingsgame.com/play
Play in Telegram: @ClashOfKingsGameBot
Project site: clashofkingsgame.com

Thanks for reading - and if you played the original years ago, welcome back.

DEV Community: Voyna Carstv