Skip to content

Product engineering

Talk to us Discuss a Project
Talk to us Discuss a Project

Case study · Real-time gaming

Vokabul8

Four wagering formats built on one shared clock, where the hard engineering problem was making every player in the world see the same second.

Delivered

Engagement
Full product design and engineering
Platforms
Web application and dashboard
Role
UI/UX design and full engineering
Stage
Beta Verify before publishing
The Vokabul8 platform: the live "What’s the word?" round with its countdown and letter entry, the four game formats with their odds, and the social feed running alongside.
Industry
Gaming
Users
Adult players
Formats
Four game types
Platforms
Web
Role
Design and engineering
Status
Delivered

01The business situation

A shared game needs a shared second.

The platform runs many short rounds through the day, each open to everyone at once. Players wager on guessing letters, counts and positions across four formats, and their stake is held in a connected wallet. All of that rests on one assumption: that every player, wherever they are, is looking at the same countdown. If the clock drifts, the fairness of the whole product goes with it.

Core challenge

Keep a single authoritative clock across every connected player, while four differently-shaped games resolve against the same daily round schedule.

Before

Turn-based games with no shared moment

  • Asynchronous Play
  • Local Timers
  • Isolated Sessions
  • No Shared Round

After

One synchronised round everyone plays together

  • Player
  • Live Round
  • Wallet
  • Social Feed

Vokabul8 Platform

02The system at a glance

One clock. Four connected experiences.

  • Admin Dashboard Questions, rounds and operations
  • Player Experience Live rounds and wagers
  • Odds & Settlement Stakes, results and winnings
  • Social Layer Feed, posts and chat
Core PlatformSocket-synchronised round engine
  • Round Scheduling
  • Live Timer Sync
  • Four Game Formats
  • Wallet Integration
  • Private Rooms
  • Bulk Question Import

03Workflow 01

Four ways to wager on the same day’s words.

One format runs live and public. Two more let players wager on rounds not yet revealed. The fourth turns the same mechanic into a private room. Each carries its own odds against the same underlying schedule.

Image placeholder The four game formats: the live word round with its countdown and letter entry, the two prediction formats with their odds and selection groups, and a private room lobby. assets/portfolio/vokabul8/workflow-games.png · 16 / 11
  • One live, three predictiveThe active round is public, while other formats let players wager on rounds still to come.
  • Odds per formatEach game type carries its own odds, so risk differs meaningfully between them.
  • Private roomsThe same mechanic can be run as a closed game among invited players over a set number of rounds.

04Workflow 02

The clock is the product.

A round opens, everyone sees the same countdown, wagers close together, and the result settles against the wallet. Getting that sequence identical for every connected player is where most of the engineering went.

  1. 1Round opens

    Image placeholder A live round opening: the partially revealed word, the synchronised countdown and the current stake pool. assets/portfolio/vokabul8/step-round.png · 1 / 2.04

  2. 2Wager placed

    Image placeholder Placing a wager: the wallet balance, the stake selector and the odds for the chosen answer. assets/portfolio/vokabul8/step-wager.png · 1 / 2.04

  3. 3Settled to wallet

    Image placeholder Round settlement: the revealed answer, the outcome for this player and the resulting wallet balance. assets/portfolio/vokabul8/step-settle.png · 1 / 2.04

05Workflow 03

Operations is a content pipeline.

A platform running many rounds a day consumes questions faster than anyone can type them. The admin dashboard is built around bulk import as much as around monitoring.

  • Bulk question importAdministrators populate the question bank in batches rather than one at a time.
  • Rounds scheduled aheadThe day’s sequence is prepared in advance so the live engine simply runs it.
  • A social layer, not a bolt-onA feed and chat sit alongside play, giving the platform a reason to be open between rounds.
Image placeholder Admin dashboard: the question bank with its bulk import tool, the day’s round schedule, and operational monitoring of active games and stakes. assets/portfolio/vokabul8/admin-console.png · 16 / 10
Image placeholder The social feed: player posts, reactions and the chat panel running alongside gameplay. assets/portfolio/vokabul8/social-feed.png · 1 / 2.04

06Engineering behind the product

The system behind a synchronised round.

Two problems dominated: keeping one clock true across the world, and settling outcomes correctly against real balances.

  • Socket-based timer synchronisation

    A persistent connection keeps every player on the same countdown, which is what makes simultaneous play fair.

  • Round scheduling engine

    The day is divided into a fixed sequence of short rounds that the live engine executes on schedule.

  • Four format resolutions

    Each game type has its own answer model and odds, resolving against a shared round record.

  • Custom selection algorithm

    Question selection and outcome processing run through a purpose-built algorithm rather than simple random draw.

  • Wallet integration

    Stakes and winnings settle against VeightCoin, the connected virtual-currency wallet from the VeightPay platform.

  • Private room mechanics

    A room has a creator, an invited membership and a fixed round count, with joint winners handled explicitly.

  • Bulk content tooling

    Administrators import questions in bulk, which is a hard requirement at this round frequency.

  • Social feed and chat

    Posting, reactions and messaging run alongside gameplay in the same application.

07Technical architecture

Under the hood

A Laravel platform with sockets holding a single synchronised clock across every connected player.

Backend

  • Laravel
  • PHP
  • WebSockets

Frontend

  • Vue.js
  • Tailwind CSS

Data

  • MySQL

Cloud & services

  • DigitalOcean
  • OneSignal (push)
  • Mailgun (email)

08Delivery journey

How the platform was delivered.

  1. Product definition

    Full product scope, not an MVP

  2. UX

    Design player and admin surfaces

  3. Round engine

    Build scheduling and synchronisation

  4. Game formats

    Implement each format and its odds

  5. Wallet integration

    Connect stakes and settlement

  6. Beta release

    Ship with the wallet connected

  7. Support

    Iterate on player feedback

Timeline and scope changed during the engagement before release. This is a wagering product; nothing here asserts licensing or regulatory status, and no player or stake figures are published. Verify before publishing

09Where it stands today

What the platform brings together

  • Four wagering formats on one round schedule
  • A countdown synchronised across every connected player
  • Stakes and winnings settled against a connected wallet
  • Private rooms with fixed rounds and joint winners
  • Bulk question import for daily operations
  • A social feed and chat alongside gameplay

Related systems

VeightPay

Fintech · Wallet & Payments · Web

A wallet-based payments platform for cross-border transfers without a card or domiciliary account, with an agent marketplace and merchant APIs.

View case study , VeightPay

Polar Attack

Gaming · Reflex Game · Android

A tilt-controlled reflex game built on an open-source Java engine, with three difficulty levels and a published Play Store release.

View project overview , Polar Attack

Real-time is a promise you have to keep every second.

We build the synchronisation first, because everything else depends on it being true.

Discuss your system