Melody Rain

What the company appears to be: Melody Rain is a local-first web application that transforms traditional sheet music into animated visual performances using MusicXML, MIDI, and MP3 files. It renders notes as falling elements synchronized with audio playback and exports them as portrait-format MP4 videos.

What changed: The project was submitted as part of the OpenAI 2026 hackathon. No evidence suggests prior commercial activity or product development beyond this submission.

Single most important open question: Is there any evidence of traction, revenue, or customer adoption beyond the author's own description?

The description states that Melody Rain is a local-first React and TypeScript application built with Vite and SCSS. It uses OpenSheetMusicDisplay to render MusicXML as SVG sheet music, @tonejs/midi for MIDI timing, and integrates audio playback with score movement and note animation.

It synchronizes MusicXML notation, MIDI timing, and MP3 audio on one timeline so that notes "fall" toward the score in sync with musical events. The system supports customization of background, colors, transparency, animation style, score layout, title, and playback speed.

The application can export complete performances as 9:16 MP4 videos in standard or high quality using a local pipeline involving Playwright, FFmpeg, and Chrome/Edge browsers.

Evidence: Self-reported by author; no third-party verification. The description claims the product is built with specific technologies but does not provide functional screenshots, user data, or performance metrics.

The author positions Melody Rain as a tool that brings emotional depth to sheet music visualization — not just a functional timeline but an expressive experience that reconnects users with music. The tagline "Notes fall like rain. Music comes alive." reflects this emotional framing.

It is described as a small doorway back into the feeling of music, especially for those who no longer practice instruments but still enjoy looking at sheet music. The goal is not to replace learning or performing an instrument, but to offer a way for people who have drifted away from music to see it again and perhaps return to playing.

Inference: This positioning implies a niche audience focused on nostalgia, emotional connection, and accessibility rather than performance or education tools.

The description does not explicitly state target customers or personas. However, the author's personal motivation — studying piano as a child, stopping due to life busyness, and wanting to reconnect with music — suggests an audience of former musicians or music enthusiasts who are nostalgic for their relationship with music.

It may appeal to individuals interested in sharing musical experiences through short-form video platforms where portrait-format content is popular.

Inference: The ICP likely includes people who value emotional engagement with music, have access to sheet music files, and want to create or consume visually engaging musical content without needing technical skills or cloud services.

There is no evidence of a business model or pricing structure in the description. The project is presented as a hackathon submission and does not mention monetization strategies, subscription plans, freemium tiers, or any commercial offerings.

Not evidenced: No indication of how revenue would be generated or what users might pay for access to Melody Rain.

Melody Rain is built using React, TypeScript, Vite, SCSS, Express.js, Playwright, FFmpeg, and tone.js-midi. It uses a deterministic state model to ensure consistency between preview and export functions.

The system maps MIDI events back to visible score elements and computes every falling, landing, and resting state from an absolute timeline. Video export is handled locally using Playwright to launch a browser instance and pipe PNG frames to FFmpeg for MP4 creation.

Codex (GPT-5.6) was used as an active development collaborator throughout the project, helping with implementation planning, code generation, debugging, testing, and documentation.

Evidence: The description provides technical details about architecture, tooling, and workflows, but no evidence of production deployment, scalability issues, or performance benchmarks.

There is no evidence of traction, revenue, customers, or adoption beyond the author's own account. The project was submitted to a hackathon and has no recorded usage statistics, user feedback, or market presence.

Not evidenced: No data on downloads, active users, customer retention, or product usage patterns.

The description does not mention competitors or similar products. It focuses solely on the unique emotional experience it aims to deliver rather than comparing itself to existing tools in the music visualization space.

Not evidenced: No information about competing solutions, market size, or competitive positioning.

• No commercial traction: The project is presented as a hackathon submission with no evidence of prior product development or user base.
• Limited scalability: The local-first approach and browser-based export pipeline may limit performance for large-scale use cases.
• Dependency on AI tooling: While Codex was used during development, the application itself does not call OpenAI APIs at runtime — this raises questions about whether future versions will introduce such dependencies.
• Niche appeal: The emotional positioning suggests a narrow target market, which could limit growth potential.

1. What is the intended path from hackathon prototype to commercial product?
2. Are there any plans for monetization or business model development beyond the current scope?
3. Has the team explored how users might interact with or share these videos outside of the platform?
4. How does the local-first architecture scale, especially when handling large files or batch processing?
5. What are the long-term technical and design goals for Melody Rain beyond the current features?