Engagement at a glance
- Task: Build voice-controlled puzzle gameplay and clear audio feedback
- Historical project budget: $55,000
- Delivery period: 2019-2020, 9 months
Audio-interactive case study
An adventure game case built around voice input, audio interaction and accessible puzzle mechanics across mobile and desktop storefronts.
Players use voice input to affect the game world, making UX feedback and audio readability core production requirements.
Case evidence
CrocoApps worked on game development, audio-interactive design and the user interface during a nine-month engagement spanning 2019-2020.
The work focused on translating microphone input into understandable puzzle actions and feedback across mobile and desktop releases.
| Project | One Hand Clapping |
|---|---|
| Release platforms | Google Play, App Store, Epic Games Store and Steam |
| Engine / stack | Unity, C#, Photoshop |
| CrocoApps scope | Game development, audio-interactive design and user interface |
| Timeline | 9 months |
| Historical project budget | $55,000 |
| Production period | 2019-2020 |
Source: CrocoApps public project archive and approved production materials.
Voice input
Voice-based interaction changes the UX problem: the game must help players understand pitch, timing and microphone feedback without making the mechanic feel technical.
The production materials show review stages, interaction work and final gameplay states for the voice-input mechanic.
Voice-driven gameplay creates unusual UX and testing needs: players differ by vocal range, confidence, hardware and environment.
Voice input lets players solve puzzles and affect the game world.
The system needed to support different vocal ranges and player skill levels.
The UI had to explain audio input clearly enough that players could understand cause and effect.
The game was released through Google Play, the App Store, Epic Games Store and Steam.
CrocoApps addressed a non-standard input mechanic by combining interaction validation, readable UX feedback, Unity development and microphone testing.
Validate how voice input maps to game actions and puzzle states.
Create feedback that makes audio interaction understandable.
Build gameplay systems and platform-ready versions.
Review microphone, range and usability risks across player conditions.
Share the mechanic, hardware assumptions and platform goals so we can identify early technical risks.