Inspiration
Motion-controlled games often require dedicated consoles, controllers, or wearables. Motion Arcade asks whether a standard Android phone can eventually provide an offline, controller-free arcade for one or two players.
What is implemented today
Motion Arcade is currently an engineering baseline, not yet a playable game. The repository contains:
- an immutable design source of truth and staged acceptance gates
- a modular Android project with app, vision, deterministic game-core, and games boundaries
- a pinned supply chain and a bundled offline MediaPipe pose model
- tested time and coordinate-transform contracts
- automated JVM, Android emulator, CI, APK-policy, native-runtime, and license checks
- a content-addressed debug APK that intentionally displays only the Slice 0A baseline screen
Live camera binding, motion recognition, gameplay, two-player identity tracking, final visual assets, physical-device QA, performance/thermal evidence, and release approval are still unfinished.
Planned experience
The target experience has three distinct games: Harbor Pop Fishing, Neon Gym Boxing, and Runestone Monster Expedition. Each is planned for solo and two-player motion input, but those gameplay claims remain goals until the corresponding slices and release gates have direct evidence.
How it is being built
The Android project uses Kotlin, Jetpack Compose, CameraX, MediaPipe, Gradle, and Python validation scripts. Codex is being used as a coding and review collaborator to analyze the design package, implement bounded slices, generate tests, and keep completion claims tied to build, test, and review evidence.
Challenges and learning
The difficult part is not drawing a game screen. It is proving that camera coordinates remain correct across rotation and lens changes, that two people are not silently swapped, that native resources are closed on every path, and that an emulator is never treated as proof of physical-device behavior. The project has reinforced a simple rule: compilation is evidence of a build, not evidence of a finished product.
Current status
The technical baseline and coordinate-transform sandbox have passed their recorded automated checks. Capability-probe policy work is under independent rereview. The current APK is intentionally non-playable, and no gameplay video, store listing, physical-device result, or release-ready claim is available yet.
Log in or sign up for Devpost to join the conversation.