Gaming Systems is one platform for running a casino: seven products that cover everything from the player’s phone to the table and the cage, designed as one system.
- Client
- TRONIUS Gaming
- Services
- Product design
- design system
- brand
I designed the UX, the UI and the design system for all seven products, from a phone to a desktop, and built the brand from scratch: identity, marketing and video.
The platform
A casino runs on many jobs at once. Gaming Systems covers twelve of them on one platform: customers, machines, tables, online gaming, marketing, compliance, customer service, cage and finance, analytics, payments, self service and experience management.
So the work was never one screen. It was one language for all of them: the same parts, the same colours for the same meanings and the same way of moving money, whether on a desktop, a tablet or a phone.
At the table
A table is run from a tablet. Each seat is a session, and its card shows the player, the drop, the average bet and the time played. Updating one takes a tap or two.
Money is counted the same way wherever it moves: choose cash, chips, wallet or ticket, enter the amount on large keys, read the total and confirm. Fills, credits and transfers sit one tap from the table.
In the player’s hand
Players get the Portal, an app for their own phone. They activate it in the casino by scanning a code from a member of staff, and from then on see their two balances: real money, and freeplay earned as they play.
At a machine they scan its code and move funds across in one tap: a set amount, the whole wallet or a sum they choose. The app is dark where the rest of the platform is light, with the same purple and the same parts.
The process
Work is planned and tracked in Jira. Before I design, an AI tool gathers the information the task needs, and that makes everything after it quicker.
A screen I draw in Figma is read by Claude Code through Figma’s MCP server and built from it. A screen that starts in Claude Design is built by Claude first and then brought back into Figma. That is the whole circle: from the file to the code, and from the code back to the file.
Claude Code proposes a plan, and I approve it before it writes any code. Nothing is committed until I say so.
The model writes the first draft, and I decide what stays.
