Aeria

The description states that Aeria is a browser-based, gesture-controlled music instrument built by one developer (Fèmi Sanya) using React, Vite, MediaPipe, and Tone.js. It allows users to play musical notes via hand gestures detected through a webcam, with support for multiple instruments including piano, violin, bells, and theremin. The project was submitted as part of the OpenAI 2026 hackathon.

The author claims Aeria works without hardware or cost, runs in-browser, and uses no external API calls. It includes visual feedback for each instrument and supports pinched-finger play modes. The system maps hand positions to musical notes using a constrained scale (initially pentatonic, later expanded to major) to ensure harmonic output.

Key commercial due-diligence questions include: Is there any evidence of user adoption or engagement beyond the single developer? What is the actual market demand for such a tool? Are there any technical limitations that prevent scalability or usability in real-world settings?

The description states that Aeria is:

• A browser-based music instrument
• Controlled via hand gestures detected through a webcam
• Built using React, Vite, MediaPipe Hand Landmarker, and Tone.js
• Capable of playing notes from C to B with different instruments (piano, pad, violin, bells, theremin)
• Visual feedback provided for each instrument (particles, animated keyboard, skeleton)
• Supports pinched-finger play mode
• Runs in the browser without requiring hardware or external API calls

Inferred from the description:

• The product uses MediaPipe for real-time hand tracking and Tone.js for audio synthesis.
• It maps finger positions to musical notes using a constrained scale (pentatonic then major) to maintain harmony.

Not evidenced:

• No actual functionality demonstration or user testing data
• No mention of performance metrics, latency, or accuracy of gesture detection

The author claims Aeria is:

• A browser-based, gesture-controlled music instrument
• Designed for people who want to play music but don’t always have access to a physical instrument
• Creative and novel, especially in its use of the theremin-like sound

Inferred from the description:

• The positioning appears to be focused on accessibility and convenience for casual users or learners.
• The claim of novelty seems to stem from combining gesture control with browser-based music creation.

Not evidenced:

• No evidence of market research, competitor analysis, or target audience validation
• No indication that this is a product in development or intended for commercial release

The description states:

• The inspiration comes from someone who loves music and wants to play piano but lacks time or access to a real instrument
• The tool is meant for people who want to play music casually, without needing physical instruments

Inferred from the description:

• The target user may be amateur musicians, students, or hobbyists interested in exploring music creation with minimal setup.

Not evidenced:

• No defined customer segments beyond general interest in music
• No evidence of personas, usage scenarios, or feedback from potential users
• No indication of whether this is aimed at individuals or educational institutions

The description states:

• Aeria requires no hardware, has no cost, and runs in the browser
• It does not involve any monetization strategy or pricing model

Inferred from the description:

• The project appears to be non-commercial in nature, possibly a personal experiment or hackathon submission.

Not evidenced:

• No evidence of revenue streams, pricing plans, subscriptions, or monetization strategies
• No indication of whether the creator intends to commercialize it

The description states:

• Built with React and Vite for frontend
• Uses MediaPipe Hand Landmarker for real-time hand tracking (no video data leaves device)
• Tone.js for audio synthesis
• Implemented gesture-to-note mapping system constrained to a scale (pentatonic then major)
• Visual feedback includes particles, animated keyboard, and skeleton
• Features include pinched-finger play mode

Inferred from the description:

• The project uses modern web technologies and integrates well with browser-based APIs.
• There is an iterative development process involving prompt engineering and debugging sessions with Codex.

Not evidenced:

• No evidence of scalability, performance optimization, or robustness under various conditions
• No information about long-term maintenance or support plans

The description states:

• The project was submitted to the OpenAI 2026 hackathon
• It was built entirely by one person (Fèmi Sanya)
• There is no mention of user adoption, downloads, or usage beyond the developer’s own experience

Inferred from the description:

• This is likely a prototype or proof-of-concept rather than a mature product.
• The lack of traction indicators suggests early-stage development.

Not evidenced:

• No evidence of users, customers, or market validation
• No data on engagement, retention, or performance metrics
• No indication of ongoing development or roadmap beyond the hackathon submission

The description does not provide any information about competitors or similar products in the market.

Inferred from the description:

• The author believes their approach is unique due to its gesture-based browser-based interface and lack of hardware requirements.
• However, no competitive landscape is described or analyzed.

Not evidenced:

• No mention of existing tools or platforms offering similar functionality
• No evidence of competitive advantages or differentiation strategies

The description indicates several potential risks:

• Hand tracking accuracy issues (mentioned as a challenge during development)
• Low-light latency problems related to MediaPipe limitations
• Lack of user testing or feedback beyond the developer’s own experience
• Unclear path to commercialization or monetization

Inferred from the description:

• The project may not be suitable for widespread adoption due to technical constraints.
• Without clear traction or a defined business model, there is little evidence of viability as a product.

Not evidenced:

• No evidence of risk mitigation strategies or plans for addressing technical limitations
• No indication of how the creator intends to scale or improve upon the current version

1. What specific user needs does Aeria address, and how did you validate those needs?
2. Are there any users or early adopters beyond yourself who are actively using or testing Aeria?
3. How do you plan to monetize or commercialize this tool if at all?
4. Have you considered scalability issues related to browser-based performance and latency?
5. What are the technical limitations of the current implementation, and how might they affect usability?
6. Is there a longer-term roadmap for development beyond the hackathon version?