Boo

I design mobile-first casino interfaces — the colour systems, typographic hierarchies, interaction patterns, and microcopy decisions that determine whether a Kiwi player feels immediately at home the moment they open Boo on their phone, or whether something feels slightly off in a way they cannot quite name. That nameless friction is a design failure, and it almost always traces back to one of three causes: the visual system was not built for dark environments (most casino play happens in low-light conditions — on the couch after the kids are in bed, in a bach on a rainy afternoon), the navigation was designed for a desktop screen and then shrunk rather than rebuilt for thumb interaction, or the language on the interface was written for a global audience and never localised for the way Kiwis actually talk. At Boo, the UX is built mobile-first from a blank canvas, not ported from a desktop template. The colour system, touch targets, microcopy, and information hierarchy were all designed for a player holding a phone in portrait orientation, playing one-handed, on a Spark or One NZ network. This page explains the design thinking behind that approach, choice, mate.

How is Boo's dark mode colour system built — and why does it matter for mobile casino play?

The choice to build Boo's interface in dark mode first is not aesthetic preference — it is a decision grounded in how, where, and when Kiwi players actually use the platform. The majority of mobile casino sessions happen in low-light or ambient-light conditions, and a white or light-surfaced interface in those contexts creates eye strain within minutes, increases battery drain on OLED screens significantly, and introduces an uncomfortable brightness contrast that makes a player less likely to extend their session. A well-designed dark mode casino interface is not simply a white interface with colours inverted — it is a purpose-built colour system with a specific luminosity hierarchy. Background sits at roughly 8–12% luminosity. Surface cards (game tiles, panels, modals) sit at 14–18%. Interactive elements and primary CTAs sit at their full brand hue. Text hierarchy uses four levels: primary (near-white at 90%+ luminosity), secondary (around 65%), tertiary (around 45%), and disabled (around 30%). Getting this hierarchy wrong — using text that is too close in luminosity to its background — is the single most common accessibility failure in mobile casino interfaces and the one most likely to affect Kiwi players with mild vision variations. The colour chart below maps Boo's complete dark mode system and the UX role of every colour in the hierarchy. See the casino glossary for any UX terms.

The Warning / RG Nudge colour row is the one most operators get wrong, and it is the one I spend the most time defending in design reviews. The temptation is to make responsible gambling alerts visually assertive — bright orange, full-screen takeovers, high-contrast alarm-style messaging. The research on this is clear: high-anxiety visual design around gambling limits produces avoidance behaviour, not engagement. Players dismiss intrusive alerts faster than they read them. The design principle I apply at Boo is that RG nudges should feel like a helpful friend tapping you on the shoulder, not a warning siren. The amber-on-dark tone shown in the chart is warm and visible without being alarming. Session timer displays use this colour so the information is present at all times without commanding attention away from the game itself. When a limit is approaching, the nudge grows slightly in size and adds a brief vibration — it does not take over the screen.

The success green and win gold colours serve different purposes despite both communicating positive outcomes. Success green is used for transactional confirmations — your POLi deposit went through, your KYC check passed, your withdrawal is processing. It is a calm, trustworthy colour associated with completion and safety, and it needs to feel reassuring rather than exciting. Win gold, by contrast, is the colour of celebration — it appears on big win animations, jackpot reveals, and bonus triggers. The distinction matters because mixing these signals creates confusion: if the same colour means both "your deposit worked" and "you just won a jackpot", neither message lands with appropriate weight. Getting the emotional register of colour right is the detail that separates a polished interface from one that feels generically built.

What are the seven core UX design principles that guide every design decision at Boo — and how does the platform score on each?

Every design decision on Boo's mobile interface is evaluated against seven core principles that I developed specifically for the NZ market. These are not generic UX principles borrowed from a textbook — they are specifically calibrated to the realities of Kiwi mobile casino play: the network conditions (Spark, One NZ, and 2degrees all have different characteristics in Auckland versus the regions), the device mix (a higher proportion of older Android devices than many European markets), the cultural context (direct, unpretentious communication over polished marketing language), and the specific regulatory expectations that the DIA framework will introduce for licensed platforms. Speed is the first principle and the non-negotiable baseline — a lobby that takes more than two seconds to reach an interactive state on a 4G connection loses players before they have evaluated anything else. Clarity is the second, which encompasses visual hierarchy, label precision, and the elimination of ambiguity from every clickable element. The remaining five principles — Trust, Localisation, Accessibility, RG-First, and Discovery — each require deliberate design investment to execute properly rather than lip service in a design brief. The honeycomb diagram below shows the full seven-principle framework and Boo's current score on each.

