Pasa Slots

A slot game lives or dies on feel, and feel is the hardest thing to retrofit.

The client had a working prototype in which the reels were animated first and the result was read off wherever they happened to stop. It looked fine until it did not: a dropped frame or a backgrounded tab changed the outcome, two players on the same spin could see different symbols, and a near-miss could not be designed deliberately because nothing knew in advance what the spin was going to be. Every new bonus feature made the timing more fragile.

The second problem was breadth. Each themed machine had been built as its own screen with its own copy of the paytable, spin loop and bonus logic, so adding a theme meant duplicating the game and adding a fifth place for a bug to hide. The brief was to make a new theme a content decision rather than an engineering project, and to keep the whole thing playable on a phone.

The engine is the product; the themes are content on top of it.

The client releases new machines on a regular cadence without engineering involvement in the game loop — reel strips, paytables and feature rules are authored against the typed definition and reviewed like content. Because outcome and presentation are separate, feature work such as a new bonus round is written once and appears correctly in every theme.

Responsible-play controls — session length, spend ceilings and reality-check prompts — sit in the same store as the wallet, so they cannot be bypassed by the interface and were straightforward to tighten when the client's policy changed. Our involvement ended at handover with the engine, theme authoring guide and test suite in the client's hands.

Have something that needs to ship?

Scope agreed in writing, architecture first, weekly increments you can review. Start with a 30-minute call or send the brief.