01The problem
A broken process with a very long damage chain
Bad Dog Games had no reliable way to know where their machines were, whether they were active, or how they were performing. But the deeper problem was how that data was collected in the first place, and what happened when it wasn't.
The existing process required technicians with specific Samsung devices, special logins, and a proprietary app to scan machines on scheduled routes. Every single link in that chain was a failure point.
The full damage chain
- 01
Machine hits Day 7 without a technician scan
The RMS system requires a data collection scan every 7 days. When technicians missed their route, the machine locked itself. Routes could span hours of driving. One technician. Multiple locations. One broken app.
- 02
Machine locks. Venue owner can't resolve it.
The lockout screen displays a support number. Many owners didn't call. They just turned the machine off to stop paying electricity on a device earning nothing.
- 03
Machine sits dark until the next collection visit
If it locks on day 7 and the next scheduled visit is 30 days out, that machine earns zero revenue for 30 days. No alert. No escalation. No one knows.
- 04
Word spreads between venue owners
Bar and gaming venue owners talk. "The Bad Dog machines lock themselves and it takes forever to get someone out." Bad Dog was losing new placement deals before machines were ever installed, because of reputation damage from a data collection process.
- 05
Growth stalls
Not because of the product. Not because of the games. Because the infrastructure behind the machines had never been properly designed.
02The old system
Six codes. One broken app. Zero margin for error.
The old technician QR screen shows "QR Code 1 of 6." Because technician visits were infrequent, so much data accumulated between collections that it couldn't fit in a single code. The system split it across up to six separate QR codes that had to be scanned in sequence.
Each code was packed with an extremely dense matrix of pixels to hold all that data. That density made them highly sensitive to anything less than perfect conditions. A glare from overhead lighting. A slight angle. A reflection off the screen glass. Any interference with even one section of the code and the entire scan failed. Not just that code. The whole sequence had to restart.
Before
Technician QR / Up to 6 codes per machine
- Up to 6 codes per collection, scanned in sequence
- Extremely dense pixel matrix, highly sensitive to glare and reflection
- Required proprietary app that failed regularly
- One failed scan broke the entire sequence
- Samsung device + special login required
After
Player QR / One code, any phone
- One code per scan, displayed large for reliable reads
- Large size compensates for data density, resists glare
- Native phone camera, no app needed
- Works on any iPhone or Android
- "I would like free credits" incentive built into the screen
03The insight
The technician was never the right person for this job
Every machine already had a QR code on it. Every player already had a phone. The question wasn't how to make technicians more reliable. It was why a player couldn't close the loop instead.
The redesign didn't add new hardware or require a software install. It redirected an action that was already happening. Players were already standing next to these machines with phones in their hands. That existing behavior just needed a purpose.
04How it works
A five-step loop. No app. No technician.
The machine has no internet connection. The player's phone is the bridge. That's the entire architecture.
- 1
EGM Machine
QR displayed No internet
- 2
Player's Phone
Any phone No app
- 3
Bad Dog Server
Machine ID, GPS, timestamp logged
- 4
Code Generated
Returned to player's phone
- 5
Machine Validates
Feedback on machine, not on phone
- 1
QR code appears automatically on the machine
No scheduling, no dispatch, no specialized device. The code is there whenever a player is there.
zero staffing cost - 2
Any player scans it with any phone
iPhone or Android. No app download required. The native camera app is all they need.
universal access - 3
Phone opens the Bad Dog mobile site and transmits data
The machine itself has no internet connection. The player's phone is the connection point. The mobile site collects machine ID, GPS location for compliance tracking, and timestamp. Then sends it to Bad Dog's server.
compliance-ready location data - 4
The site generates a code and displays it on the phone
This is all the mobile site does. Scan. Send data. Return code. The phone's job is done in seconds.
intentionally minimal - 5
Player enters the code on the machine
Validation and all success/failure feedback happen on the machine. Once the code is entered, the player is done with their phone entirely.
feedback on machine, not phone
Screen 1 of 3
Location permission request
The site requests GPS access for compliance tracking. One tap. The player doesn't need to understand why. The data is collected and sent before they see the code.
Screen 2 of 3
Success screen, English
Activation code, large and unambiguous. "Now, on the slot machine you scanned, enter this code." The phone's job is done. Player's attention goes back to the machine.
Screen 3 of 3
Success screen, Spanish
Same screen, player's language. The flag in the corner toggles between English and Spanish. One tap, no menu, no settings. Designed for a user population that is predominantly Spanish-speaking.
05What changed
Same outcome. Completely different actor.
The goal of machine data collection didn't change. Who was responsible for it did.
Before
Technician-dependent route scans
Technician dispatched on route
scheduling dependencySamsung device + special login required
hardware dependencyUp to 6 QR codes per machine
scan failure riskMissed scan = machine lockout
direct revenue lossReputation damage spreading
business growth impact
After
Player-initiated, continuous collection
QR appears automatically on machine
zero staffing costAny player, any phone
universal accessOne code, displayed large
scan reliabilityPhone transmits data continuously
compliance-readyLockout risk eliminated by design
scalable
06Design decisions
The choices that made this work in the field
This wasn't a typical mobile design project. The users were casino players, ranging from tech-comfortable to tech-averse, on a loud floor, often older. Every decision had to account for that context.
- 1
The mobile site was intentionally minimal
The phone does four things: open a page, collect data, send it, display a code. That's it. No account creation, no profile, no onboarding. Anything that added steps on the phone was a step that could cause a player to abandon the flow. Everything else (validation, feedback, the gameplay continuation) happens on the machine where the player's attention already is.
- 2
The QR code is large because it has to be
QR codes encode data through pixel density. The more data a code carries, the more tightly packed that matrix becomes, and the larger the code needs to be to remain reliably scannable. The machine owner required that the scan capture a significant volume of machine data in a single read. A smaller code physically could not hold it. Size was the only way to keep the matrix scannable under real-world venue conditions: overhead lighting, screen glare, varied scan distances. This wasn't an aesthetic choice. It was physics.
- 3
Bilingual throughout, large text by default
The user base skews older and includes a significant Spanish-speaking population. Both the mobile site and machine UI were designed bilingual from the start, not as an afterthought. Large text wasn't a nice-to-have. It was the default. A player who can't read the prompt at a glance while holding their phone in one hand and a drink in the other will not complete the flow.
- 4
Feedback lives on the machine, not the phone
Once a player enters the code, the machine handles everything. The phone doesn't need to confirm success, show a result, or stay open. This keeps the interaction model clean: the phone is a bridge you use and put away, not an ongoing interface. It also means the flow works even if a player locks their screen or switches apps after getting the code.
07Behavioral design
Getting players to scan voluntarily
A QR code on a machine doesn't scan itself. Getting players to engage required more than availability. It required a reason. The solution used a two-stage behavioral approach: make it appealing before making it required.
- Day 5
Soft Prompt
A prompt appears offering free credits as an incentive to scan. Low pressure. The player can decline and continue playing. The goal is introduction and habit formation before the requirement kicks in.
- Day 7
Required Scan
The machine requires a scan to continue. By Day 7, most players have already encountered the flow voluntarily. The gate doesn't feel like an ambush. It feels like a familiar step with a known reward on the other side.
08Outcomes
What this project actually delivered
This project isn't about a mobile UI. It's about identifying the wrong assumption at the root of a business problem and redesigning around it. The technician was the bottleneck. The player was the solution. The phone was already in their pocket.
Lockout Risk Eliminated by Design
By removing the technician as the sole collection mechanism, machines were no longer dependent on a person showing up on schedule. The failure point was eliminated, not managed.
30-Day Revenue Gaps Closed
Machines that previously sat dark for weeks at a time while waiting for a technician visit now stay active through player-initiated scans that happen continuously.
Reliable Location and Compliance Data
Bad Dog went from technician-dependent location snapshots to continuous, GPS-approximate data collected with every player scan. Compliance tracking became viable for the first time.
Reputation Risk Addressed at the Source
The word-of-mouth problem between venue owners was downstream of the lockout problem. Fix the lockouts and the reputation narrative changes. The design addressed the root cause, not the symptom.
Operational Visibility for the First Time
With continuous scan data, Bad Dog gained access to machine-level performance metrics (uptime, popularity, plays) that had been impossible to track reliably before.
Scalable Without Adding Headcount
The system grows with the machine footprint. Adding machines doesn't require adding technicians. The players in the room are the infrastructure.
“The best systems design I've done has been about finding the person who was already in the room. Players were already standing next to these machines with phones in their hands. The technician model put the right action in the wrong person's hands. Shifting that wasn't a UX insight. It was a business one.”