PortfolioDP.

Live multiplayer strategy-trivia product

Knowledge starts the battle.
The map remembers it.

A live bilingual multiplayer game that combines trivia with territory control, estimation, voting, conquest, and social tension.

Open live product Public product
Live buildquizempire.fun
Quiz Empire live mobile conquest map
Quiz Empire mobile lobby with three players
Playable nowThree players turn knowledge into territory.

Interactive round anatomy

A quiz question is only one move.

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.

Role
Product creator & builder
Duration
Live and evolving
Milestone
Public product
01 / 05
Quiz Empire estimation result on mobile
Estimate · Live mobile state
Current phase · Estimate

Earn the first decision

Estimation questions rank players before territorial choices begin.

Live conquest state26 territories
Quiz Empire live map with three player territories
DanielBot 775Bot 323

The product system

Strategy creates interaction between answers.

01

Strategy can add tension, but each phase must be understood faster than it is explained.

02

Bot fallback and reconnection are part of the product promise in a real-time game.

03

Audio and motion clarify state only when the underlying rules are already legible.

Real-time game engine

The invisible product work keeps the match trustworthy.

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.

Player surfaceReact · Vite · PWALandscape interactionAudio and motion
Socket.IO looptimers · heartbeat · state
Match authorityExpress serverRooms and botsReconnect and AFK

Public validation · first-day snapshot

The launch produced signal, not just traffic.

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.

New visitors · launch day60All recorded as new in the captured snapshot
Page loads · launch day73Tracked first-party page loads
Reddit-attributed27Page loads across Reddit referral sources
Distribution experiment

One product. Two audiences. Three questions.

The launch posts deliberately asked whether the goal was understandable, whether the map created real strategy, and what would earn a second match.

Direct51
Reddit27
Other2

What players made visible

Feedback became a decision queue.

01Fix first

Stability and bot credibility

A Chrome freeze during the first territory capture, slow bot selection, and unrealistic numeric estimates are direct trust issues.

  • First-capture flow
  • Bot pacing
  • Estimate calibration
02Build retention

Progress must outlive one match

Players asked for profile progression, achievements, recurring events, and a question pool that continues to expand.

  • Profile progress
  • Achievements
  • Dynamic question pool
03Expand carefully

More formats, after the core is stable

Audio questions, a Europe-scale map, and configurable six-to-eight-player rooms emerged as credible expansion directions.

  • Audio questions
  • Larger maps
  • Variable player count

Interpretation note: these figures document early reach and qualitative learning. They do not yet demonstrate retention, product-market fit, or sustained adoption.

Product delivered
  • Released a working end-to-end multiplayer product with a 26-region map.
  • Reached 60 new visitors and 73 tracked page loads in the captured first-day launch snapshot.
  • Recorded 27 Reddit-attributed page loads in the captured launch traffic-source view.
  • Converted public feedback into a prioritised backlog spanning stability, replay, content variety, and larger game formats.
Next proof: live usage
Question 01

Fix the reported Chrome freeze during first territory capture and refine bot pacing and numeric estimates.

Question 02

Test repeat-play drivers: profile progression, achievements, a growing question pool, and recurring events.

Question 03

Explore audio questions and larger maps or configurable player counts after the core flow is stable.

Question 04

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.

Continue exploring
Next case study

S.W.I.T.C.H. User Management

Start a conversation

Let's find what's
worth building.

I am open to conversations about complex product ownership, business analysis, supplier evaluation, and delivery work that needs a steady bridge between business and engineering.