The costly workflow
Remote music sessions lose the immediacy of playing together when control data, hardware access, and session feedback live in separate tools.
Live beta
TeleMIDI Connect
A browser-based collaboration flow that lets a host keep MIDI hardware local while a remote player sends expressive controls through a shared session.
Musicians collaborating across distanceActive beta · 2026Evidence reviewed July 28, 2026
Interface evidence
A real frame from the documented system
Each image is an optimized public-safe capture. Captions state the fixture, data, and verification boundary represented in the frame.
The public launcher defers the collaboration bundle until a visitor explicitly requests it. This capture contains no session code, device details, or user data.
ProvenanceCaptured from the committed public launcher with no active runtime session or fixture mutation.
What Devin owned
Designed and built the public browser workflow, session model, realtime feedback, and host-versus-remote control boundaries.
System design
Architecture and data flow
The public description stays at a useful system level without exposing private records, credentials, or machine-specific implementation details.
Architecture
- Static browser client served through the portfolio application
- Firebase-backed realtime session state
- WebMIDI output on the host device
- Keyboard scanning and live piano feedback in the client
Data flow
- The host creates a session and connects a local MIDI destination.
- A remote player joins with the shared session information.
- Control events move through realtime state to the host browser.
- The host browser sends the authorized events to local MIDI hardware.
Constraints
- MIDI hardware must remain on the host computer.
- Browser support for WebMIDI varies by device and browser.
- Public sessions need a simple path without exposing private administration.
System-flow diagram
How information moves through the verified slice
This is a public-safe architecture diagram, not a product screenshot. It shows responsibilities and handoffs without exposing private data or implementation paths.
Flow step 01
The host creates a session and connects a local MIDI destination.
Flow step 02
A remote player joins with the shared session information.
Flow step 03
Control events move through realtime state to the host browser.
Flow step 04
The host browser sends the authorized events to local MIDI hardware.
Evidence references
The artifacts behind the verification
Each reference names the implementation, test, documentation, or public demonstration that supports the claims on this page.
Hosted browser beta
The published client exposes host and remote roles, session joining, keyboard input, and live connection feedback.
Open the public artifactSession API contract suite
Create and join contracts cover invalid input, unavailable runtime configuration, and successful session responses.
Runtime configuration boundary
The public client receives only the configuration required for the collaboration flow; administrative controls remain separate.
Verified behavior
What the evidence supports
- Host-created sessions and remote joining are implemented in the public beta.
- Remote control, WebMIDI output, keyboard scanning, and live piano feedback are represented in the shipped client.
- The public route is isolated from the private administration surface.
The beta demonstrates the complete browser-to-hardware collaboration path without requiring MIDI hardware on the remote player’s device.
Boundaries
What this case study does not claim
- The beta depends on a WebMIDI-capable host browser.
- Session observability and recovery UX are still being refined.
- It is a live beta, not a claim of production-scale usage.
Proof-safety review
Public package checks
Confirmed for the material rendered on this case-study page and its linked public evidence.
- Confirmed — Uses only public or synthetic proof data
- Confirmed — Contains no secrets or credentials
- Confirmed — Contains no personal data
- Confirmed — Contains no machine-local absolute paths
- Confirmed — Contains no private records
- Confirmed — Exposes no writable production controls
- Confirmed — Contains no protected-system references
Implementation vocabulary
FirebaseWebMIDIJavaScriptRealtime collaboration