Hand Sabers

The description states that Hand Sabers is:

• A rhythm game playable in a browser
• Uses webcam tracking for both hands
• Maps hand movements to virtual sabers in a 3D scene
• Features cubes flying toward the player on different lanes that must be hit with the correct hand at the right time and direction
• Includes real-time scoring, accuracy, misses, combos
• Has playable and importable maps
• Offers a map library with leaderboards
• Contains a timeline-based map editor
• Supports one-hand mode and other gameplay settings
• Enables multiplayer rooms and lobbies
• Allows remote tracking through a paired phone
• Incorporates music-reactive visual effects
• Provides performance diagnostics and automated checks

Evidence All of this is self-reported by the author. No independent verification or demonstration of actual product functionality beyond the developer's own account.

The author claims:

• The game turns hands into virtual sabers using only a webcam
• It avoids requiring VR headsets or motion controllers
• It started as a technical experiment but evolved into a full rhythm game with features like multiplayer and map editing
• It uses AI coding tools (Codex + GPT-5.6) to build new features during the hackathon

Inference The positioning appears to be that of an innovative, low-barrier entry rhythm game using existing webcams rather than specialized hardware.

Evidence These are claims made by the author; no external validation or market positioning data provided.

The description states:

• The target is people who want to play a rhythm game without VR or motion controllers
• Users need a webcam and space to move their hands
• It's designed for browser-based play

Inference The ICP likely includes casual gamers, tech enthusiasts, and those interested in interactive web experiences.

Evidence No explicit customer segmentation, user personas, or market research data provided.

The description states:

• There is no mention of pricing
• No business model is described
• No revenue streams are mentioned
• The project was submitted to a hackathon and not commercialized

Evidence Not evidenced. The author does not describe any monetization strategy or pricing structure.

The description states:

• Built with TypeScript, Three.js, Vite, Node.js, Express, WebSockets, browser-based computer vision
• Uses Codex with GPT-5.6 for development assistance
• Features remote hand tracking from a paired phone
• Includes authenticated tracking connections and packet validation
• Has multiplayer host rules, lobby map selection, and chat
• Offers synced previews of remote players' hands
• Contains a 3D preview inside the map editor
• Includes beat-reactive tunnel rings and scene effects
• Provides configurable graphics and music-effect settings
• Has performance profiling for frame processing
• Includes better error isolation and runtime reliability
• Refactored gameplay, networking, diagnostics, and editor systems

Evidence These are self-reported technical details. No evidence of production deployment or scalability.

The description states:

• The project was submitted to the OpenAI 2026 hackathon
• It started as a hand-tracking experiment
• It has progressed from basic tracking to a playable game with multiplayer and map editing
• The author mentions ongoing improvements and future plans

Evidence No data on user engagement, downloads, or usage metrics. The project remains in early development phase.

The description states:

• No specific competitors are named
• It is positioned as a rhythm game using webcam input instead of VR or controllers
• It includes features like multiplayer and map editing that may differentiate it from basic webcam games

Evidence Not evidenced. The author does not reference existing products or competitive landscape.

Key risks identified:

• Developer dependency: Only one person involved (Michał Oślizło)
• Lack of traction or user data
• No commercialization or monetization strategy
• Unproven scalability of webcam-based tracking in real-world conditions
• Limited evidence of product-market fit beyond developer testing
• AI tool reliance without clear indication of human oversight effectiveness

Evidence These are inferred from the lack of external validation, no revenue, and single-developer operation.

1. What is your plan for scaling beyond a single developer?
2. Have you tested the webcam tracking stability under various lighting conditions?
3. Are there any plans to monetize or commercialize this product?
4. How do you intend to validate user experience beyond personal testing?
5. What are your long-term goals for the project and how will you measure success?