The Accessibility score of 82% is the improvement area I am actively working through in the current design sprint. WCAG 2.1 AA compliance is the target, and the remaining gap comes from two specific issues: contrast ratios on tertiary text in a small number of game tile metadata labels (the text showing RTP and provider name below each pokie thumbnail), and reduced-motion support for the win celebration animations, which currently cannot be disabled by players who have system-level reduced-motion preferences enabled on their device. Both are tractable problems with well-understood solutions — they are in the backlog rather than the "too hard" category, and they will be resolved before the incoming DIA licensing framework requires full accessibility compliance for licensed NZ operators.

The Discovery score of 84% reflects a genuinely difficult design challenge: a library of several thousand pokies needs to be surfaced in a way that helps a Kiwi player find the game they want in under three taps, without the lobby feeling like a wall of thumbnails. The solution we have implemented at Boo is three-tier curated discovery: a "Top Kiwi Pokies" row showing the eight titles with highest NZ session volume in the last seven days, a "Live Now (NZ time)" row for live dealer tables currently running in NZST, and a personalised "For You" row that updates based on each player's own game history. A predictive search that suggests results after two characters handles everything else. The three-row structure means a player who opens the app without a specific game in mind has three meaningful and locally-relevant discovery paths before they even reach the main game library.

Which specific UX decisions produce the highest measurable impact on NZ player conversion and session depth?

Design decisions are not all equal in their measurable impact. Some changes are cosmetically significant but produce minimal conversion or retention movement. Others are modest in visual scope but produce outsized improvements in the metrics that matter: registration completion rate, first-deposit completion rate, session length, and seven-day return rate. A/B testing across comparable platforms serving NZ players has produced a reasonably consistent body of evidence on which UX decisions move the needle most. The seven highest-impact interventions for the NZ market specifically are: displaying POLi as the primary deposit option (not buried in a payment method dropdown), using "pokies" everywhere rather than "slots" or "games" in navigation labels, implementing genuine dark mode rather than grey-on-black, placing the account balance in the persistent header so it is always visible without a tap, adding a one-tap deposit shortcut on the bottom nav, showing live dealer game previews with real-time player counts, and positioning deposit limits as a completion step in registration rather than a settings-buried option. The lollipop chart below shows the measured relative impact of each of these seven decisions across NZ-facing cohort data.

The POLi result is the one that consistently surprises operators who have not specifically researched the NZ market. In most global markets, displaying a bank transfer option prominently at the deposit step reduces conversion because bank transfers feel slow and friction-heavy compared to card payments. In New Zealand, POLi is the opposite experience — Kiwis recognise it instantly as the same system used for paying utilities, buying event tickets, and managing everyday financial transactions. It connects directly to their ANZ, ASB, BNZ, Kiwibank, or Westpac account and completes in seconds. When Boo promotes POLi as the primary option rather than burying it as one of eight payment logos in a grid, first-deposit completion rate improves substantially — because the player sees a familiar, trusted method at the top of the list rather than having to scroll to find it. This is a localisation decision that compounds across every session: the first deposit experience sets the emotional tone for the entire relationship with the platform.

The deposit limit at registration result — impact score 65, the lowest on the chart but still significant — is important to understand in context. A UX designer who was optimising purely for conversion would remove this friction point entirely: requiring a player to set a deposit limit before they can complete registration adds a step, introduces a decision, and will cause some percentage of players to pause or drop off. The reason it is in the design is precisely because it slightly reduces conversion in exchange for a larger benefit: players who set limits at registration experience significantly lower rates of disputed withdrawals, self-exclusion due to problem gambling, and chargeback requests. The design intent is to make responsible gambling the path of least resistance, not an opt-in afterthought. Under the incoming DIA licensing framework, this is not optional — operators will be required to offer limit-setting at registration. At Boo, it is already there. 18+ · Gambling Helpline 0800 654 655 · Register at Boo and experience a mobile casino built for Kiwis, by designers who understand what that means.