Project Overview
FoogleTech engineered the full embedded and Android stack for an online multiplayer boxing game system, where physical strikes on hardware pads are detected by custom firmware and relayed to an Android application in real time. Starting from an unusable >300ms latency baseline and unreliable hit detection, FoogleTech redesigned the firmware strike-detection algorithm, UART communication protocol, and Android integration layer — achieving sub-100ms response and 98% accuracy across straight-on and side strikes.
The Engineering Challenge
- The initial prototype had end-to-end strike detection latency exceeding 300ms — completely breaking the real-time gameplay experience and making competitive multiplayer impossible at any meaningful level.
- Double-hit detection was a persistent firmware bug: rapid successive strikes on the same pad were being registered as a single event or generating phantom double-counts, causing match score corruption in competitive play.
- Device classification across multiple hardware pad types was handled inconsistently in firmware, causing the Android application to misidentify which device sent which strike event — especially critical in multi-pad multiplayer setups.
- Synchronising firmware event timestamps with Android UI rendering required a reliable, low-overhead serial protocol that could handle burst events without dropping frames during intense strike sequences.
Our Solution
- FoogleTech rewrote the strike detection algorithm in Embedded C with a configurable debounce window and strike-force threshold, implemented at the firmware level on PIC microcontrollers (programmed via PICkit and MPLAB) — eliminating double-hit false positives while maintaining sensitivity across varying strike intensities.
- Hardware-level device classification commands were introduced into the UART protocol, allowing each physical pad unit to self-identify on initialisation — the Android app then maps all incoming strike events to the correct device without ambiguity, even in multi-device multiplayer configurations.
- A custom lightweight serial frame protocol was designed to minimise round-trip time between firmware strike detection and Android event handling, combined with firmware-side interrupt-driven event reporting (replacing the original polling approach) to eliminate polling-induced latency.
- The Android integration layer was rebuilt using Android Studio with dedicated serial port reader/writer threads running at elevated priority, decoupled from the UI rendering thread — ensuring strike events are processed and displayed within the target latency budget regardless of UI load.
Results & Outcomes
- End-to-end strike detection latency reduced from over 300ms to consistently below 100ms — transforming the product from an unplayable prototype to a genuinely competitive real-time multiplayer experience.
- 98% accuracy achieved across both straight-on and side strikes on center body pads, with the double-hit bug fully resolved and zero phantom events recorded during final acceptance testing.
- Device classification operating correctly across all multi-device multiplayer configurations, with each pad unit reliably identified from initialisation without any manual assignment or external configuration.
- The optimised firmware and Android stack shipped and accepted by the client — the product went from prototype to demonstrated live gameplay within the project timeline.
Why Online Boxing — Embedded Strike Detection Chose FoogleTech Software
FoogleTech Software is a specialist engineering company with over a decade of expertise in AI, embedded systems, IoT, and full-stack software development — serving product teams and enterprises across Gaming & Entertainment and beyond. Our engineers don't just write code — they understand the domain, the constraints, and the real-world pressures that ship deadlines create. For Online Boxing — Embedded Strike Detection, that meant deploying a pre-vetted team with direct experience in Embedded C, Arduino, UART, reducing ramp-up time from months to days and delivering production-quality work from the first sprint.
Every FoogleTech engagement starts with a structured discovery phase, follows a disciplined agile delivery model with daily engineering syncs, and ends with complete documentation handover — so your in-house team owns the outcome. No black boxes, no lock-in.