Creative case study
PixiJS Slot Game Engine
A high-performance, configurable slot machine engine built with PixiJS v8 — from spinning reels and win-line evaluation to bonus rounds and sound management.
Creative case study
A high-performance, configurable slot machine engine built with PixiJS v8 — from spinning reels and win-line evaluation to bonus rounds and sound management.
Client
iGaming Studio
Role
Lead Game Developer
Year
2026
Discipline
HTML5 Game Engine
Reduced time-to-ship for new slot themes from 6 weeks to under 10 days by building a fully data-driven engine.
The hero image is loaded from the MDX coverImage field. Replace the demo URL with your own gameplay capture, PixiJS canvas screenshot, or rendered artwork.
50+ types
Reel symbols
60 FPS
FPS target
< 1 day
Theme swap time
The client needed a reusable slot engine that could ship multiple game themes on a tight schedule. The key constraint was that artists and designers had to be able to swap out a theme — symbols, background, paytable, colors, sounds — without touching any engine code.
The engine is split into two layers: the core engine and the theme manifest.
The core engine handles all game logic: reel spinning physics, symbol evaluation, win-line calculation, RTP simulation, and bonus round state machines.
The theme manifest is a single JSON file that declares symbol definitions, reel strips, paytable multipliers, asset paths, and sound cues. Swapping a theme is literally swapping one JSON file and an asset bundle.
Standard slot reels feel cheap when they just teleport symbols into place. I implemented a physics-based spin using GSAP:
This gives each spin a satisfying, weighty feel without requiring complex physics simulation.
Win celebrations are handled by a dedicated Win Presenter that sequences:
PIXI.ParticleContainer.Each stage is orchestrated by a SequenceRunner class that manages async chain logic cleanly.
PIXI.TilingSprite for parallax without Canvas API overhead.The engine powers 4 live slot titles. Each new theme was delivered in under 10 days, against a previous industry baseline of 5–6 weeks.
More Case Studies
A technical deep-dive into how production iGaming studios store, version, and serve complex game math configurations across operators, jurisdictions, and variants.
A complete blueprint of an enterprise iGaming backend system: from the Seven-Layer Model and 48ms game transaction loops to GLI compliance and scaling pipelines.

An educational compiler project translating academic Computer Science theory into a working plain-English general-purpose compiler that compiles directly to zero-overhead x64 assembly.