A card game that used to be counted by hand now scans in under five seconds, with every round verified and logged.

Balotech Game’s AR Card-Scanning Platform

The Objective

Balotech is a traditional card game where rounds were counted and verified by hand, which meant miscounts, slow setup, and disputes mid-game, with no record of who bought in, what happened, or who won the last trick. We built an AR mobile platform that scans the cards in under five seconds, auto-verifies every count, and writes each round to a synced ledger with full history and round-level insight. Scan accuracy now runs at 98.7%, disputes are down 78%, and daily rounds are up 61%. Hand-counting became a five-second scan.

Service Tags

Mobile App Development UI/UX Redesign AR Feature Engineering Performance Optimization

Industry Tags

AR Gaming Mobile Gaming

Tech Stack

Kotlin (Android) Swift (iOS) Angular AR card-scanning and auto-verification engine Real-time backend logic with auto-synced ledgers

The Impact

98.7%
Scan accuracy on card verification
AR scanning verifies every card count with near-perfect precision.
78%
Reduction in disputes
Auto-verification removed the miscounts that used to stall rounds.
61%
Increase in daily rounds
Faster setup and scanning let players run more games per day.
47%
Increase in game sharing
Built-in social sharing pulled more players into each game.
The Client

A classic card game ready for a faster, fairer format.

Balotech Game is a modern reinvention of a traditional Balotech card experience, built for the people who already play it. The owner came to us to take a classic offline activity and make it fast, accurate, and transparent on mobile. The brief was clear on what mattered: speed in the hand, accuracy in the count, and a record of every round that players could trust.

The Problem

A game whose pace was set by how fast someone could count cards.

Every round of Balotech depended on someone counting cards correctly, by hand. That broke down in the ways manual counting always does, miscounts that slowed the round and started arguments about what had actually been played. Setup and verification dragged, and in competitive rounds that delay was the difference between a good session and a frustrating one.

There was also no memory. Nothing tracked who bought in, what round type was played, Kaboot, Double, or how previous rounds turned out. Players had no live view of card distribution, the last trick winner, or where the current round stood. The game lived entirely in the moment and in people’s recollection of it, and recollection is exactly what causes disputes.

Our Approach

Make the scan fast enough to disappear, then build trust on top of it.

Speed was the thing the whole experience hinged on. If scanning a hand took longer than counting it, nothing else mattered, players would go back to counting. So the AR scanning and recognition engine came first, tuned until a full hand read in under five seconds. Everything else was built on the assumption that the scan was fast enough to feel invisible.

Accuracy was the second pillar, and it had to be near-perfect, because the entire reason to digitize was to end the disputes. Auto-verification checks every card in the scanned hand, so the count isn’t a judgment call anymore. Once scanning and verification were reliable, the ledger followed naturally: if every round is captured accurately, you can keep a complete, trustworthy history of it without anyone logging anything by hand.

On top of that we layered the round-level insight players were missing, trick winners, card distribution, round progress, and built social sharing directly into the flow, so a good game could pull in more players instead of ending in silence.

What We Built

An AR scanning engine, a smart ledger, and a redesigned mobile experience.

AR Scanning & Verification
Smart Ledger & Insights
How It Was Built

A nine-person squad, seven months, through five phases.

A nine-member cross-functional product squad delivered the platform over seven months, moving through research, design, development, AR integration, and deployment. The sequence mattered: research and design framed how players actually move through a round, then AR integration was treated as its own phase rather than a feature bolted onto a finished app, because the scanning accuracy and speed were the make-or-break of the whole product. Native builds on Kotlin and Swift, with Angular on the web, gave the performance headroom that real-time scanning and ledger syncing needed.

Outcome

Every round scanned, verified, and remembered.

Balotech now runs as a fast AR experience instead of a hand-counted one. A hand scans in under five seconds, the count is auto-verified so there’s nothing left to argue about, and every round writes itself to a ledger players can look back on, buyers, round types, trick winners, distribution, and results. Scan accuracy holds at 98.7%, disputes have dropped 78%, and players are running 61% more rounds a day, with sharing up 47% as good games spread on their own. The game kept everything that made it worth playing and shed the friction that slowed it down.

Testimonials

“Our operations required a high-volume, highly dependable system, and AppVerticals delivered exactly that. The architecture is scalable, the backend is fast, and the UI is clean. It transformed how our teams work.”

Thomas Reid

Balotech Game

AR Builds Where the Technology Has to Disappear

Turning a real-world activity into a fast, accurate mobile experience, where the technology has to disappear for players to trust it? That's the kind of AR build we engineer for speed and accuracy from the first phase.

Start a conversation