Free 30-minute AI & automation audit with a senior engineer. You keep the notes. Book yours

Use case · Sports technology

Connected software for a cricket bowling machine, from serial commands to live scoring

A venue controller, operator tablet apps, display screens and a Bluetooth app that turn a physical bowling machine into a connected cricket-simulator experience.

Client details are kept confidential. This use case describes the problem and what we built.

The brief

A sports-technology company makes cricket bowling machines for training centres and simulator venues. The hardware was solid, but the experience around it needed software: operators had to run sessions easily, players needed live feedback, and the machine had to fit into venue and partner systems.

We built the connected software layer. It covers a controller that drives the machine over serial and coordinates sensors, cameras and screens, operator apps for tablets, a player display, and a Bluetooth app for direct control.

The challenge

What needed solving

Hardware with a binary protocol

The bowling machine is driven by motors and actuators for speed, line, length and pitch deviation. It speaks a framed binary protocol over a serial link, which software has to drive safely and predictably.

A full venue experience

Simulator venues needed players registered, games queued, balls planned, runs scored automatically and highlights replayed on big screens, all coordinated in real time.

Personal machines without a venue PC

Machines used outside venues had to be controlled straight from a phone or tablet.

The solution

What we built

  1. Venue machine controller

    A Java desktop application on the venue PC sends serial commands to the machine. It plans each ball, reads scoring sensors, records camera clips and plays highlights. It exposes a REST API and a WebSocket event stream, and keeps the game queue in a local MongoDB.

  2. Operator tablet app

    A React Native tablet app for operators to set up players, configure the machine, start or queue games and watch live ball-by-ball scoring. We later ported it to Flutter with a bloc-based architecture.

  3. Player-facing display screen

    A React, TypeScript and Redux web screen that subscribes to the controller's WebSocket and shows scores, prompts and game state to players.

  4. Bluetooth control app

    A Flutter app that talks to the machine over Bluetooth Low Energy, with actuator defaults, power-on sequencing, speed and braking control, and pitch-deviation settings. It is backed by protocol-level test suites.

  5. Third-party integration design

    Documented integration paths for partner booking or kiosk systems: either push players and games into the venue queue, or pass commands through the controller to the machine.

The outcome

What changed

One connected system

Machine, sensors, cameras, tablets and screens now work as one coordinated system instead of separate devices.

Hands-free scoring and highlights

Automatic scoring and replayed highlights add to the player experience without extra staff effort.

Ready for partners

A clear REST and WebSocket surface makes it straightforward to plug the machine into booking and membership systems.

Technology used

  • Java
  • Javalin
  • Jetty WebSocket
  • Serial (JSSC)
  • VLCJ
  • MongoDB
  • React Native
  • Redux Toolkit
  • Flutter
  • Dart
  • Bluetooth Low Energy
  • React
  • TypeScript
  • Vite

Have a similar problem to solve?

Share a few lines about your project. A senior engineer — not a salesperson — replies within one business day.

Free AI audit Let’s talk