Fazi dashboard
UI/UX design
/
2024
Feature design, information architecture, user flows
A number on a screen above a slot machine isn’t really text. It has to read as a payout from across a room, in whatever currency the floor uses, appearing at a fixed moment inside a video loop that runs all day. Before this, getting a new one up there meant producing the file somewhere else, exporting it, and carrying it to the machines.
Fazi iDisplay is the CMS behind those screens – the win amount that appears when a machine pays out, and the jackpot total running above it. I designed the editor where both get built, and the system around it.
Each win or jackpot is build and set up in the editor, which was the heart of the project.
A jackpot total is content, so it queues in a playlist beside a video. Once that was settled, the rest of the CMS followed from it: wins and jackpots are two of six content types on one system, handled like the media around them – a playlist deciding what plays where and for how long, a library holding the images and video, a fonts panel behind all of it.
Wins – every win configured for one screen, as cards or as a list, each with its thumbnail, a short description, and when it was last edited.
The editor is where the work is. I put every setting for a win on one screen instead of spreading it across a flow: the amount and the machine number as separate boxes, each with its own position, size and priority; the font; the thousands and decimal separators; where the currency symbol goes; solid fill or gradient. Nobody configures a payout display once and walks away, so nothing is buried a step deeper than anything else.
The Win editor – position, size, level, font, currency format and animation timing, every control for one win on a single screen.
Getting the number on and off the screen is its own problem. Each box carries two independent animations timed against the same clip – a fade a few seconds into the loop, a fade out before the next one begins. So I gave each animation’s timing two controls – a numeric field and a timeline slider, Get and Set syncing them, either one able to drive the other, because someone judging a fade wants to drag it and someone repeating a known value wants to type it.
The numbers get their own type as well. Alongside the standard faces, the fonts panel carries embossed gold and silver number sets drawn for these displays – a jackpot total on a casino screen is closer to a graphic than to a line of text.
Every install is a different floor, with different screens above different machines. So I made the resolution a typed field per client rather than a list, which would be wrong the first time a casino mounts a panel nobody anticipated. Name, logo, resolution, set once per installation.
Settings – the one screen that changes per client: name, note, logo, and a screen resolution entered per installation rather than picked from a fixed list.
Six content types, one editor pattern, one set of foundations under all of it. What the casino gets is a number above a machine. What had to be designed is everything that puts it there.