Backlog

Next up

In Progress

Done

Main Roadmap

<h2>Important: If you are reading this and want this feature and are willing to be a tester please reach out. </h2><h3>Overview</h3>Enable Tesla in-car browser control of the Echobox audiophile app by providing a reliable connection mechanism that works across hotspot, home networks, and event environments.This feature should prioritize robust connectivity over zero-config discovery, given known limitations with local networking (mDNS, private IP access) in constrained environments like Tesla’s browser and public Wi-Fi.<div data-type="horizontalRule"><hr></div><h3>Problem</h3>Users want to control the Echobox app from a Tesla browser by connecting to a local web UI hosted on their Android device.However:<ul><li>mDNS/Bonjour is unreliable across networks (blocked multicast, AP isolation, etc.)</li><li>Tesla browser may not reliably support <code>.local</code> resolution or private IP access</li><li>Event/show networks are often hostile to peer-to-peer discovery</li><li>Relying solely on local discovery leads to inconsistent user experience</li></ul><div data-type="horizontalRule"><hr></div><h3>Goals</h3><ul><li>Provide a consistent and user-friendly connection flow from Tesla browser → Echobox app</li><li>Support offline/local-first usage where possible</li><li>Ensure functionality works at:<ul><li>Home networks</li><li>Phone hotspot</li><li>Live shows / public Wi-Fi</li></ul></li><li>Avoid breaking existing networking features (UPnP, local control)</li></ul><div data-type="horizontalRule"><hr></div><h3>Proposed Solution (Hybrid Approach)</h3><h4>1. Local Control Mode (Primary for Hotspot / LAN)</h4>When enabled, the app:<ul><li>Starts a lightweight HTTP server on the device</li><li>Optionally advertises via mDNS (<code>_echobox._tcp</code>)</li><li>Displays connection info in-app:<ul><li>Local IP URL (e.g. <code>http://192.168.1.42:port</code>)</li><li>mDNS URL (e.g. <code>http://echobox.local:port</code>)</li><li>QR code for quick access</li><li>Short pairing code</li></ul></li></ul>Notes:<ul><li>mDNS is treated as a bonus convenience, not required</li><li>MulticastLock is only acquired while this mode is active</li><li>Service names include unique instance IDs to avoid conflicts</li></ul><div data-type="horizontalRule"><hr></div><h4>2. Tesla Mode (Enhanced UX)</h4>A dedicated mode optimized for Tesla usage:<ul><li>Automatically:<ul><li>Enables hotspot (if possible)</li><li>Starts local server</li></ul></li><li>Displays a simplified “Connect your Tesla” screen:<ul><li>Large QR code</li><li>Direct IP URL</li><li>Optional <code>.local</code> URL</li></ul></li></ul><div data-type="horizontalRule"><hr></div><h4>3. Cloud Relay / Remote Access (Fallback)</h4>For maximum reliability:<ul><li>App establishes an outbound secure tunnel (WebSocket/WebRTC/HTTPS)</li><li>Generates a session URL:<pre><code>https://echobox.app/session/{id} </code></pre></li><li>Tesla browser connects via public internet</li></ul>Benefits:<ul><li>Works even if:<ul><li>Local network blocks multicast</li><li>Tesla browser blocks private IPs</li><li>User is on restrictive Wi-Fi</li></ul></li></ul><div data-type="horizontalRule"><hr></div><h4>4. Connection Priority Strategy</h4>Client (Tesla browser) attempts:<ol><li>Direct IP (fastest, most reliable locally)</li><li>mDNS hostname (<code>.local</code>) if supported</li><li>Cloud relay URL (guaranteed fallback)</li></ol><div data-type="horizontalRule"><hr></div><h3>Non-Goals</h3><ul><li>Do not rely solely on mDNS for discovery</li><li>Do not require users to configure routers or DNS</li><li>Do not modify or interfere with existing UPnP functionality</li></ul><div data-type="horizontalRule"><hr></div><h3>Technical Considerations</h3><h4>Networking</h4><ul><li>mDNS (UDP 5353) and UPnP/SSDP (UDP 1900) operate independently</li><li>Ensure lifecycle isolation between:<ul><li>mDNS advertising</li><li>UPnP discovery</li><li>HTTP server</li></ul></li></ul><h4>Android Constraints</h4><ul><li>Use <code>MulticastLock</code> only when needed</li><li>Handle vendor-specific network behavior</li><li>Keep services foreground when active to avoid throttling</li></ul><h4>Service Identity</h4><ul><li>Include unique instance ID in:<ul><li>mDNS service name</li><li>TXT records</li><li>Web UI session</li></ul></li></ul><h4>Security</h4><ul><li>Local mode:<ul><li>Optional pairing code</li></ul></li><li>Relay mode:<ul><li>Authenticated session tokens</li><li>Expiring URLs</li></ul></li></ul><div data-type="horizontalRule"><hr></div><h3>UX Flow</h3><ol><li>User opens Echobox → taps “Connect Tesla”</li><li>App shows:<ul><li>QR code</li><li>URL(s)</li></ul></li><li>Tesla connects via:<ul><li>Hotspot (recommended)</li></ul></li><li>If local fails:<ul><li>User uses relay URL</li></ul></li></ol><div data-type="horizontalRule"><hr></div><h3>Risks &amp; Mitigations</h3><table style="minWidth: 50px"><colgroup><col><col></colgroup><tbody><tr><td colspan="1" rowspan="1"></td><td colspan="1" rowspan="1">RiskMitigation</td></tr><tr><td colspan="1" rowspan="1">mDNS fails on some networks</td><td colspan="1" rowspan="1">Always provide direct IP + relay fallback</td></tr><tr><td colspan="1" rowspan="1">Tesla browser blocks local access</td><td colspan="1" rowspan="1">Relay mode</td></tr><tr><td colspan="1" rowspan="1">Multicast drains battery</td><td colspan="1" rowspan="1">Only enable during active session</td></tr><tr><td colspan="1" rowspan="1">Network conflicts</td><td colspan="1" rowspan="1">Isolate services and ports</td></tr></tbody></table><div data-type="horizontalRule"><hr></div><h3>Success Criteria</h3><ul><li>Tesla browser can consistently connect in:<ul><li>Hotspot scenario ✅</li><li>Home Wi-Fi ✅</li><li>Public/show environments ✅</li></ul></li><li>Minimal user friction (≤ 2 steps to connect)</li><li>No regression in existing networking features</li></ul><div data-type="horizontalRule"><hr></div><h3>Summary</h3>Implement a hybrid connectivity model:<ul><li>Local-first (IP + optional mDNS)</li><li>Cloud-backed fallback</li></ul>This ensures reliability across real-world conditions while still supporting zero-config discovery where available.

In Review

Tesla Operating System Support via Local + Relay Connectivity

omb studios

Improve the system for finding missing album artwork.Possible improvements:<ul><li>additional providers</li><li>higher resolution artwork</li><li>manual artwork selection</li><li>automatic artwork matching confidence display</li></ul>

Advanced Artwork Backfill

Track real-world performance of devices over time.Examples:<ul><li>startup latency</li><li>seek success rate</li><li>gapless reliability</li><li>group playback stability </li></ul>The app could automatically adapt playback strategies based on this data.

Renderer Performance Insights

Show detailed information about each network audio device discovered on the network.Display:<ul><li>supported formats</li><li>maximum sample rate</li><li>gapless capability</li><li>seek reliability</li><li>preload support </li></ul>This would help users understand what each device can actually handle.

Renderer Capability Viewer

Allow users to store multiple room correction profiles and switch between them.Examples:<ul><li>Couch listening position</li><li>Desk listening position</li><li>Nearfield vs room listening </li></ul>Profiles could include:<ul><li>PEQ filters</li><li>target curve</li><li>measurement data</li></ul>

Room Correction Profiles

Allow DSP presets to automatically switch based on the output device.Examples:<ul><li>Headphone EQ when using wired headphones</li><li>Speaker correction when using a USB DAC</li><li>Disable EQ when streaming to network renderers </li></ul>This would provide context-aware audio tuning.

Device-Specific DSP Profiles

Allow users to export and share DSP presets such as:<ul><li>parametric EQ profiles</li><li>crossfeed settings</li><li>headphone tuning </li></ul>Users could import presets from other users or from popular headphone profiles.

DSP Preset Sharing

Provide a UI that shows how well multi-room speakers are synchronized.Display:<ul><li>latency estimates</li><li>drift measurements</li><li>sync health status</li><li>which device is the coordinator </li></ul>This would help users understand and troubleshoot multi-room playback timing issues.

Visual Group Sync Diagnostics

Improve queue management and playback behavior.Examples:<ul><li>album-aware shuffle</li><li>queue editing improvements</li><li>smart shuffle (avoid same artist repeats)</li><li>queue save/load </li></ul>This would make managing playback sessions much easier.

Intelligent Queue & Playback Controls

Provide an overview of the library’s audio quality characteristics.Examples:<ul><li>average dynamic range</li><li>distribution of sample rates</li><li>hi-res authenticity statistics</li><li>clipping risk summary </li></ul>This would give users insight into the overall quality of their collection.

Library Quality Dashboard

Allow users to save and recall common speaker groups.Examples:<ul><li>Living Room + Kitchen</li><li>Whole House</li><li>Office + Bedroom </li></ul>One tap would restore the saved group configuration and start playback.

Multi-Room Group Presets

Automatically create collections based on audio analysis and mastering characteristics.Example collections:<ul><li>Most dynamic albums</li><li>Albums with clipping risk</li><li>Suspected upsampled hi-res</li><li>Highest dynamic range recordings</li><li>Inconsistent mastering across tracks </li></ul>This would allow users to explore their library by sound quality rather than just metadata.

Smart Collections Based on Audio Quality

Provide a visual breakdown of the full playback signal path:Source → decoder → resampler → DSP chain → output device.Show information like:<ul><li>source codec and sample rate</li><li>DSP stages applied</li><li>resampling</li><li>output device capabilities</li><li>bit-perfect eligibility </li></ul>This would help users understand exactly what happens to their audio during playback.

Signal Path Inspector (Full Audio Chain Transparency)

Show comparisons between different releases of the same album (e.g., original, remaster, deluxe editions). The app already analyzes loudness, dynamic range, clipping risk, and hi-res plausibility. This feature would present those metrics side-by-side so users can see which version is likely the most dynamic or least compressed.Example information to compare:<ul><li>Dynamic range</li><li>LUFS loudness</li><li>clipping risk</li><li>peak headroom</li><li>hi-res authenticity </li></ul>Goal: help users choose the best sounding version of an album in their library.

Mastering Comparison for Album Variants

Automatically detect duplicate tracks and alternate releases.Examples:<ul><li>same track from different albums</li><li>multiple rips of the same CD</li><li>different mastering versions </li></ul>Users could compare and choose which to keep.

Completed

Duplicate & Variant Detection

Improve how network audio devices appear in the app.Possible improvements:<ul><li>custom device names</li><li>device grouping by room</li><li>favorite devices</li><li>better icons for device types</li></ul>

echobox by ombs.io