
Earn the first decision
Estimation questions rank players before territorial choices begin.
Live multiplayer strategy-trivia product
A live bilingual multiplayer game that combines trivia with territory control, estimation, voting, conquest, and social tension.


Interactive round anatomy
Most quiz experiences test recall but create limited interaction between players. The hypothesis is that territory and conquest can make knowledge feel more social, tactical, and replayable.

Estimation questions rank players before territorial choices begin.

The product system
Strategy can add tension, but each phase must be understood faster than it is explained.
Bot fallback and reconnection are part of the product promise in a real-time game.
Audio and motion clarify state only when the underlying rules are already legible.
Real-time game engine
The client uses React, TypeScript, Vite, and Sass; Express and Socket.IO manage the real-time server loop. Questions are loaded in Hungarian and English from a maintained Google Sheets source, while the PWA is optimized for fullscreen landscape play.
Public validation · first-day snapshot
Two public posts—one Hungarian and one English—asked focused questions about comprehension, strategic depth, and the reason to return. The response converted those hypotheses into a concrete backlog.
The launch posts deliberately asked whether the goal was understandable, whether the map created real strategy, and what would earn a second match.
What players made visible
A Chrome freeze during the first territory capture, slow bot selection, and unrealistic numeric estimates are direct trust issues.
Players asked for profile progression, achievements, recurring events, and a question pool that continues to expand.
Audio questions, a Europe-scale map, and configurable six-to-eight-player rooms emerged as credible expansion directions.
Interpretation note: these figures document early reach and qualitative learning. They do not yet demonstrate retention, product-market fit, or sustained adoption.
Fix the reported Chrome freeze during first territory capture and refine bot pacing and numeric estimates.
Test repeat-play drivers: profile progression, achievements, a growing question pool, and recurring events.
Explore audio questions and larger maps or configurable player counts after the core flow is stable.
Add automated game-engine and reconnect coverage as usage grows.
A public launch turned assumptions into specific decisions: fix the first-capture failure, tune bot behaviour, and test progression, content variety, and larger formats as reasons to return.
Evidence note · Launch figures are a captured first-day analytics snapshot: 60 new visitors and 73 tracked page loads that day. These are early reach signals, not retention or adoption claims.
Start a conversation