Robotics Learning Educational Game

The problem

The client had a robotics simulator that could not grow. Its Unity codebase depended on deprecated APIs and conflicting packages, core systems were unstable, and every new feature risked breaking an old one. On top of that rescue, they needed a complete product: a full interface, real gameplay, a curriculum for two age groups, an in-game economy students could not tamper with, and a live connection to their backend, on both Windows and macOS.

Our approach

We planned the eight months as four phases, each with written acceptance criteria and a milestone review before the next one began. We stabilised before we built: the core was audited, repaired and profiled before a single new feature went in. We made the server the only source of truth for coins, rewards and progress. And we documented every system as we built it, so the client’s own developers could take over without us.

How we delivered it

Core engineering and stability (Months 1–2)

• Technical audit of every existing system
• Resolved package conflicts and replaced deprecated APIs
• Refactored unstable legacy code
• Profiled and optimised performance
• Stable, production-ready baseline builds

Interface and user experience (Months 3–4)

• 12 screens built from the approved designs
• Core navigation flows
• Curriculum progression screens
• Event management interface
• In-game HUD and feedback states

Gameplay and economy (Months 5–6)

• Drag-and-drop simulator interactions
• Challenge and practice game modes
• Junior and Senior curriculum tracks
• Server-authoritative economy: coins, chips and energy
• 28-day daily rewards and character shop

Backend integration and launch (Months 7–8)

• Full API integration: authentication, profiles and inventory
• Server-synchronised progress tracking
• End-to-end QA and optimisation
• Production builds for Windows and macOS
• Technical handover documentation

What we built

A production-ready learning platform in Unity and C#. Students program a robot by dragging command blocks into place and watch it run their code in real time. They learn through Junior and Senior curriculum tracks, try ideas in a practice sandbox, and compete in challenge modes and team events. A server-authoritative economy of coins, chips and energy, a 28-day daily reward cycle and a character shop keep them coming back. Sign-in, profiles, inventory and progress all sync with the client’s backend.

Results

Delivered on schedule and to specification across all four phases: two production builds with identical features, more than 12 screens, and a complete handover of source code and documentation. The platform needed no further development to go to market, and the client’s team can now maintain and extend it on their own.

• Shipped on schedule and to specification across all four phases
• Two production builds with identical feature sets
• Economy and progress validated on the server, with no client-side manipulation
• Full handover: source code, architecture, database and API docs, build and deployment guides, QA test protocols
• Ready for commercial deployment with no further development