Games
/app-game is the Prox OS route group for browser-native games. It is a
Positioning
/app-game is the Prox OS route group for browser-native games. It is a
lightweight arcade and game-folder experiment, not a full game marketplace.
The current pack ships local, UI-first games that run inside managed OS
windows without backend services, external engines, multiplayer, or score sync.
Playable Apps
| App | Route | Controls | Status |
|---|---|---|---|
| Games Hub | /app-game | Open game cards | Playable launcher |
| Snake | /app-game/snake | Arrow keys or WASD | Playable |
| Tile Merge | /app-game/tile-merge | Arrow keys or WASD | Playable |
| Minesweeper | /app-game/minesweeper | Click reveal, right-click or Flag Mode to flag | Playable |
| Memory Cards | /app-game/memory-cards | Click cards | Playable |
| Breakout | /app-game/breakout | Arrow keys or A/D, Space pause | Playable |
| Pong | /app-game/pong | Arrow keys or W/S, Space pause | Playable |
| Falling Blocks | /app-game/falling-blocks | Arrows, Space hard drop, P pause | Playable |
Implementation Boundary
- Games use local React state only.
- Games do not call production APIs, databases, score services, auth, payments, multiplayer systems, or external game runtimes.
- Animation games use
requestAnimationFrameor interval cleanup so pause, game over, and unmount stop updates. - Keyboard handlers ignore editable targets and prevent default only for game controls.
- High scores in the hub are placeholder catalog values, not persisted user records.
Snake Polish
Snake received a lifecycle and control pass:
- Keyboard input now ignores editable elements.
- Rapid opposite-direction input is queued safely so the snake cannot reverse into itself between ticks.
- Game over and win states stop movement and cannot be restarted accidentally through movement keys.
- Food generation handles a full board and avoids occupied cells.
- Pause, restart, and unmount cleanup remain local to the current window.
Phase 2+
- Define iframe sandbox and performance policy for external games.
- Add local score storage after user data persistence policy is clear.
- Design community game submission, moderation, and takedown flows.
- Add touch controls and mobile window presets where useful.
- Explore AI-generated game templates after runtime review and moderation boundaries are documented.
Non-goals
- No multiplayer.
- No game backend.
- No real community submissions.
- No ad network, payment, or external game engine.
Data Boundary
Games uses bundled mock records and local component state only. No score, identity, payment, multiplayer, or community data is persisted or sent to a backend.
Relationships
Games Hub and each local game are registered through the shell app registry and appear in the App Store Games collection. Future game publishing should connect to Permission Center, Trust Center, and App Store review before any community runtime is enabled.