Sendspin’s JavaScript player corrects several browser timing errors that could leave a browser silent or out of step with other speakers. On Android, implausibly large delay reports no longer cause every audio chunk to be discarded, and keeping the audio output open across disconnects avoids repeatedly introducing an extra delay.
Safari and Firefox receive separate timing corrections. In the contributor’s microphone measurements, an iPhone running iOS 18.7 with its built-in speaker moved from about 29 milliseconds early to 0.3 milliseconds early. On the tested MacBook Pro, Safari moved from about 70 milliseconds early to 5 milliseconds late. In Firefox on macOS, playback moved from about 22 milliseconds late to 0.3 milliseconds late.
These are corrections in the JavaScript client, not a claim about every Sendspin application. Apple Bluetooth and AirPlay outputs still need a manually chosen delay, and Android browser playback can remain late. Quick reconnects also stop carrying old audio into the new connection.