Our goal was to design an interface that would be not only visually appealing but also intuitive and accessible for users with disabilities. Thanks to a clean layout, facial navigation support, large interactive elements, and the ability to rearrange components, the application became truly inclusive. During school testing, children with disabilities were able to use the interface with ease and joyfully played virtual instruments. Teachers highlighted the user-friendly visual style and its adaptability to various cognitive and motor needs.

We implemented all essential features, including facial input, different play modes, multiplayer functionality, and AI-powered tools. One of the most important additions was the ability to reposition elements on the screen — a feature highly appreciated by users with physical limitations. Due to time constraints, a few optional features, such as saving custom layouts and implementing a personalized AI teacher, were postponed. However, all core functionality was delivered and works as intended.

The application proved to be stable throughout demonstrations and testing, with no crashes or critical failures. The only issues encountered were slight delays in multiplayer synchronization over slower connections and occasional interface lag when switching modes rapidly. These minor problems were documented and can be addressed in future iterations.

We prioritized support for a wide range of input methods, including mouse, keyboard, facial navigation, and Jamboxx. The user interface is responsive and works across different screen sizes, including tablets and laptops. This was confirmed during testing sessions in a school environment, where students used various devices and interaction methods.

The project codebase is hosted on GitHub and organized into modular, logically independent components. Each team member worked in their own branch and merged into the main branch after review, minimizing conflicts. Key modules are accompanied by README files with descriptions and setup instructions, making the project easy to maintain or extend by future developers.

We followed Agile principles, adapting them to our team’s workflow. Instead of formal tools, we communicated through a shared WhatsApp group and held regular in-person and online meetings. Work was divided into iterations, and tasks were discussed and assigned based on current priorities. Our team had clearly defined roles: each member was responsible for a specific area — from UI/UX and frontend to artificial intelligence and backend development. This structure helped maintain transparency and ensured efficient collaboration throughout the project.